Ctrl+Z Therapy
CasesQuick answersGuides10-minute checklistHow we testCartoonSend it in

Next.js on Vercel? Data Cache moves to Runtime Cache, and reads will cost money

Ship ItChecked against the official source

Source checked 31 Oct 2026 · Published 31 Oct 2026 · Last reviewed 31 Oct 2026 · By Ctrl+Z Therapy (how we test)

The short answer

Vercel's changelog of October 30, 2026 says Data Cache is exiting beta and moving to Runtime Cache. Next.js fetch caching and unstable_cache will switch over on every version without code changes. Once your team migrates, Data Cache reads and writes that were previously unbilled are charged at Runtime Cache pricing. Rates start at $0.40 per million read units and $4.00 per million write units, and vary by region.

What to do

  1. Review your project's Data Cache usage in Observability before you migrate.
  2. Follow Vercel's optimization guide to cut unnecessary reads and writes.
  3. Know your date: existing Hobby teams are migrated on November 29, 2026. Pro teams are notified of their migration date and when billing changes take effect.

Good to know

  • Hobby teams get 1 million read units and 200,000 write units free each month across all projects. On Pro, usage draws from your $20 infrastructure credit each month, and anything beyond it is billed at regional rates.
  • Teams created on or after October 30, 2026 use Runtime Cache by default. You can opt in early from your team's CDN settings, but Runtime Cache pricing applies as soon as you opt in.

Source

Checked on 31 Oct 2026. Prices, limits and settings change, so check the source before you rely on them.

Related