# Vercel Sandbox creation now returns a ready sandbox

By Steven Van · 2026-10-08

Startup errors now surface during creation, and the change applies automatically without an SDK upgrade or configuration changes.

The first command or file operation in a new [Vercel](<https://creatorstoolbox.com/tools/vercel>) Sandbox no longer waits for snapshot restoration. That wait now happens inside Sandbox.create(), and startup errors reject the creation call instead of surfacing during the first operation.

## Readiness before the next operation

Sandbox.create() resolves once the sandbox is ready to run commands and read or write files. Code can await creation, then immediately run a command such as node --version. Creation time includes startup and any snapshot restoration.

## Timing and rollout

Creation takes about **50 ms longer at p50**, with a larger increase possible for uncached snapshots. Total time through the first operation remains the same. To compare end-to-end performance, measure from the start of creation through completion of the same first command or file operation.

The change applies automatically, with no SDK upgrade or configuration changes required. The [Sandbox.create() documentation](<https://vercel.com/docs/sandbox/sdk-reference#sandbox.create>) describes the readiness behaviour.

![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>)

[Original source](<https://vercel.com/changelog/sandbox-create-waits-until-ready>)

[Read Vercel Sandbox creation now returns a ready sandbox on Creators Toolbox](<https://creatorstoolbox.com/blog/vercel-vercel-sandbox-creation-now-returns-a-ready-sandbox>)

---
Canonical source: https://creatorstoolbox.com/blog/vercel-vercel-sandbox-creation-now-returns-a-ready-sandbox