Vercel Sandbox now provides 64 GB of storage

Vercel has quietly doubled the storage capacity of its Sandbox environment from 32 GB to 64 GB. The change is effective immediately and applies to every sandbox, regardless of whether it was created from a Vercel-managed image, a custom image, or a configuration that still uses the deprecated runtime property. This means teams can now run larger repositories, heavier dependency trees, or data workloads that spill to disk without hitting the previous ceiling.

The cost of adopting the new capacity is zero: no rebuild, no reconfiguration, and no redeployment are required. Existing sandboxes automatically receive the additional 32 GB without any downtime or manual intervention. However, the change does not alter the underlying ephemeral nature of the sandbox filesystem; any data written to disk is still lost when the sandbox is destroyed or restarted, so persistent workloads still need to offload data to external storage services.

Where the new limit stops working is at the boundary of truly massive monorepos or datasets that exceed 64 GB. Teams working with such workloads will still need to split their projects, trim dependencies, or move data processing to external services. Additionally, the increase does not affect the CPU or memory limits of the sandbox, so disk-heavy workloads that are also CPU-bound may still encounter bottlenecks elsewhere in the environment.