Managing Sandbox Snapshots

Capture a sandbox's state and restore it into other sandboxes.

Render Sandboxes is in public beta.

APIs, defaults, and limits might change during the beta period.

After you create a sandbox, you can capture its state in a snapshot. You can restore from a snapshot to create new sandboxes with the same prepared filesystem or resume a process from a saved state.

Snapshots are useful for reusing installed packages, preparing environments for agents, and saving progress before a sandbox terminates.

A sandbox must be actively running to capture a snapshot. Creating a snapshot does not terminate the sandbox.

Kinds of snapshots

Render supports two kinds of sandbox snapshots:

Kind	Description
Runtime snapshot	Captures the writable filesystem, along with memory and CPU state. Use this to resume running processes from their captured state in a new sandbox. Restoring from a runtime snapshot requires the exact same compute plan as the source sandbox.
Filesystem snapshot	Captures the writable filesystem only. Use this to reuse files and installed packages in a new sandbox, without preserving running processes. Restoring from a filesystem snapshot supports any compute plan.

Kind

Description

Runtime snapshot

Captures the writable filesystem, along with memory and CPU state.

Use this to resume running processes from their captured state in a new sandbox.

Restoring from a runtime snapshot requires the exact same compute plan as the source sandbox.

Filesystem snapshot

Captures the writable filesystem only.

Use this to reuse files and installed packages in a new sandbox, without preserving running processes.

Restoring from a filesystem snapshot supports any compute plan.

Capturing a snapshot

The following example captures a filesystem snapshot and waits until it's available. Replace sbx-abc123 with your sandbox's ID:

shell

$ render sandboxes snapshots create sbx-abc123 --kind filesystem --wait

The command prints the snapshot's ID and details after capture completes.

typescript

import { Render } from '@renderinc/sdk'

const sandboxes = new Render().sandboxes

const snapshot = await sandboxes.snapshots.create({
  sandboxId: 'sbx-abc123',
  kind: 'filesystem',
  wait: true
})

console.log(snapshot.id, snapshot.status)

Call snapshots.create with the source sandbox's ID and the snapshot options.

python

from render import Render

sandboxes = Render().sandboxes

snapshot = sandboxes.snapshots.create(
    "sbx-abc123",
    kind="filesystem",
    wait=True,
)

print(snapshot.id, snapshot.status)

Call snapshots.create with the source sandbox's ID and the snapshot options as keyword parameters.

python

import asyncio
from render import RenderAsync

async def main():
    sandboxes = RenderAsync().sandboxes

    snapshot = await sandboxes.snapshots.create(
        "sbx-abc123",
        kind="filesystem",
        wait=True,
    )

    print(snapshot.id, snapshot.status)

asyncio.run(main())

Call snapshots.create with the source sandbox's ID and the snapshot options as keyword parameters.

To capture a runtime snapshot instead, set the kind to runtime or omit the kind option.

The wait option waits up to five minutes for capture to complete. If you omit it, creation returns before the snapshot is available. If the wait times out, capture continues. Check the snapshot's current status before starting another capture.

Restoring from a snapshot

Restore from a snapshot by providing its ID when you create a sandbox. Each restore creates a new sandbox, preserving the snapshot for reuse.

Snapshots always belong to the same sandbox group as their source sandbox. Provide that group's ID when restoring. You can restore from a snapshot only into another sandbox in the same group.

Replace snp-abc123 with the ID returned by snapshot creation and sbg-abc123 with its sandbox group ID. You can find group IDs with render sandbox-groups list:

shell

$ render sandboxes create --snapshot-id snp-abc123 \
    --group sbg-abc123 --timeout=300 --wait

typescript

const restored = await sandboxes.create({
  snapshotId: snapshot.id,
  sandboxGroupId: snapshot.sandboxGroupId,
  timeoutSeconds: 300,
  wait: true
})

console.log(restored.id, restored.status)

python

restored = sandboxes.create(
    snapshot_id=snapshot.id,
    sandbox_group_id=snapshot.sandbox_group_id,
    timeout_seconds=300,
    wait=True,
)

print(restored.id, restored.status)

python

restored = await sandboxes.create(
    snapshot_id=snapshot.id,
    sandbox_group_id=snapshot.sandbox_group_id,
    timeout_seconds=300,
    wait=True,
)

