---
title: "Snapshots"
description: "Capture a sandbox and create new sandboxes from it."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.jgcp.mistrivedev.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Snapshots

:::note[Planned]
Snapshots are not available yet. The samples show the planned API.
:::

A snapshot captures the state of a sandbox. You can create any number of new sandboxes from it.

## What a snapshot includes

Set `includes` when you create a snapshot:

| Value | What the snapshot holds |
| --- | --- |
| `VOLUMES` | The sandbox's [volumes](https://docs.jgcp.mistrivedev.com/sandboxes/volumes/). |
| `DISK` | Its whole disk. |
| `MEMORY` | Its disk and memory, so processes continue where they were. |

These are the same levels a stopped sandbox reports in `preserved`. Each snapshot records the sandbox it came from, its size and, if it has one, the time it expires.

## Restore and fork

There is no separate restore call. To go back to a snapshot, create a sandbox with `source.snapshot`. To fork, do the same several times: each new sandbox starts from the same state and then runs on its own.

## Lifetime

A snapshot outlives its sandbox. Deleting the sandbox does not delete its snapshots. Delete a snapshot when you no longer need it.

You can also build a [template](https://docs.jgcp.mistrivedev.com/sandboxes/templates/) version from a snapshot, so the state you captured becomes a named environment.

:::note[Today]
Today you can snapshot only a sandbox whose home folder is on a volume, and you cannot create a sandbox from a snapshot yet.
:::

Source: https://docs.jgcp.mistrivedev.com/sandboxes/snapshots/index.mdx
