Virtual Machine Snapshots in Oracle VirtualBox

Learn what Oracle VirtualBox snapshots capture, how to create and view them, and how to restore a VM to an earlier working state safely.

A virtual machine snapshot is a saved restore point for a virtual machine (VM) at a specific time. It lets you return the VM to the captured condition later, which is useful when studying, testing software, or making risky configuration changes.

This lesson assumes that you understand the difference between a host computer and a guest operating system. If you need an introduction, review what a virtual machine is and what a guest operating system is.

Why Use VirtualBox Snapshots?

A snapshot preserves a point in the VM's lifetime. After the snapshot is created, you can continue using the VM, install software, change settings, or modify files. If you later need the earlier condition, you can restore the snapshot.

Common uses include:

Preserving a clean operating system installation for repeated labs.
Creating a rollback point before an operating system update.
Testing unfamiliar applications or configuration changes.
Capturing an in-progress lab session that you want to resume later.
Comparing a VM before and after a change.

What a VirtualBox Snapshot Includes

VirtualBox associates a snapshot with the VM and records several parts of its condition. The exact storage details are managed by VirtualBox, but the practical result is a restore point for the VM's configuration and data.

Captured component — What it represents — When it matters

VM settings — Configuration information associated with the VM, such as its assigned hardware and other setup details — Restores the VM configuration that existed at the snapshot point.

Power state — Whether the VM was powered off, powered on, or suspended — Helps restore the VM to the appropriate operating condition.

Virtual disk state — The recorded state of the virtual disks attached to the VM — Returns guest files, installed software, and disk-based configuration to the earlier condition.

Optional memory state — The contents of the running VM's memory — Allows a running session to resume from approximately the same point when memory was included.

The memory state is different from the virtual disk state. Disk state contains information stored on the VM's virtual disks. Memory state contains what was held in RAM, such as running applications and an active lab session. A snapshot made without the desired memory condition cannot recreate that exact running session.

Current State and Saved Snapshots

A newly created VM has no explicit saved snapshots. The Snapshots view can still show an item named Current State. This is normal.

Current State means the VM's present, changing point in its history. It reflects the condition after the most recent saved snapshot, or the beginning of the VM's history if no snapshot exists. It is not itself a named, permanent restore point.

An explicit snapshot is a saved point that you create and name. Current State changes as you use the VM; a saved snapshot remains available until you restore, delete, or otherwise manage it.

State or action — Meaning — Typical use

Current State — The VM's present condition — Continue normal VM work or inspect what has changed since the last snapshot.

Take Snapshot — Saves a new restore point — Preserve a known working condition before a change.

Restore or Revert — Returns the VM to a selected snapshot — Discard or roll back unwanted changes.

Delete Snapshot — Removes a saved restore point and lets VirtualBox reorganize its snapshot-related disk history — Remove obsolete restore points after confirming they are no longer needed.

Viewing Snapshots in VirtualBox Manager

Open Oracle VirtualBox Manager.
Select the target virtual machine in the VM list.
Open the Snapshots view using the Snapshots control in the Manager interface.
Inspect the snapshot list or tree. Named entries represent saved restore points, while Current State represents the VM's present condition.

Read snapshot names and descriptions before selecting one for restoration. In a snapshot history, later snapshots may depend on earlier points, and the displayed structure helps you identify the milestone you actually want.

Creating a Snapshot

Graphical workflow

Choose the VM state you want to preserve. Confirm that the guest is in a known, useful condition.
Select the VM in VirtualBox Manager and open its Snapshots view.
Choose Take Snapshot from the snapshot interface or the relevant VM controls.
Enter a meaningful name, such as clean-installation or pre-update-2026-08.
Add a description explaining what the snapshot contains and what you expect to happen if you restore it.
Confirm the operation and wait for VirtualBox to finish.

Good names identify a purpose or milestone rather than only a date. For example, Ubuntu-clean-lab-baseline is more useful than Snapshot 1. A description might say: Guest updates complete; lab tools installed; restore to this point before experimenting with networking.

Running versus powered-off VMs

You can create a snapshot while the VM is running or while it is powered off. The choice affects what can be preserved:

For a powered-off VM, the snapshot records a stopped condition and disk-based state.
For a running VM, including memory state can preserve the contents of memory and the in-progress session.
If memory is not included, restoring the snapshot should not be expected to reproduce every open application or exact running-session condition.

For a clean baseline, powering off the guest before taking the snapshot can make the intended starting condition clear. For a lab that must resume with applications open, use a running snapshot with the appropriate memory state when VirtualBox offers that option.

Restoring a Snapshot

Open the VM's Snapshots view.
Select the saved snapshot that matches the desired milestone.
Choose Restore or Revert, depending on the wording shown by your VirtualBox version.
Review any warning about the current condition and confirm only after checking that important newer work is backed up or no longer needed.
Start or resume the VM and verify its operating system, applications, files, and power condition.

Reverting restores the configuration, virtual disk state, power state, and memory state when memory was saved. Changes made after the selected snapshot can be discarded or become inaccessible from the restored line of history, depending on the restoration choice and the snapshot structure. Treat restoration as a potentially destructive operation for newer VM work.

