# Automatic persistence now in beta on Vercel Sandbox By Steven Van · 2026-03-26 Vercel Sandbox's beta SDK auto-snapshots a stopped sandbox's filesystem and restores it on resume, with no manual snapshot step. [Vercel]() Sandbox's beta SDK now saves a sandbox's filesystem automatically when it stops, and restores it when the sandbox resumes, removing the need to manage snapshots by hand. The change splits a sandbox into two parts: the sandbox itself is a persistent identity, named and tied to its filesystem state and settings, while a session is the compute that runs against it. Stopping a sandbox shuts down the session but snapshots the filesystem; resuming boots a new session from that snapshot. If a stopped sandbox receives a command, the SDK starts a new session for it automatically, so there's no need to check its status or restart it manually. Persistence is on by default in the [beta SDK]() and can be turned off per session with *persistent: false*, which leaves the sandbox resumable by name but starts each new session with a clean filesystem. Saved filesystem state is not charged; billing applies only while a session is running. [![]()]() ![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 Automatic persistence now in beta on Vercel Sandbox on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-automatic-persistence-now-in-beta-on-vercel-sandbox