How to Restore a Snapshot in Oracle VirtualBox

Learn how to restore an Oracle VirtualBox snapshot, what changes are lost during rollback, how to prepare safely, and how to validate the restored VM.

What Restoring a Snapshot Does

A snapshot is a saved recovery point for a virtual machine (VM). A VM is the guest computer managed by VirtualBox, while the guest operating system is the operating system running inside it.

When you use Restore Snapshot, VirtualBox performs a rollback: it returns the VM to the saved state represented by the selected snapshot. This is useful for undoing unwanted changes, recovering from failed testing, or returning a training or development VM to a known-good baseline.

For example, you can take a snapshot before installing an application. If the installation makes the guest operating system unstable, restoring the snapshot returns the VM to the earlier state, before that installation and its related changes.

What a VirtualBox Snapshot Contains

A snapshot represents the VM at the moment it was created. Depending on the VM and its storage configuration, the restored state includes:

Virtual hard disk state: the disk image used by the VM for the guest operating system, applications, and files.
Guest files and folders: data stored inside the guest virtual disks is returned to its earlier state.
Guest system configuration: operating-system settings and other changes stored on the virtual disks can be reverted.
VM settings and configuration: VirtualBox-managed machine metadata and virtual hardware settings associated with the snapshot can be restored.

This scope is different from a complete backup of the host computer. Files stored on the host outside the VM, such as documents in a host folder, are not automatically restored by restoring the VM snapshot.

What Is Lost During Restoration?

Restoring a snapshot discards the VM's current state—its present configuration and disk contents before restoration. Changes made after the selected snapshot may no longer be available.

VM component	Effect of restoration	Typical examples
Guest virtual disk contents	Returned to the disk-related state represented by the snapshot.	Earlier disk blocks, partitions, and stored data.
Files and folders in the guest OS	Files created, changed, or deleted after the snapshot may be reverted accordingly.	Documents, source code, logs, and test data.
Installed applications and updates	Software added after the snapshot may disappear.	Applications, patches, drivers, and updates.
Guest system configuration	Post-snapshot operating-system changes can be rolled back.	Services, user settings, registry or system configuration changes.
Virtual machine settings	VirtualBox configuration changes made after the snapshot may be reverted.	Virtual hardware or machine configuration adjustments.
Files stored on the host outside the VM	Normally unaffected by the VM snapshot.	Host documents and separate host-side backups.

Prepare Before Restoring

Identify the target snapshot. Review the VM's snapshot list and confirm its name, description, and position in the snapshot history. Choose the exact recovery point you need.
Save important work inside the guest OS. Copy important files to an independent backup location or to a host-side location that you understand will not be part of the rollback.
Preserve the current state if necessary. If you may need today's work later, create a new snapshot of the current VM state before restoring the older snapshot. Give it a descriptive name such as Before-rollback-2026-08-18.
Prepare the VM for the operation. Shut down the guest operating system and ensure the VM is powered off unless your VirtualBox version and situation explicitly support another state. Do not interrupt VirtualBox while it is applying the rollback.

The pre-restore snapshot creates a separate recovery point for the state that existed immediately before the rollback. It does not merge that state into the older snapshot.

Restore a Snapshot in the VirtualBox Interface

Open Oracle VirtualBox Manager.
Select the virtual machine that you want to roll back.
Open the VM's Snapshots view or snapshot list.
Review the available snapshots and select the desired recovery point.
Open the selected snapshot's context menu, commonly by right-clicking it.
Choose the Restore action.
Read the warning carefully. Confirm only after checking that the current state can be discarded or has been preserved in another snapshot or backup.
Allow VirtualBox to complete the operation. Avoid closing VirtualBox, disconnecting storage, or manually changing the VM's disk files during the rollback.

After completion, the selected snapshot should be shown as the VM's active restored state or current branch in the snapshot list. The exact labels and layout can vary between VirtualBox versions, but the operation is performed from the selected VM's snapshot view.

Validate the Restored VM

Start the VM and check that the guest operating system boots normally.
Verify that expected files, applications, and settings match the selected snapshot's timeframe.
Confirm that changes you intended to remove—such as a failed installation, test files, or experimental configuration—are no longer present.
Check important services, network access, mounted virtual disks, and application startup if the VM is used for a lab or production-like task.
Use the VM normally only after these checks succeed.

Examples of Snapshot Rollback

Undoing a Failed Software Installation

A user creates a snapshot named Before-app-install, installs an application, and finds that the guest OS becomes unstable. Restoring Before-app-install returns the guest disk and related VM state to the point before the application and its associated changes were made.

Preserving Current Work Before a Rollback

A developer needs to restore an older known-good snapshot, but the current VM contains useful test results. The developer first creates a snapshot named Current-test-results, then restores the older snapshot. The older state becomes active while the former current state remains available as a separate recovery point.

Resetting a Training Lab

A student completes a lab that modifies system files and settings. To repeat the exercise from a clean baseline, the student restores the baseline snapshot. The VM is then ready for another attempt with the earlier disk contents and configuration.

Restore Snapshot Safety Checklist

Check	Why it matters	Recommended action
Correct snapshot selected	Restoring the wrong point can remove the wrong work.	Verify the name, description, date, and snapshot-tree position.
Important guest data saved	Post-snapshot guest data can be lost.	Back up important files before confirming restoration.
Current state may be needed later	The present VM state is discarded by rollback.	Create a pre-restore snapshot or an independent backup.
VM is ready for rollback	Active guest activity can complicate a state change.	Shut down the guest and follow VirtualBox's state requirements.
Post-restore validation	A successful operation does not prove that applications or services work as expected.	Boot the VM and verify files, settings, applications, and services.

Safe Snapshot Management Practices

Use descriptive names that identify the purpose and timing, such as Clean-lab-baseline or Before-kernel-upgrade.
Create a snapshot before risky changes, including upgrades, experiments, major configuration edits, and software installations.
Keep track of which snapshots are known-good recovery points and which represent unfinished experiments.
Do not keep unnecessary snapshots indefinitely. Snapshot chains can increase storage use and make disk management more complex.
Use independent backups for important files and complete VM recovery. A snapshot depends on the VM's virtual disk files and is not a replacement for backup storage.

Troubleshooting Snapshot Restoration

The Wrong Snapshot Was Restored

This usually happens when the snapshot name or its position in the snapshot list was not verified. If you created a snapshot of the former current state before restoring, locate and restore that recovery snapshot after confirming it is the desired state. Use clearer names for future recovery points.

Files Created After the Snapshot Are Missing

This is an expected result when those files were stored on a guest virtual disk. The rollback returned that disk to its earlier state. Recover the files from an independent backup or host-side copy if one exists. For future restores, back up important guest data or create a current-state snapshot first.

Recent Software or VM Settings Disappeared

Changes made after the selected snapshot are reverted along with the rest of the VM state. Verify that the restored state matches the selected snapshot's timeframe, then reapply only the changes that are still needed. Take a snapshot before future major changes.

Host Files Were Not Restored

A VM snapshot primarily affects the VM configuration and associated virtual disk state. It does not restore arbitrary files stored on the host. Use separate host backups for documents and other resources outside the VM.

Key Points

Restoring a snapshot rolls a VM back to an earlier saved point.
Guest disk contents, guest-level changes, and applicable VM configuration changes made after that point can be lost.
Host files outside the VM are normally not affected.
Verify the target snapshot, save important work, and create a pre-restore recovery point when needed.
Boot and test the guest OS after restoration before relying on the VM.