Tag-based cache invalidation now available for all responses
By Steven Van ·
Tag responses with the Vercel-Cache-Tag header and invalidate them via dashboard, CLI, Function API, or REST API, free on any plan.
Vercel's CDN now supports tag-based cache invalidation on all responses, not just Next.js apps. Responses can be tagged with a comma-separated list in the Vercel-Cache-Tag header, so related content can be grouped and invalidated together instead of purging the entire cache. This complements existing caching headers like Cache-Control, CDN-Cache-Control, and Vercel-CDN-Cache-Control, and it exposes the same underlying technology that powers Next.js Incremental Static Regeneration (ISR) to any framework or backend. Vercel still recommends Next.js apps use ISR for built-in tagging and invalidation rather than managing cache headers manually.
Once a response is tagged, it can be invalidated through:
- Dashboard settings
- The Vercel CLI
- The Function API
- The REST API
Vercel's CDN reads the Vercel-Cache-Tag header and strips it before the response reaches the client. If cache tags are applied via rewrites from a parent project to a child project on the same team, the parent project's cached responses also pick up the child project's tags. This is available starting today on all plans at no additional cost.
