# Legacy Sandbox Persistence - Documentation

> For the complete documentation index, see [llms.txt](/llms.txt). Markdown is available with `Accept: text/markdown` and `.md` URL variants.

Source: /docs/guides/sandbox-legacy-persistence

# Legacy Sandbox Persistence

This legacy page is kept for users who still use the 1.x or beta SDK line. New SDK 2.x integrations should follow the current Sandbox documentation.

The sandbox persistence allows you to pause your sandbox and resume it later from the same state it was in when you paused it.
This includes not only state of the sandbox’s filesystem but also the sandbox’s memory. This means all running processes, loaded variables, data, etc.

Please note:

- It takes about 4 seconds per 1 GB RAM to pause the sandbox.

- It takes about 1 second to resume the sandbox.

- The data of a paused sandbox is permanently retained until you explicitly call the `kill` method.

##

[​](#pausing-sandbox)

Pausing sandbox

When you pause a sandbox, both the sandbox’s [filesystem](/docs/guides/sandbox-filesystem) and memory state will be saved. This includes all the files in the sandbox’s filesystem and all the running processes, loaded variables, data, etc.

JavaScript & TypeScript

Python

```
import { Sandbox } from 'novita-sandbox/code-interpreter'

const sandbox = await Sandbox.create()
console.log('Sandbox created', sandbox.sandboxId)

// Pause the sandbox.
// You can save the sandbox ID in your database
// to resume the sandbox later
const result = await sandbox.betaPause()
console.log('Sandbox paused', sandbox.sandboxId, result)

await sandbox.kill()
```

Note: Brief transition period after pausingPausing is an asynchronous operation. After calling `beta_pause()`, the sandbox pauses in the background.During this transition period, before the pause completes:

- Read-only operations (e.g., `get_info`, `list`): return normally; status is shown as `paused`

- Execution operations (e.g., `commands.run`, accessing sandbox public URLs): will return errors — this is expected behavior. Wait for pausing to complete before retrying (time varies with memory size, see note above)

- Resume operation (`connect`): automatically waits for the pause to complete before resuming the sandbox — no manual polling or retry needed

##

[​](#resuming-sandbox)

Resuming sandbox

When you resume a sandbox, it will be in the same state it was in when you paused it.
This means that all the files in the sandbox’s filesystem will be restored and all the running processes, loaded variables, data, etc. will be restored.

If you call `connect()` immediately after calling `beta_pause()`, `connect()` automatically waits for the pause to complete before resuming the sandbox. No manual polling is required — the entire process is transparent to the caller.

If you try to resume a sandbox that has been destroyed or does not exist:

- JavaScript SDK will throw `NotFoundError`

- Python SDK will throw `NotFoundException`

JavaScript & TypeScript

Python

```
import { Sandbox } from 'novita-sandbox/code-interpreter'

const sandbox = await Sandbox.create()
console.log('Sandbox created', sandbox.sandboxId)

// Pause the sandbox.
// You can save the sandbox ID in your database
// to resume the sandbox later
const result = await sandbox.betaPause()
console.log('Sandbox paused', sandbox.sandboxId, result)

// Resume the sandbox.
// Even if called before pausing completes, connect() automatically waits for the pause to finish.
const resumedSandbox = await sandbox.connect()
console.log('Sandbox resumed', resumedSandbox.sandboxId)

await sandbox.kill()
```

##

[​](#listing-paused-sandboxes)

Listing paused sandboxes

You can list all paused sandboxes by calling the `Sandbox.list` method and supplying the `state` query parameter.
More information about using the method can be found in [List Sandboxes](/docs/guides/sandbox-list).

JavaScript & TypeScript

Python

```
import { Sandbox, SandboxInfo } from 'novita-sandbox/code-interpreter'

const sandbox = await Sandbox.create()

// List all paused sandboxes.
const paginator = Sandbox.list({ query: { state: ['paused'] } })

// Get all paused sandboxes.
const sandboxes: SandboxInfo[] = []
while (paginator.hasNext) {
const items = await paginator.nextItems()
sandboxes.push(...items)
}

console.log('all paused sandboxes', sandboxes)

await sandbox.kill()
```

##

[​](#removing-paused-sandboxes)

Removing paused sandboxes

You can remove paused sandboxes by calling the `kill` method on the sandbox instance.

JavaScript & TypeScript

Python

```
import { Sandbox } from 'novita-sandbox/code-interpreter'

const sandbox = await Sandbox.create()
console.log('Sandbox created', sandbox.sandboxId)

// Pause the sandbox.
await sandbox.betaPause()

// Kill the paused sandbox.
await sandbox.kill()
```

##

[​](#sandbox’s-timeout)

Sandbox’s timeout

When you resume a sandbox, the sandbox’s timeout is reset to the default timeout of a sandbox - 5 minutes.
You can pass a custom timeout to the `Sandbox.connect()` method like this:

JavaScript & TypeScript

Python

```
import { Sandbox } from 'novita-sandbox/code-interpreter'

const sandbox = await Sandbox.create()

const connectedSandbox = await Sandbox.connect(sandbox.sandboxId, { timeoutMs: 60 * 1000 })
console.log('Sandbox connected', connectedSandbox.sandboxId)

await sandbox.kill()
```

##

[​](#network)

Network

If you have a service (for example a server) running inside your sandbox and you pause the sandbox, the service won’t be accessible from the outside and all the clients will be disconnected.
If you resume the sandbox, the service will be accessible again but you need to connect clients again.

Last modified on June 5, 2026