# Snapshots (instance vs volume)

Source: https://docs.quake.ai/docs/compute/concepts/snapshot-types
Markdown: https://docs.quake.ai/docs/compute/concepts/snapshot-types.md

---

# Snapshots (instance vs volume)

**Snapshot** means different things depending on which service creates it. On Quake AI, separate the two cases before you plan backup or migration.

## Instance snapshots

An **[instance snapshot](/docs/compute/concepts/snapshots)** captures the instance root disk (and related metadata) into a bootable **image**. Use it to clone a configured server, roll back after a risky change, or build a golden image pipeline.

Nova and Glance handle this path. The result is an image you can launch as a new instance.

## Volume snapshots

A **volume snapshot** is a point-in-time copy of a **[block volume](/docs/block/concepts/volumes)** managed by Cinder. Use it for database disks, attached data volumes, and backup schedules that target storage independently of the instance lifecycle.

Volume snapshots can be restored to new volumes or used as clone sources. They do not automatically replace instance images unless you design that workflow.

## Provider vocabulary

| Provider phrase | Usually means on Quake AI |
|---|---|
| AWS EBS snapshot | Volume snapshot |
| AWS AMI from instance | Instance snapshot → image |
| GCP disk snapshot | Volume snapshot |
| DigitalOcean volume snapshot | Volume snapshot |
| "Snapshot the server" (ambiguous) | Clarify: instance image vs attached volume |

## What to read next

- [Instance snapshots](/docs/compute/concepts/snapshots): capture and restore instance state
- [Volumes](/docs/block/concepts/volumes): volume snapshots and clones
- [Backup and restore an instance](/docs/compute/how-to/backup-and-restore): operational backup workflow