Snapshots of files

Disk-only, taken automatically every minute and at each stop.

docs-confirmed “Every stop makes the snapshot that a resume needs: `boat stop`, auto-stop, and a stop for an empty wallet.” Source↗

A named snapshot keeps the disk and the memory.

docs-confirmed “A snapshot is a saved copy of a specific machine. It captures the disk and the memory” Source↗

A cold snapshot captures the filesystem of a stopped sandbox.

docs-confirmed “container sandboxes capture filesystem state only (**cold snapshots**), VM sandboxes capture filesystem and memory state (**hot snapshots**)” Source↗

A filesystem snapshot is the lighter option and reboots on resume.

docs-confirmed “To save only the filesystem — a lighter snapshot that reboots on resume — pass `mode: 'filesystem'`” Source↗

Snapshots hold installed software and the files under /data.

docs-confirmed “A snapshot holds a machine’s installed software and its files under `/data`: home, workspace and saved sign-ins” Source↗

A snapshot holds every file on the disk and survives the source sandbox.

docs-confirmed “A snapshot saves a running sandbox’s memory, running processes and every file on its disk.” Source↗

A filesystem snapshot becomes an image that any number of sandboxes can start from.

docs-confirmed “Filesystem Snapshots and Directory Snapshots are [Images](/docs/sdk/py/latest/Image) and are automatically garbage collected after their TTL expires (30 days by default).” Source↗

Snapshots hold memory and disk together.

docs-confirmed “Snapshots are immutable point-in-time copies of both memory and disk state.” Source↗

Disk mode keeps only the root filesystem and boots fresh.

docs-confirmed “Snapshots accept `mode: "memory"` (the default) or `mode: "disk"` in `POST /v1/sandboxes/{id}:snapshot`.” Source↗

A stop snapshot holds the disk and the memory.

docs-confirmed “**Stop snapshot** (disk + memory)” Source↗

A checkpoint holds the writable layer on top of the base image.

docs-confirmed “A checkpoint snapshots the writable filesystem overlay” Source↗

Filesystem is the default snapshot type and restores with a cold boot.

docs-confirmed “`filesystem`: captures filesystem state and restores with a cold boot.” Source↗

Snapshots are made automatically at every stop unless you opt out.

docs-confirmed “Snapshots capture the state of a running sandbox, including the filesystem and installed packages.” Source↗

The catch: There is no snapshot you can save under a name; the only restore points are seven nightly copies of the home folder.

Backups restore in place only, and cover /home/node.

docs-confirmed “Every instance’s data (`/home/node`) is backed up nightly into seven rotating slots, so the last seven nights are available as restore points.” Source↗

The catch: Snapshots work but are in private preview, so the provider does not recommend them for production.

docs-confirmed “This feature is currently in private preview and is not recommended for production use.” Source↗

The catch: Snapshots are in public beta, hold at most 20 GB, and are deleted 30 days after they were made or last used.

Mounted buckets are not included in a snapshot.

docs-confirmed “[`snapshotContainer()`](/containers/api/durable-object-container/#snapshotcontainer) saves the writable root filesystem of a running instance.” Source↗