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 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.Vercel-Cache-Tag This complements existing headers that cache responses on Vercel's CDN, like , , and and exposes the same underlying technology that powers Next.js Incremental Static Regeneration (ISR) to any framework or backend.Cache-ControlCDN-Cache-ControlVercel-CDN-Cache-Control We recommend Next.js applications continue using for built-in cache tagging and invalidation without managing cache headers manually.Incremental Static Regeneration (ISR) After a response has a cache tag, you can invalidate it through , the , the , or the .dashboard settingsVercel CLIFunction APIREST API Vercel's CDN reads and strips it before sending the response to the client.

If you apply cache tags via from a parent to a child , and both projects belong to the same , cached responses on the parent project also include the…