Vercel Blob Can Now Delete Itself, and the Free Plan Pays for the Metadata

Automatic deletion is the right feature for a storage product with a small free allowance. It also spends the smallest allowance you have.

Share
Vercel Blob Can Now Delete Itself, and the Free Plan Pays for the Metadata

Vercel Blob added automatic deletion on 17 November 2026. Pass ttlDays when writing a blob and it is deleted that many days after upload, from 1 to 730, across put, copy, putImage, multipart and presigned uploads. setTtl changes or clears a TTL on up to 1,000 existing blobs without re-uploading. Hobby includes 1 GB of storage, 10,000 simple operations and 2,000 advanced operations a month.1

The feature is straightforwardly good, and it lands against a free tier with an unusual shape: storage is the generous part and advanced operations are the scarce one. Setting a TTL spends the scarce one.2

What the free allowance actually covers

ResourceHobby includedOn-demand rate
Blob storage1 GB per month$0.023 per GB
Simple operationsFirst 10,000$0.400 per 1M
Advanced operationsFirst 2,000$5.000 per 1M
Data transferFirst 10 GB$0.050 per GB

Prices measured on 27 October 2026. Vendor plan terms, allowances and prices change without notice, so treat every figure on this page as a dated snapshot rather than a permanent fact. Where a number here differs from the vendor's own pricing page, the vendor's page is correct and the figure above is simply older than it.

According to Vercel's documentation, two thousand advanced operations sounds like a lot until you read what counts as one. Uploading, copying, listing blobs, creating a Blob store, setting a TTL, and every interaction with the Vercel dashboard when browsing a store, uploading a file or viewing blob details all count as advanced operations.

That last category catches people. A developer checking their data through the dashboard consumes the smallest budget in the product.

What a TTL costs

Setting a TTL adds one advanced operation per started 60 days, on top of the write. A 7-day TTL is one extra operation, a 61-day TTL is two, and the 730-day maximum is thirteen.

We ran the arithmetic on a few realistic workloads, and it is friendlier than it first appears. A daily export with a 7-day TTL costs one write plus one TTL operation per file, so 30 files a month is 60 advanced operations out of 2,000. That leaves room for roughly a thousand files a month before the allowance becomes the constraint.

Two things are free and worth knowing: clearing a TTL costs nothing beyond the setTtl call itself, and blobs deleted by their TTL are free to delete. Delete operations never count as advanced operations at all.

ActionAdvanced operations
Upload a blob1, plus 1 per multipart part
Set a 1 to 60 day TTL1 on top of the write
Set the 730 day maximum TTL13 on top of the write
Change or clear a TTL with setTtl1, plus the TTL charge if extended
Blob deleted by its TTLFree
Manual deleteFree
Browse your store in the dashboard1 per interaction

The multipart trap on the free plan

The documentation recommends multipart uploads for files over 100 MB, and on Hobby that recommendation has a price. A multipart upload counts as multiple advanced operations: one when starting, one per part, and one for completion.

A single 500 MB file split into five parts is seven advanced operations. Do that every day and the 2,000 monthly allowance is gone in under ten days, before a single TTL is set. Add a 7-day TTL to each and the count climbs further.

The free plan's 1 GB of storage puts a ceiling on this, so the failure mode is not a surprise bill but a hard stop: once the advanced allowance is exhausted, uploads fail. We worked through the arithmetic on a few common patterns and the pattern that breaks first is large files uploaded often, not many small files.

What about the 5 TB ceiling?

The maximum size for any single blob is 5 TB, which is far beyond anything a Hobby allowance can hold and therefore not a limit the free plan will ever meet. It matters for a different reason: it explains why multipart exists at all, and thus why the advanced-operation arithmetic matters on a plan that will never approach the size cap.

For files over 100 MB the documentation recommends multipart uploads, and each part is an operation. A team on Pro treats that as noise. A team on Hobby treats it as a budget line, and the correct instinct there is to keep individual files small rather than to optimise how they are split.

Why TTLs matter more on a small allowance

Storage at 1 GB is small enough that a forgotten backup directory or an agent that writes a transcript on every run will fill it. Automatic deletion is the mechanism that prevents that without anyone remembering to build a cleanup job.

The API surface is the part worth copying into a project now. ttlDays is accepted on put, copy, putImage, multipart and presigned uploads, so a TTL can be attached at the point where a blob is created rather than in a scheduled sweeper. In the CLI, version 65.16.0 and later takes --ttl-days on put, put-image, copy and presign, and vercel blob set-ttl changes existing blobs.

The verdict is that this is a feature a free plan needs and a free plan can afford, provided it is applied deliberately.

The downsides deserve naming. TTL metadata spends advanced operations rather than storage, which is the scarcer resource on Hobby. Dashboard browsing competes for the same allowance. Multipart uploads multiply the cost of exactly the large files the documentation recommends them for, and a TTL is awkward to adjust because widening one is not free. A poor fit for workloads whose expiry you cannot predict.

Best for session transcripts, exports and temporary uploads with a known lifetime. Not ideal where the right lifetime is genuinely unknown and will be revised repeatedly.

Frequently asked questions

How long can a Vercel Blob TTL be?
From 1 to 730 days, counted from the upload date.

Does setting a TTL cost anything?
One advanced operation per started 60 days, on top of the write.

How many advanced operations does Hobby include?
2,000 per month.

Are TTL deletions charged?
No. Blobs deleted by their TTL are free to delete, and delete operations are free.

Can I change a TTL after uploading?
Yes, with setTtl, on one URL or up to 1,000 at a time, and you can clear it entirely.

Do dashboard interactions count?
Yes. Browsing your store, uploading files and viewing blob details each count as advanced operations.

The TTL range, the supported write methods, the expiresAt field, setTtl behaviour, the CLI flags and the per-60-day operation charge are from Vercel's changelog entry of 17 November 2026. The Hobby allowances, on-demand rates, operation definitions, dashboard interaction counting, multipart behaviour, the 100 MB recommendation and the 5 TB maximum file size are from Vercel's Blob pricing documentation, read on 19 November 2026.

Sources

  1. Vercel Changelog: Blob TTLs: vercel.com/changelog/vercel-blob-now-supports-ttls-for-automatic-deletion. Used for: ttlDays 1 to 730; works on put, copy, putImage, multipart, presigned; setTtl on up to 1,000 blobs.
  2. Vercel Docs: Vercel Blob pricing: vercel.com/docs/vercel-blob/usage-and-pricing. Used for: Hobby: 1 GB storage, 10,000 simple ops, 2,000 advanced ops; TTL costs 1 advanced op per started 60 days.

All sources are the vendor's own plan or documentation pages, checked on 27 October 2026. Plan terms change without notice, so confirm current limits before you rely on them.