Vercel Uncaps Blob Stores, Then Meters Creating One

Vercel removed the per-plan limit on how many Blob stores a team can create, then turned creating one into a billed operation, according to a Sept. 23, 2026 changelog entry from engineer Agustin Falco (Vercel changelog, Sept. 23, 2026). Hobby teams were capped at 100 stores, Pro at 500, Enterprise at 1,000; all three caps are gone.

What changed

Vercel Blob is the platform’s object storage product, built for files like uploads, exports and generated images rather than rows in a database. Until now, the store count caps pushed most teams toward one store per project, using folder-style pathname prefixes to separate data within it.

Falco’s post reframes the store itself as a boundary, not just a bucket. With no cap, Vercel suggests creating a store per environment so production, staging and preview each get their own credential, or a store per customer in a multi-tenant app so one tenant’s data can be exported or deleted in a single call. A temporary store for a preview branch or a migration is now cheap to spin up and delete when done.

That flexibility isn’t free to create. Store creation now counts as one Blob Advanced Operation: $5 per million on Pro, and on Hobby it draws down the same 2,000 free monthly operations every other Blob action already shares. Deleting a store stays free. Vercel’s post notes the underlying storage, transfer and operation costs don’t change based on how many stores the data is split across, so the store-count cap was pure friction, not cost protection, once someone actually needed the isolation.

The context

This lands a week after Vercel went the other direction on a different storage limit. A Sept. 16 changelog entry cut the 30-day grace period on Hobby deployments over the plan’s shared 10GB cap down to zero, deleting most over-limit deployments immediately instead of warning first (Vercel changelog, Sept. 16, 2026).

Read together, the two changes aren’t contradictory so much as consistent: Vercel is tightening the storage limit that costs it money to leave unenforced (old build output sitting on disk) while loosening the one that only ever protected against confusion (how many named buckets a customer’s own data lives in). Both moves shift more of Vercel’s storage surface onto metered billing rather than flat plan limits.

Our take

Uncapping Blob stores is a low-drama improvement for anyone building multi-tenant software on Vercel — a store-per-customer pattern with per-tenant delete used to mean either hitting a wall at scale or building your own logical-isolation layer on top of pathname prefixes. Charging $5 per million store creations is a reasonable way to keep that door open without inviting abuse, since almost nobody creates stores fast enough to notice the bill.

The pairing with the Hobby grace-period cut matters more than either change alone: two free-tier safety nets removed in the same eight days. Neither is severe by itself, but a Hobby team that leaned on lenient defaults for either storage type now has less room to be surprised gently.