VMware ESXi and vSphere Cluster Management

Delete Virtual Machine Snapshots in VMware ESXi Using vSphere Snapshot Manager

Learn how to delete one or all VMware ESXi virtual machine snapshots, understand snapshot hierarchy effects, and safely validate merges, discarded restore points, and consolidation.

Deleting a VMware virtual machine snapshot is an operation performed in the vSphere client through Snapshot Manager. It is different from deleting the virtual machine or deleting its active virtual disks. Snapshot deletion removes a restore point and merges required disk changes into an applicable parent snapshot or the base disk.

A snapshot is not merely a label placed on a disk. VMware uses delta disks to record writes made after the snapshot was created. When you delete a snapshot, vSphere commits or merges the required delta data so that remaining disk states continue to work. The operation can therefore require substantial datastore space and disk I/O.

Snapshot hierarchy and key terms

Snapshots form a dependency chain or tree. Understanding the tree is essential before confirming a deletion.

Base disk: The original virtual disk state. Snapshot data may eventually be merged back into this state.
Snapshot: A point-in-time virtual machine disk state. Depending on how it was created, it can also include memory and configuration state.
Parent snapshot: The earlier snapshot or disk state on which a later snapshot depends.
Child snapshot: A later snapshot that depends on its parent.
Delta disk: A disk file containing writes made after a snapshot was created.
Current state: The VM's active running position in the snapshot hierarchy. Snapshot Manager commonly marks it with You are here.
Commit or merge: Incorporating delta-disk changes into a parent snapshot or the base disk.

The recorded point in time and the current running state are not necessarily the same. A snapshot can represent an older restore point while the VM continues running with later changes. The position of the selected snapshot relative to You are here determines which data is merged and which restore points may be discarded.

Prepare before deleting a snapshot

Identify the correct virtual machine in the vSphere inventory.
Open its Snapshot Manager and inspect the complete snapshot tree.
Confirm the snapshot you intend to select and locate the current-position indicator, usually labeled You are here.
Determine whether the selected snapshot is above, at, or below the current position on the displayed branch.
Check datastore free capacity. Merging changed data requires writes and may temporarily need additional working space.
Consider the VM's disk I/O and schedule the operation when the impact is acceptable.
Use a backup or another recovery plan if the snapshot is an important restore point.

Do not interrupt snapshot deletion or consolidation once it starts unless directed by an appropriate recovery procedure. Monitor the vSphere task instead. Powering off the VM solely to stop a merge can create additional operational risk.

Delete one snapshot in Snapshot Manager

Open the vSphere client and select the target virtual machine.
Open Snapshot Manager.
Review the tree, including the selected snapshot and the You are here indicator.
Select the intended snapshot.
Choose Delete, then confirm the operation.
Monitor the vSphere task until merging and cleanup finish.
Refresh or reopen Snapshot Manager. Confirm that the selected snapshot is gone and that the remaining tree matches the expected design.

The exact menu placement can vary between vSphere client versions, but the operation is performed from the VM's Snapshot Manager rather than by manually deleting virtual-disk files from a datastore.

How the selected position changes the result

Selected snapshot position	Deletion behavior	What remains available	What is permanently removed
Above the current position	The selected ancestor is removed and its required data is committed into the previous disk state or parent.	Later snapshots and the current branch can remain usable because their required disk state is preserved through the merge.	The selected snapshot as a separate restore point.
At the current position	Changes represented by that snapshot are merged into its parent.	The VM's current disk contents and the parent state remain.	That snapshot as a separate revert point.
Below the current position	The selected snapshot is a descendant or future branch relative to the current position. Removing that branch point also removes dependent child snapshot positions on that path.	The current position and unaffected branches remain, subject to the tree and merge result.	The selected future point and subsequent child restore points below it.
Delete All	All snapshots are removed. Data before the current position is merged toward the base disk; future branches after the current position are discarded.	The VM's resulting active disk state, with no snapshot tree.	Every snapshot restore point.

Example: delete an ancestor while retaining a newer snapshot

Consider this chain:

Base disk -> snap01 -> snap02 -> You are here

If you select snap01 and choose Delete, snap01 is removed and its data is merged into the earlier disk state. snap02 and the current state remain available because the merge preserves the disk state needed by the later child.

The operation does not restore the VM to snap01, nor does it delete the VM. It removes snap01 as an independent point in time while maintaining the usable later branch.

Example: delete the current snapshot

Consider this layout:

