# Vercel Blob now supports consistent reads on private storage

DevFeed: [Vercel Blob now supports consistent reads on private storage](<https://devfeed.tech/articles/vercel-blob-now-supports-consistent-reads-on-private-storage-1128.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-blob-now-supports-consistent-reads-on-private-storage>)

Author: Agustin Falco

Published: 2026-07-14T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [SDKs](<https://devfeed.tech/topics/sdks.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [JSON](<https://devfeed.tech/topics/json.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [json](<https://devfeed.tech/tags/json.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel Blob now supports consistent reads for private storage. Passing useCache: false to get() or presignUrl() bypasses cached reads so the result reflects the latest write, although the request takes longer and incurs Fast Origin Transfer. The same behavior can be enabled directly on a private blob URL with a cache=0 query parameter.

## Source excerpt

Vercel Blob now supports consistent reads on private storage. Pass useCache: false to get() or presignUrl() for a read that reflects the latest write. A blob written to a fresh pathname has no existing cached entry, so reads reflect the latest write immediately. When you overwrite a blob at an existing pathname, readers might see the cached version for up to 60 seconds. When a read must reflect the latest write, like an agent's memory file, a session transcript, or a scheduled JSON report, pass useCache: false. These reads bypass the CDN, take longer than cached reads, and incur Fast Origin Transfer. You can also bypass the cache without the SDK. Under the hood, useCache: false adds a cache=0 query parameter to the request. You can set it yourself on a private blob URL: Install the latest @vercel/blob SDK for consistent reads: Learn more in the consistent reads documentation. Read more