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

# Snapshots

A snapshot is a named copy of a running sandbox's memory, processes, and disks. The source continues once it is taken, and new sandboxes can start from it with that state while the source sandbox exists.

## Take a Snapshot

`POST /sandbox/{id}/snapshot` snapshots a `running` sandbox. `name` is optional and need not be unique.

```json Request theme={null}
{ "name": "deps-installed" }
```

The response is `202` with the snapshot.

```json Output theme={null}
{
  "data": {
    "id": "snap-0193c4e1-5b2a-7d10-8c3f-2e4a6b8d0f12",
    "sandbox_id": "sb-us-east-1-0193c4d2-7f1a-7c2e-9d4b-5a6e8f0c1b2d",
    "name": "deps-installed",
    "phase": "Preparing",
    "failure_cause": null,
    "created_at": "2026-11-11T19:12:40Z",
    "updated_at": "2026-11-11T19:12:40Z"
  }
}
```

`phase` moves through the steps of the copy and ends at `Published` when the snapshot is usable, or `Failed` with a `failure_cause`. A larger memory size takes longer, from about 10 seconds to about a minute. The source's processes stand still while its memory is copied, about 6 to 10 seconds at 1 GiB, and its state reads `running` throughout.

A paused sandbox cannot be snapshotted. A snapshot request while a pause or another snapshot is in progress is refused with `409 operation_in_progress`.

## Create from a Snapshot

`from` starts a new sandbox with the snapshot's state.

```json Request theme={null}
{
  "from": {
    "snapshot": "snap-0193c4e1-5b2a-7d10-8c3f-2e4a6b8d0f12"
  },
  "name": "retry-1",
  "timeout": 600
}
```

* **Fields.** Only `name`, `tags`, `timeout`, `idle_timeout`, and `region` may be given with `from`. The image, the sizes, the environment, and the network policy are the source's.
* **Timeouts.** An omitted `timeout` or `idle_timeout` is copied from the source.
* **Identity.** The new sandbox receives a new machine ID, new SSH host keys, and new entropy.
* **Batches.** `POST /sandbox/batch` accepts `from`, to start many sandboxes from one snapshot.

A snapshot that is not yet `Published` is refused with `409 snapshot_not_published`. A snapshot whose source has terminated is refused with `409 source_terminated`.

## Manage Snapshots

| Request | Effect |
| - | - |
| `GET /sandbox/{id}/snapshot` | Lists the sandbox's snapshots, newest first. |
| `GET /sandbox/{id}/snapshot/{snapshot_id}` | Returns one snapshot. |
| `DELETE /sandbox/{id}/snapshot/{snapshot_id}` | Deletes the snapshot. Returns `204`. |

A sandbox holds at most three snapshots. A fourth is refused with `409 snapshot_quota` until one is deleted and the host has removed its checkpoint, shortly after the delete. Pauses and forks do not count against the cap.

A snapshot belongs to its source sandbox and is removed when the source terminates. Its record can read `Published` for a few minutes afterwards, while a create from it is refused with `409 source_terminated`. To keep a ready state beyond one sandbox, use a [template](https://developers.telnyx.com/docs/edge-compute/sandboxes/organization-resources/templates.md). A snapshot published as a template Preview will keep a sandbox's live state after it terminates.

## Snapshots, Pauses, and Forks

| Operation | Source Afterwards | Result |
| - | - | - |
| Pause | Stopped, resumable | The same sandbox, resumed later |
| Snapshot | Running | A named state for new sandboxes while the source exists |
| Fork | Running | New sandboxes now |
