Vercel's CDN now supports tag-based cache invalidation, giving you granular control over cached content across all frameworks and backends.

Responses can now be tagged using the Vercel-Cache-Tag header with a comma-separated list of tags as a new cache organization mechanism to group related content and invalidate it together, rather than just purging your entire cache when content changes.

This complements existing headers that cache responses on Vercel's CDN, like Cache-Control, CDN-Cache-Control, and Vercel-CDN-Cache-Control and exposes the same underlying technology that powers Next.js Incremental Static Regeneration (ISR) to any framework or backend.

We recommend Next.js applications continue using Incremental Static Regeneration (ISR) for built-in cache tagging and invalidation without managing cache headers manually.

Link to headingHow it works

After a response has a cache tag, you can invalidate it through dashboard settings, the Vercel CLI, the Function API, or the REST API.

Vercel's CDN reads Vercel-Cache-Tag and strips it before sending the response to the client. If you apply cache tags via rewrites from a parent to a child project, and both projects belong to the same team, cached responses on the parent project also include the corresponding tags from the child project.

This is available starting today on all plans at no additional cost. Read the cache invalidation documentation to learn more.