print(restored.id, restored.status)

These examples wait until the restored sandbox is running and set a five-minute runtime timeout. You can then execute commands or manage files inside it.

Restored state and configuration

Restoring from a snapshot preserves some aspects of the source sandbox, while other settings come from the new create request or their defaults. See Configuring sandbox behavior for how to provide these settings with the CLI or SDKs.

Property	Preserved?	Notes
Filesystem	☑️
Running processes	☑️	Runtime snapshots only.
Compute plan	☑️	Preserved by default. Filesystem snapshots support choosing a different plan.
Network policy	☑️	Inherits the source sandbox's network policy, including allowlist rules. Provide a network policy when creating the restored sandbox to override it.
Environment variables	➖	New commands use newly provided variables. Resumed processes retain their environment.
Runtime timeout	☑️	Inherits the source sandbox's runtime timeout, including if disabled. The runtime timeout restarts when the sandbox is restored. Provide a runtime timeout when creating the restored sandbox to override it.
Idle timeout	☑️	Inherits the source sandbox's idle timeout, including if disabled. Provide an idle timeout when creating the restored sandbox to override it.

Restoring by name

You can name a snapshot when you capture it, then restore from it by name instead of ID:

Replace sbg-abc123 with the group ID of the source sandbox (sbx-abc123):

shell

$ render sandboxes snapshots create sbx-abc123 \
    --kind filesystem --name prepared-env --wait
$ 
$ render sandboxes create --from prepared-env --group sbg-abc123 --wait

The --from flag accepts either a snapshot name or ID. Do not combine it with --snapshot-id.

typescript

const snapshot = await sandboxes.snapshots.create({
  sandboxId: 'sbx-abc123',
  kind: 'filesystem',
  name: 'prepared-env',
  wait: true
})

const restored = await sandboxes.create({
  snapshotName: 'prepared-env',
  sandboxGroupId: snapshot.sandboxGroupId,
  wait: true
})

python

snapshot = sandboxes.snapshots.create(
    "sbx-abc123",
    kind="filesystem",
    name="prepared-env",
    wait=True,
)

restored = sandboxes.create(
    snapshot_name="prepared-env",
    sandbox_group_id=snapshot.sandbox_group_id,
    wait=True,
)

python

snapshot = await sandboxes.snapshots.create(
    "sbx-abc123",
    kind="filesystem",
    name="prepared-env",
    wait=True,
)

restored = await sandboxes.create(
    snapshot_name="prepared-env",
    sandbox_group_id=snapshot.sandbox_group_id,
    wait=True,
)

Names are case-sensitive and scoped to a sandbox group. If you reuse a name, restoring by that name uses the most recently available snapshot with that name in the selected sandbox group.

A snapshot's name must be between 1 and 64 characters and cannot begin with snp-.

Retrieving snapshot details

You can retrieve a snapshot to check its status, capture error, expiration time, and other details:

shell

$ render sandboxes snapshots get snp-abc123 --group sbg-abc123

typescript

const currentSnapshot = await sandboxes.snapshots.get({
  sandboxGroupId: snapshot.sandboxGroupId,
  snapshotId: snapshot.id
})

console.log(currentSnapshot.status, currentSnapshot.error)

python

current_snapshot = sandboxes.snapshots.from_id(
    sandbox_group_id=snapshot.sandbox_group_id,
    snapshot_id=snapshot.id,
)

print(current_snapshot.status, current_snapshot.error)

python

current_snapshot = await sandboxes.snapshots.from_id(
    sandbox_group_id=snapshot.sandbox_group_id,
    snapshot_id=snapshot.id,
)

print(current_snapshot.status, current_snapshot.error)

Lookup, listing, and deletion methods all require the snapshot's sandbox group ID.

Snapshot status

A snapshot has one of the following statuses:

Status	Meaning
`creating`	Capture is in progress. New sandboxes cannot yet be restored from the snapshot.
`available`	Capture succeeded. New sandboxes can now be restored from the snapshot.
`failed`	Capture failed. Check the snapshot's `error` field for details.

Waiting for an existing snapshot

If you captured a snapshot without waiting, you can wait for it to become available with the following approaches:

Use render sandboxes snapshots get to check the snapshot's status:

