# Sandbox persistence is now GA By Steven Van · 2026-05-26 Vercel Sandbox filesystem state now saves and restores automatically between sessions, with an opt-out for ephemeral workloads. [Vercel]() Sandboxes now save and restore their filesystem state automatically between sessions. Persistence is on by default, so there's no manual snapshot management: stop a sandbox and its filesystem is snapshotted, resume it and the snapshot restores. The [persistence]() feature is now generally available. - Every sandbox created with Sandbox.create() is persistent unless you opt out by passing persistent: false (or --non-persistent from the CLI), which discards the filesystem when the session ends. - Each sandbox gets a durable, customizable name that's unique within a project, used to create, retrieve, or resume it by name. - Resuming is automatic: calling a method like runCommand() or writeFiles() on a stopped sandbox starts a new session from the most recent snapshot. - Other additions include Sandbox.fork() to create a sandbox from an existing one, Sandbox.getOrCreate() for idempotent retrieve-or-create, and Sandbox.delete() to permanently remove a sandbox. Snapshots consume snapshot storage, billed separately from compute, so ephemeral or one-off workloads can skip persistence to keep costs down. [![]()]() ![Vercel]() Vercel The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config. [View Vercel →]() Sources [Original source]() [Read Sandbox persistence is now GA on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-sandbox-persistence-is-now-ga