Vercel switches Sandbox snapshot storage billing from monthly to daily averages

What changed

Vercel has changed how it bills for snapshot storage in Sandbox, its product for running code in isolated environments. According to a post on the Vercel blog, charges are now calculated from each day's average usage and added to the monthly invoice. Previously, Vercel derived the charge from a single average taken across the entire monthly billing period.

The per-unit price is not moving. Snapshot storage still costs $0.08 per GB-month, and Vercel says the only thing that has changed is how usage is calculated. In other words, this is a metering change rather than a rate increase.

Who is affected and when

The new calculation applies to Pro and Enterprise teams and takes effect automatically at the start of each team's next billing period. Vercel says no action is required: there is no setting to enable and no migration to perform.

Vercel has also added visibility into the new numbers. Daily charges for snapshot storage can be tracked on the team's Usage page, so teams can see how day-to-day changes in storage translate into cost.

How it can change what you pay

For a workload whose snapshot storage barely moves during the month, the switch should be close to a wash. The rate is unchanged, and steady usage averages out similarly whether it is sampled daily or monthly.

The difference shows up with variable usage. Under daily averaging, a day spent holding a large amount of snapshot storage counts fully toward the bill instead of being blended into one month-long figure. Teams whose sandbox usage comes in bursts — heavy days followed by quiet ones — may see their totals shift once the new method lands, in a direction that depends on the shape of their usage.

The Vercel post does not detail exactly how the old monthly average was sampled, so the most reliable way to compare old and new figures is the daily breakdown on the Usage page after the first billing period under the new scheme.

Why it matters

Usage-based pricing is only as useful as its granularity. A single monthly average hides when storage was held and by how much, which makes it harder to connect a cost spike back to the behaviour that caused it. Daily metering tightens that feedback loop: if a team's snapshot footprint grows because of a new workflow, the effect shows up in the invoice within days rather than being smoothed away across the month.

There is also a practical housekeeping angle. Because the change is automatic and requires nothing from customers, it is easy to miss. The first invoice after a team's next billing period begins is the moment to check that costs match expectations, particularly for anyone running bursty sandbox workloads. Nothing needs to be reconfigured, but anyone watching a budget should be aware that the meter behind the same $0.08 rate now counts differently.

For teams with flat, predictable storage, the practical impact is likely limited to better reporting. For everyone else, the change makes cost attribution sharper — and makes it worth a quick look at the Usage page before the next invoice arrives.