shell

$ render sandboxes snapshots get snp-abc123 --group sbg-def456

To wait in a script, call this command in a polling loop while the status is creating, pausing between checks. Stop when the status is available or failed. Add --output json to read the status programmatically.

typescript

const availableSnapshot = await sandboxes.snapshots.waitUntilAvailable({
  sandboxGroupId: snapshot.sandboxGroupId,
  snapshotId: snapshot.id
})

python

available_snapshot = sandboxes.snapshots.wait_until_available(
    sandbox_group_id=snapshot.sandbox_group_id,
    snapshot_id=snapshot.id,
)

python

available_snapshot = await sandboxes.snapshots.wait_until_available(
    sandbox_group_id=snapshot.sandbox_group_id,
    snapshot_id=snapshot.id,
)

The SDK methods wait up to five minutes by default and raise an error if capture fails or the wait times out.

Snapshot expiration

By default, snapshots expire 30 days after capture. This expiration time does not change if you use the snapshot to restore a sandbox.

Check expiresAt (TypeScript) or expires_at (Python) for an individual snapshot's expiration time. The CLI displays this value in snapshot details.

You can set an expiration time when capturing a snapshot with either SDK. The following example sets it to 24 hours from now:

typescript

const snapshot = await sandboxes.snapshots.create({
  sandboxId: 'sbx-abc123',
  kind: 'filesystem',
  expiresAt: new Date(Date.now() + 24 * 60 * 60 * 1000).toISOString(),
  wait: true
})

python

from datetime import datetime, timedelta, timezone

snapshot = sandboxes.snapshots.create(
    "sbx-abc123",
    kind="filesystem",
    expires_at=datetime.now(timezone.utc) + timedelta(hours=24),
    wait=True,
)

python

from datetime import datetime, timedelta, timezone

snapshot = await sandboxes.snapshots.create(
    "sbx-abc123",
    kind="filesystem",
    expires_at=datetime.now(timezone.utc) + timedelta(hours=24),
    wait=True,
)

The expiration time must be in the future. After a snapshot expires, you can no longer retrieve it or restore from it. Sandboxes already restored from an expired snapshot are unaffected.

Listing snapshots

List snapshots in a sandbox group to find their IDs and statuses. The following example lists snapshots that are available to restore from:

shell

$ render sandboxes snapshots list --group sbg-abc123 --status available

typescript

const entries = await sandboxes.snapshots.list({
  sandboxGroupId: snapshot.sandboxGroupId,
  status: ['available']
})

for (const { snapshot } of entries) {
  console.log(snapshot.id, snapshot.name, snapshot.status)
}

python

page = sandboxes.snapshots.list(
    sandbox_group_id=snapshot.sandbox_group_id,
    status="available",
)

for listed_snapshot in page.snapshots:
    print(listed_snapshot.id, listed_snapshot.name, listed_snapshot.status)

python

page = await sandboxes.snapshots.list(
    sandbox_group_id=snapshot.sandbox_group_id,
    status="available",
)

for listed_snapshot in page.snapshots:
    print(listed_snapshot.id, listed_snapshot.name, listed_snapshot.status)

Results are ordered newest first. Omit the status filter to include snapshots with any status. Deleted and expired snapshots are excluded.

The SDKs return one page at a time. Use the cursor from the last entry (TypeScript) or next_cursor (Python) to retrieve additional pages. For pagination options, see the TypeScript and Python references.

Deleting a snapshot

Delete a snapshot when you no longer need to restore from it:

shell

$ render sandboxes snapshots delete snp-abc123 --group sbg-abc123 --confirm

Without --confirm, the command previews the deletion and makes no changes.

typescript

await sandboxes.snapshots.delete({
  sandboxGroupId: snapshot.sandboxGroupId,
  snapshotId: snapshot.id
})

python

sandboxes.snapshots.delete(
    sandbox_group_id=snapshot.sandbox_group_id,
    snapshot_id=snapshot.id,
)

python

await sandboxes.snapshots.delete(
    sandbox_group_id=snapshot.sandbox_group_id,
    snapshot_id=snapshot.id,
)

You cannot delete a snapshot while its status is creating. Deletion prevents future restores and does not affect sandboxes already restored from the snapshot.