Optimized CDN caching for immutable static assets
Vercel now reuses static files across deployments for frameworks that output content-addressed assets, reducing CDN requests by 17%, lowering data transfer by 24%, and improving TTFB by 60% with zero configuration required.
Vercel now reuses static files across deployments for frameworks that output content-addressed assets. It's zero-config: Vercel uses to manage these immutable files alongside your code changes, handling the hard parts like hash collisions, file lifecycles, and efficient routing.Framework-defined infrastructure
This brings several benefits:
Vercel's supported frameworks will automatically take advantage of this optimization, even for projects without enabled. Next.js 16.3 preview and later already have it enabled out of the box, and support for additional frameworks (including Nitro) is coming soon. No configuration is required: upgrading to a supported framework version is all you need to do.Skew Protection
If you're a framework author and want to implement this in your own toolchain, see the immutable static files section of the .Build Output API docs
— For frameworks using query-parameter-based (such as Next.js), we saw 17% fewer CDN requests and 24% fewer bytes transferred for static content.Lower costs and improved cache hit ratesSkew Protection
— Deployments complete up to 30% faster on average.Faster Deployments
— Immutable assets can remain cached across deployments, giving frequently deployed projects a 60%+ global TTFB reduction.Faster Time to First Byte
Source: original entry ↗