Vercel Blob is now generally available: Cost-efficient, durable storage

Vercel Blob hits general availability

Vercel Blob is now generally available as durable, S3-backed storage integrated with Vercel's application delivery network. The service already stores and serves more than 400 million files and powers production applications including v0 and the Vercel Dashboard. Private Blobs with scoped access also reached general availability on June 30, 2026.

Vercel built Blob around the principle that storage should be straightforward, globally distributed, and durable. The service uses Amazon S3 infrastructure, which provides 99.999999999% reliability. For context, with one billion objects stored, you could go 100 years without losing a single one.

Delivery architecture

Vercel Blob introduces Blob Data Transfer, a delivery strategy separate from Fast Data Transfer. Blob Data Transfer uses volume-optimized infrastructure across 18 hubs to serve assets at reduced cost, while Fast Data Transfer remains latency-optimized, running in 94 cities for ultra-low latency workloads.

Requests for Blob assets follow the standard Vercel request lifecycle:

1. The request is routed to the nearest Vercel Region, like any standard Vercel Edge Request

2. The Region identifies it as a Blob request and queries the Vercel cache

• On a cache HIT, it's served directly from the cache

• On a cache MISS, the asset is fetched from Blob storage using Fast Origin Transfer and stored in the cache

1. The response is returned to the user, incurring Blob Data Transfer

Because storage and delivery are unified inside Vercel's network, Blob Data Transfer and the Vercel CDN work together without needing a separate CDN.

Integration and SDK

Uploading files with the @vercel/blob SDK is a single function call. The example below creates a Vercel Function that accepts a file and returns a public URL:

import { put } from '@vercel/blob';
export async function PUT(request: Request) {
  const form = await request.formData();
  const file = form.get('file') as File;
  const blob = await put(file.name, file, { access: 'public', addRandomSuffix: true });
  return Response.json(blob);
}

Blob supports uploads up to 5TB with built-in multipart uploads, resumability, retries, and concurrency, all enabled through the Vercel Blob SDK. Developers can track progress from the client and handle large media or user-generated content without custom workarounds.

Once uploaded, files become immediately publicly available and are cached across Vercel's delivery network. Every file uses a structured path format that traces back to its storage location.

Blob URLs work directly with Vercel Image Optimization and framework-native image handling like next/image in Next.js. Transformations such as resizing, format conversion, and compression happen automatically within the same workflow. Developers can also browse and manage files in the Vercel dashboard.

import Image from 'next/image';
export default function Profile() {
  return (
    <Image
      src="https://ce0rcu23vrrdzqap.public.blob.vercel-storage.com/profiles/user-abcde-NoOVGDVcqSPc7VYCUAGnTzLTG2qEM2.png"
      width={200}
      height={200}
      alt="User profile"
    />
  );
}

Pricing model

Blob pricing is usage-based and region-specific for Pro and Enterprise customers. Storage and operation pricing match Amazon S3 rates. Blob Data Transfer is on average 3x more cost-efficient than Fast Data Transfer due to its region-optimized architecture. Free data transfer allotments have doubled since the beta period.

Image Optimization requests continue to use Fast Data Transfer, whether the source images are stored in Blob or elsewhere, because images are critical to FCP and LCP metrics and benefit from the lower-latency network. Combined with automatic format and size optimization, this can lower costs compared to serving unoptimized images over Blob Data Transfer.

Observability for Blob

The Observability dashboard now includes a dedicated Vercel Blob tab. Team-level views show total data transfer, download volume, cache activity, and API operations, with drill-downs by user agent, Vercel region, and client IP.

This visibility helps developers understand real-world usage patterns, spot inefficiencies, and optimize how applications store and serve assets.

Roadmap

Vercel continues development on Blob with upcoming features including data residency controls for choosing storage locations and improved local development tooling for offline workflows. Private Blobs with scoped access for authenticated requests have already shipped and are generally available.