Summary
Vercel Blob now supports read-after-write consistency on private storage through a useCache: false option on get() and presignUrl(), returning the latest write instead of a possibly stale CDN-cached copy.
What changed
On July 14, 2026, Vercel Blob added a useCache: false parameter to get() and presignUrl() that bypasses CDN caching so a read reflects the most recent write on private storage.
Why it matters
Read-after-write consistency matters for workflows where an application or agent writes an object and must immediately read it back, such as pipelines that generate a file and then process it. An opt-in bypass lets developers trade cache performance for correctness only where they need it, without giving up CDN caching everywhere.
Evidence excerpt
Pass useCache: false to get() or presignUrl() for a read that reflects the latest write.