Vercel Blob now supports consistent reads on private storage. Pass `useCache: false` to `get()` or `presignUrl()` to guarantee a read reflects the latest write, bypassing the CDN entirely.
The behavior depends on write history. New pathnames return fresh data immediately. Overwritten blobs can serve stale cached content for up to 60 seconds without this flag. The flag matters most for agent memory files, session transcripts, and scheduled JSON reports where stale reads cause real failures. Under the hood, `useCache: false` appends a `cache=0` query parameter, which means you can implement this manually on any private blob URL without the SDK.
The tradeoff is real: consistent reads hit the origin, run slower than cached reads, and trigger Fast Origin Transfer billing. The full documentation covers how consistent reads interact with the CDN layer and when to use each approach. If you are building anything stateful on Vercel Blob, read it.
[READ ORIGINAL →]