Data Cache is moving to Runtime Cache
Vercel is retiring Data Cache in favor of Runtime Cache, introducing new pricing and storage tiers across Pro and Enterprise plans starting October 30, 2026.
Vercel announced the transition of Data Cache to Runtime Cache, marking the end of Data Cache’s beta phase. Next.js fetch caching and unstable_cache will automatically migrate to Runtime Cache with each version update, requiring no code changes from developers. The shift aims to consolidate Vercel’s caching infrastructure under a single, more scalable system. Teams are encouraged to review their current Data Cache usage in Observability before the migration begins.
Pro and Enterprise plans will receive significantly increased storage allocations compared to Data Cache. Pro projects gain 8 times the previous team-wide pool storage, while Enterprise projects receive 10 times their prior allocation. Hobby teams will get 1 million free read units and 200,000 free write units monthly across all projects. Pricing for additional usage starts at $0.40 per million read units and $4.00 per million write units, with regional variations applied.
Migration timelines vary by plan. Teams created on or after October 30, 2026, will use Runtime Cache by default. Hobby teams will be migrated on November 29, 2026, while Pro teams will receive notifications about their migration dates and billing changes. Enterprise teams will be contacted directly by their account teams to coordinate migration details and pricing.
Teams can opt in early to Runtime Cache starting October 30, 2026, via CDN settings, with pricing taking effect immediately. Vercel provides tools to optimize cache usage, including an Observability dashboard to review Data Cache usage and an optimization guide to reduce unnecessary reads and writes. Developers can also use the Vercel Agent to streamline cache optimization or disable caching entirely if needed.