Base disk -> snap01 -> snap02 (You are here)

Deleting snap02 commits the changes associated with snap02 into snap01. The VM keeps its current disk contents, but snap02 is no longer available as a restore point. snap01 remains as the earlier point in the tree.

Example: delete a snapshot below the current position

In a displayed branch, a snapshot below You are here is a descendant or future branch relative to the current active position. For example:

Base disk -> snap01 -> You are here -> snap02 -> snap03

If you select snap02 and delete it, snap02 is removed along with dependent later restore points on that path, including snap03. The current position at snap01 remains, but you can no longer revert to the snap02 or snap03 moments.

This result is different from deleting an ancestor above the current position. Carefully inspect the parent-child layout before confirming, especially when a selected future branch has several child snapshots. If one of those points is needed for recovery, use an appropriate backup or recovery plan before deleting the branch.

Delete All behavior

Delete All removes every snapshot associated with the virtual machine. It is appropriate only when no snapshot restore point needs to be retained.

Snapshots preceding the current position are merged toward the base disk so the active disk state remains usable. Snapshots after the current position are future branches or restore points and are discarded rather than retained. After the operation completes successfully, Snapshot Manager should show no snapshots for the VM.

Open Snapshot Manager and review every branch.
Confirm that all restore points can be removed.
Choose Delete All and confirm.
Monitor the task through merge and cleanup.
Refresh Snapshot Manager and verify that the snapshot tree is empty.

Operational monitoring and validation

Snapshot deletion can take from a short time to a lengthy maintenance period. Duration depends on the amount of changed delta data, snapshot depth, datastore performance, and ongoing VM I/O.

Watch Tasks and Events for progress, completion, or errors.
Keep sufficient free datastore capacity available throughout the merge.
Do not interrupt an active delete or consolidation task.
After completion, verify that the intended snapshots are absent and only intended restore points remain.
Confirm that the VM is powered and operating normally and that applications can access their disks.
Refresh the inventory or reopen Snapshot Manager if the interface has not updated.

Delete, Delete All, Revert, and Consolidate compared

Action	Primary purpose	Effect on disk data	Effect on restore points
Delete	Remove one selected snapshot.	Merges required snapshot changes into a parent or applicable earlier disk state.	Removes the selected restore point; dependent future points can also be removed when the selected node is below the current position.
Delete All	Remove the VM's entire snapshot tree.	Merges data before the current position toward the base disk and discards future branches.	Removes every restore point.
Revert	Return the VM to a selected saved state.	Changes the VM's active state to the selected snapshot rather than simply removing the snapshot.	The selected snapshot remains available unless separately deleted.
Consolidate	Resolve residual or orphaned snapshot disk data when vSphere reports that consolidation is needed.	Merges remaining delta-disk data as a maintenance operation.	Does not serve as a general choice for selecting and removing a particular restore point.

Troubleshooting snapshot deletion

A needed restore point disappeared

The selected snapshot may have been below the current position or may have been a branch point with dependent child snapshots. Review the tree and You are here indicator before deletion. Recover the state from a backup if the deleted restore point is required.

Deletion takes a long time

A large delta disk, deep snapshot chain, slow datastore, or heavy VM I/O can make the merge lengthy. Monitor the task, preserve datastore capacity, and reduce avoidable I/O when operationally appropriate. Do not power off or interrupt the VM solely to stop the merge.

The VM reports that disk consolidation is needed

Residual delta-disk files may remain after snapshot operations. First confirm that no snapshot task is still running and verify datastore space. Use Consolidate when appropriate; consolidation is distinct from selecting a snapshot and deleting its restore point.

Delete is unavailable or the task fails

Possible causes include insufficient vSphere privileges, another conflicting VM task, storage access problems, or insufficient datastore capacity. Check permissions, recent tasks and events, free space, and storage connectivity before retrying.

Exam-relevant points

Snapshot deletion is performed from the VM's Snapshot Manager in the vSphere client.
Deleting a snapshot does not delete the VM or its active virtual disks.
Deletion commonly merges delta changes; it is not just removal of a point-in-time marker.
The snapshot tree and the current-position indicator determine whether later branches are preserved or discarded.
Delete All removes every snapshot and every snapshot restore point.
Consolidate addresses remaining snapshot disk data when vSphere requests consolidation; it is not the same action as Delete.

For related administration skills, review the VMware ESXi online course, browsing VMFS datastores, and assigning vSphere permissions.