# Vercel Sandbox supports forking

By Steven Van · 2026-07-28

Sandbox.fork() clones a sandbox's latest snapshot, config and env vars, letting overrides apply per-field.

[Vercel](<https://creatorstoolbox.com/tools/vercel>) Sandbox now supports forking a running or stopped sandbox into a new one with Sandbox.fork(). The fork starts from the source's current snapshot and inherits its config and environment variables; if the source is running, the fork uses its last saved state rather than the live in-memory one. Any parameter passed to fork() overrides the inherited value, and if the source has no snapshot, the fork falls back to a fresh create using the source's runtime and config instead.

A fork takes about as long as creating a sandbox and has the same limits. Vercel suggests using it to branch an agent from a shared base, give each tenant its own copy of a template, or run variations of one setup in parallel. Forking is available in both the SDK and the CLI, via pnpm install @vercel/sandbox@latest or pnpm install -g sandbox@latest. More detail is in the [announcement](<https://vercel.com/changelog/vercel-sandbox-supports-forking>).

[![](<https://vercel.com/api/docs-og?title=JS%20SDK%20Reference&format=docs&sig=64faa92449ae0b9c480511c142e2f90fbb77bd4f7c053df84f7846f42096ba9b&category=Run%20agents%20and%20backends&subcategory=Sandbox>)](<https://vercel.com/docs/sandbox/sdk-reference#sandbox.fork>)

![Vercel](<https://www.google.com/s2/favicons?domain=vercel.com&sz=128>)

Vercel

The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.

[View Vercel →](<https://creatorstoolbox.com/tools/vercel>)

Sources

[Original source](<https://vercel.com/docs/sandbox/sdk-reference#sandbox.fork>)

[Read Vercel Sandbox supports forking on Creators Toolbox](<https://creatorstoolbox.com/blog/vercel-vercel-sandbox-supports-forking>)

---
Canonical source: https://creatorstoolbox.com/blog/vercel-vercel-sandbox-supports-forking