Store application and agent data on Vercel

vercel blob create-store my-blob-store --access public
vercel blob put ./assets/logo.png --pathname images/logo.png --access public
vercel blob list --prefix images/ --limit 20

vercel global-config add flags --items '{"betaUiEnabled":true,"region":"sfo1"}'

vercel install neon

The right storage solution depends on your needs for latency, durability, and consistency. This table summarizes the key differences:

See best practices for optimizing your storage usage.

Vercel Blob stores generated files, user uploads, images, videos, and other large objects in public or private stores.

You should use Vercel Blob if you need to:

• Store images: For example, storing user avatars or product images
• Store videos: For example, storing user-generated video content

• Overview
• Quickstart

A Global Config is a global data store that enables you to read data in the region closest to the user without querying an external database or hitting upstream servers. Most lookups return in less than 1ms, and 99% of reads will return under 10ms.

You should use Global Config if you need to:

• Fetch data at ultra-low latency: For example, you should store feature flags in a Global Config store.
• Store data that is read often but changes rarely: For example, you should store critical redirect URLs in a Global Config store.
• Read data in every region: Global Config data is actively replicated to all regions in the Vercel CDN.

• Overview
• Quickstart
• Limits & Pricing

The Vercel Marketplace connects agents and applications to relational data, sessions, rate limits, embeddings, and semantic search through providers like Neon, Upstash, and Supabase. Vercel injects provisioned resource credentials as environment variables.

You should use Marketplace storage if you need to:

• Relational databases (Postgres): For structured data with ACID transactions, complex queries, and foreign keys
• Key-value stores (Redis): For caching, session storage, real-time leaderboards, and rate limiting
• NoSQL databases: For flexible schemas with MongoDB or DynamoDB
• Vector databases: For AI embeddings, semantic search, and recommendation systems

You can provision a Marketplace storage resource in one command with the CLI. This installs the integration, connects it to the linked project, and pulls credentials into .env.local:

vercel install neon
vercel install upstash
vercel install supabase

See vercel install for the full reference.

• Overview
• Add a Native Integration
• Provision from the CLI with vercel install
• Browse Storage Integrations

Follow these best practices to get the most from your storage:

Deploy your databases in regions closest to your Functions. This minimizes network roundtrips and keeps response times low.

Vercel's CDN caches content in every region globally. Cache data fetched from your data store on the CDN using cache headers to get the fastest response times.

Incremental Static Regeneration sets up caching headers automatically and stores generated assets globally. This gives you high availability and prevents cache-control misconfiguration.

You can also configure cache-control headers manually with Vercel Functions to cache responses in every CDN region. Note that Middleware runs before the CDN cache layer and cannot use cache-control headers.

You can bring your Blob or Global Config stores along with your account as you upgrade from Hobby to Pro, or downgrade from Pro to Hobby. To do so:

1. Navigate to the dashboard and open Storage in the sidebar
2. Select the store that you would like to transfer
3. Select Settings, then select Transfer Store
4. Select a destination account or team. If you're upgrading to Pro, select your new Pro team. If downgrading, select your Hobby team

When successful, you'll be taken to the Storage section in the sidebar of the account or team you transferred the store to.

You can transfer Marketplace resources between teams from the resource's Settings page. See Transfer a resource to another team for steps.