For more focused instructions, see how to restore a snapshot.

Practical Snapshot Examples

Clean operating system baseline

Install and configure the guest operating system.
Apply the desired initial configuration and confirm that the VM works.
Create a snapshot named clean-lab-baseline and describe the installed components.
Install experimental software or make configuration changes.
Revert to clean-lab-baseline when the experiment should be discarded.

This creates a repeatable starting point for practice and testing.

Before a risky update

Confirm that the VM is in a known working condition.
Create a snapshot named pre-update-working-state.
Apply the operating system or application update.
Test the guest system.
Restore the pre-update snapshot if the result is unacceptable.

The snapshot reduces the risk of making a temporary change to a working VM, but important files created after the snapshot should be copied elsewhere first.

Capturing a running lab session

Leave the running VM at a useful point in the lab.
Take a snapshot and include memory state when continuation from that exact session is required.
Restore the snapshot later and compare the resumed session with a powered-off snapshot workflow.

Memory state can preserve an in-progress session, not merely the files stored on virtual disks.

Identifying the correct restore point

Open the Snapshots view for the selected VM.
Compare the names and descriptions of saved snapshots with Current State.
Choose the saved snapshot whose milestone matches the condition you need.
Confirm the selection before reverting.

Clear labels make recovery safer, especially when a VM has several snapshots.

Snapshot Chains and Storage

A snapshot chain is the sequence or branching history formed when multiple snapshots are created over time. After a snapshot, later disk changes must remain associated with the snapshot history so that VirtualBox can reconstruct the relevant states.

As the VM changes after a snapshot, snapshot-related disk history can consume additional host storage. The original virtual disk may not grow in the same way as the complete snapshot history, but the total space used by the VM and its snapshots can increase substantially.

Monitor free space on the host computer.
Avoid keeping many unnecessary snapshots for long periods.
Use snapshots for meaningful milestones rather than every minor change.
Review the snapshot tree before deleting or restoring a point.
Keep sufficient free space for normal guest disk activity and snapshot operations.

Long chains can make storage management more complicated and may affect disk operations. Deleting an obsolete snapshot can require VirtualBox to reorganize snapshot-related disk data, so allow time for the operation and do not interrupt it unnecessarily.

Learn more about the files used by VMs in virtual disk image files and virtual disks.

Snapshot Versus Backup

Need — Snapshot suitability — Backup suitability

Short-term rollback before a change — Excellent for quickly returning the same VM to a known condition — Useful as an additional safety measure, but usually slower to restore for this purpose.

Repeated lab reset — Convenient for returning to a clean baseline — A backup or clone can also provide a separate reusable source.

Long-term disaster recovery — Not suitable as the only protection — Use independent backups stored separately from the active VM.

Protection from host storage failure — Not suitable if the snapshot remains on the same host storage — Use a backup copied to separate storage or another system.

Back up important guest files and the VM itself according to your recovery requirements. Snapshots and backups solve different problems: snapshots provide convenient short-term rollback, while independent backups provide protection against broader failures and data loss.

Troubleshooting Snapshots

The Snapshots list appears empty

No explicit snapshot may have been created yet. It is normal to see Current State without any named saved snapshots. Create one with Take Snapshot if you need a restore point.

The VM does not return to the expected state

The wrong snapshot may have been selected, or the expected changes may have occurred after that snapshot. Review the names, descriptions, and position of snapshots in the history before restoring. Confirm that you selected the intended milestone rather than Current State.

The VM resumes differently than expected

The snapshot may not contain the desired running memory condition, or it may have been created from a different power state. Distinguish saved disk state from optional memory state, then create the next snapshot from the appropriate powered-off, powered-on, or suspended condition.

Host disk space decreases substantially

Subsequent disk changes may be accumulating in snapshot history. Check available host storage, review obsolete snapshots, and retain only useful restore points. Do not continue creating snapshots if the host is running low on space.

A snapshot is being treated as the only data-loss protection

This usually indicates confusion between rollback points and independent backups. Keep separate backups of important VM data and files. A snapshot stored with the VM cannot protect against every failure affecting that VM directory or host storage.

Safe Snapshot Practices

Create a snapshot immediately before a risky operating system, application, or configuration change.
Use names that identify the purpose, milestone, and, when useful, date.
Write a description containing the expected restore outcome.
Check the VM's power state and decide whether memory state is needed.
Confirm that important post-snapshot files are backed up before reverting.
Review and delete obsolete snapshots after they are no longer useful.
Monitor host disk space and avoid unnecessary long-lived chains.
Maintain independent backups for important data.

Exam-Relevant Notes

A snapshot is a saved restore point, not merely a screenshot of the guest desktop.
Snapshot contents can include VM settings, power state, virtual disk state, and optional memory state.
Current State is the present changing condition, not an explicit saved snapshot.
Restoring a snapshot can discard or hide changes made after that point.
A snapshot chain records the history created by multiple snapshots.
Snapshots can consume host storage and are not a substitute for independent backups.