How to Take a Snapshot in Oracle VirtualBox
Learn how to create a VirtualBox snapshot, choose the right VM state, name and verify restore points, and manage storage safely.
Oracle VirtualBox is a desktop virtualization platform used to create and run virtual machines. A virtual machine (VM) is a software-defined computer managed by VirtualBox, with its own operating system, applications, memory, and virtual hardware.
A snapshot is a recoverable point-in-time record of a VM. It lets you return the VM to an earlier condition after installing software, changing settings, applying updates, or testing a configuration.
When to Create a Snapshot
Create a snapshot when you have a clear restore purpose. Useful points include:
- Before installing untrusted, experimental, or difficult-to-remove software.
- Before changing operating-system settings.
- Before applying a major operating-system or application update.
- Before changing server, database, network, TLS, or application configuration.
- Before running a potentially destructive experiment.
A meaningful restore point is easier to use than a collection of snapshots with unclear purposes. For example, create a snapshot immediately before a change and document what the VM looked like at that moment.
VirtualBox Terms You Need to Know
- Powered off: The guest operating system is not running.
- Saved state: VirtualBox has saved the VM's paused execution state so it can resume later.
- Running state: The guest operating system is actively executing.
- Machine state: The VM's in-memory execution condition, including information that may allow a running VM to resume at the captured point.
- Virtual disk: A file-backed storage device used by the VM.
- Differencing data: Data that records virtual-disk changes made after a snapshot point.
- Restore point: A snapshot selected as the target for returning the VM to an earlier condition.
VM States and Snapshot Considerations
| VM state | What the user sees | Snapshot consideration | Recommended use |
|---|---|---|---|
| Powered off | The guest operating system is shut down. | Creates a point without capturing active memory. This is a straightforward and predictable option. | Use before software installation, updates, or configuration changes when the VM can be shut down. |
| Saved | The VM is paused and its state has been saved by VirtualBox. | The saved condition can be recorded. Describe the saved condition clearly. | Use when you want to preserve the VM as it was left in its saved state. |
| Running | The guest operating system is actively running. | VirtualBox can support creating a live snapshot where available. The dialog may offer an option to capture the current machine state as well as disk changes. A disk-only point and a point that includes machine memory are not equivalent. | Use only when a live capture is appropriate. For a simple, clean restore point, shut down the guest first when practical. |
How to Take a Snapshot in VirtualBox Manager
- Open Oracle VirtualBox Manager.
- Select the target VM from the machine list.
- Open the Snapshots tab or view. The exact placement can vary slightly by VirtualBox version.
- Select Current State in the snapshot tree.
- Start snapshot creation using the camera-style Take Snapshot control, or open the context menu for Current State and choose Take Snapshot.
- Enter a descriptive snapshot name.
- Add an optional description explaining what has been installed, configured, or tested.
- If the VM is running and the option is available, choose whether to include the current machine state. Including machine state captures the live execution condition; leaving it out creates a disk-focused point in time.
- Confirm creation and wait for VirtualBox to finish.
- Verify that the new snapshot appears in the snapshot tree beneath the appropriate VM state.
Example: Before Testing Software
For a clean development VM before installing an experimental application, use:
- Name: Before-test-software
- Description: Clean development VM before installing the test application.
If the test damages the guest system, this snapshot provides a defined point for returning the test environment to its pre-installation condition.
Example: Before an Operating-System Update
- Name: Pre-OS-update
- Description: VM state before applying the monthly operating-system updates.
This gives you a documented rollback point if the update causes a problem.
Example: Before Server Configuration Changes
- Name: Before-web-server-config
- Description: Known-working web server configuration before TLS and virtual-host changes.
Snapshot Names and Descriptions
Use names that identify both the purpose and, when useful, the timing of the restore point. Examples include Clean-install, Pre-OS-update, Before-database-migration, and Before-web-server-config.
Descriptions should answer questions that may arise later: What was installed? Which settings were changed? Was the guest powered off, saved, or running? What test or update was about to begin?
| Practice | Why it matters | Example |
|---|---|---|
| Use descriptive names | Identifies the intended rollback point quickly. | Pre-OS-update |
| Add a purpose-based description | Records the condition and reason for creating the snapshot. | VM state before monthly operating-system updates. |
| Check host free disk space | Snapshot-related data can grow as the VM changes. | Check the drive containing the VM files before a large test. |
| Avoid retaining unnecessary snapshots | Long-lived snapshots consume storage and make management harder. | Remove obsolete test restore points through VirtualBox. |
| Review the snapshot tree before restoring or deleting | Parent-child relationships affect which state and data are retained. | Confirm the selected snapshot is the intended restore point. |
Understanding the Snapshot Tree
Snapshots are displayed in a hierarchical snapshot tree. The tree shows snapshots associated with a VM and their parent-child relationships.
Current State represents the VM's present condition and the changes made after its snapshot ancestry. When you create another snapshot from the current state, VirtualBox can add a further entry to the sequence. If you restore a snapshot and then create new snapshots, you can create a separate branch from that point.
Order matters. A child snapshot depends on the history represented by its parent. Before restoring or deleting an entry, inspect the tree and identify which snapshot contains the desired restore point and which later changes may depend on it.
Storage Impact and Limitations
Creating a snapshot does not mean that every future version of the VM is stored as a separate full copy. As the VM changes, VirtualBox uses snapshot-related differencing data to preserve the earlier point while recording later virtual-disk changes. The amount of storage used depends on the VM's disk activity and the changes made after the snapshot.
- Available host disk space limits how many snapshots and subsequent changes can be retained.
- Busy VMs that write large amounts of data can cause snapshot-related storage to grow quickly.
- Numerous or long-lived snapshots increase storage use and management complexity.
- Check free space on the host drive containing the VM files before creating or retaining snapshots.
Do not delete snapshot files manually in the host file manager. Use VirtualBox's snapshot management controls so that related virtual-disk data can be handled consistently.
Verify the New Snapshot
After creation, remain in the Snapshots view and check:
- The new entry is visible in the snapshot tree.
- The name describes the intended restore point.
- The description records the relevant installation, configuration, or test condition.
- The date and time are consistent with when the snapshot was taken.
- The parent position in the tree is correct.
- You can clearly identify this entry as the snapshot to use if rollback becomes necessary.
Snapshot Creation Troubleshooting
The Snapshot Option Is Not Visible
- Confirm that the correct VM is selected in VirtualBox Manager.
- Open the Snapshots view rather than the general machine details view.
- Select Current State and try its context menu.
Snapshot Creation Fails or Does Not Complete
- Check available space on the host drive containing the VM files.
- Confirm that the VM files and their containing folders are writable.
- Check whether another process is locking or actively copying VM files.
- Wait for current VM disk activity or another VirtualBox operation to finish, then try again.
Snapshot Names Are Confusing
Review the names, descriptions, and tree hierarchy. Replace ambiguous habits such as Snapshot 1 or Test with purpose-based names such as Before-test-software.
Host Disk Space Shrinks After Snapshot Creation
Explain the change as normal snapshot-related growth: later VM disk changes require additional storage while the earlier point is preserved. Identify obsolete snapshots for careful cleanup, but do not remove their files manually. Use VirtualBox to delete snapshots.
Expecting a Snapshot to Replace a Backup
A snapshot is designed to return a VM to a previous state. It is not a complete backup strategy and may depend on the VM's existing files and storage. Use separate backups or exports for important VM data.
Restoring and Deleting Snapshots
Restoring a snapshot returns the VM to the selected snapshot state. This is a related procedure and should be performed only after checking the snapshot tree and confirming which later changes may be discarded or separated.
Deleting a snapshot removes that restore point and causes VirtualBox to consolidate related snapshot data. Deletion should be planned carefully because it changes the tree and can require time and host storage while consolidation occurs.
For the next procedures, see how to restore a VirtualBox snapshot and how to delete a VirtualBox snapshot. If you need an independent copy rather than a rollback point, review how to clone a virtual machine and VirtualBox virtual disk management.
Quick Checklist
- Select the correct VM.
- Check its state and available host storage.
- Open Snapshots and select Current State.
- Choose the camera control or the Current State context-menu action.
- Use a purpose-based name and useful description.
- Choose machine-state capture when relevant to a running VM and appropriate for the restore goal.
- Confirm creation.
- Verify the entry, date, description, and parent position in the snapshot tree.