Optimized CDN caching and deploying of immutable static assets
By Steven Van ·
Next.js 16.3 preview projects already get the change, with up to 30% faster deploys and 60% lower global TTFB.
Vercel now reuses static files across deployments for frameworks that output content-addressed assets, so unchanged files don't need to be rebuilt or re-uploaded on every deploy. It's zero-config: Vercel handles the hash collisions, file lifecycles, and routing itself, and the optimization applies even to projects without Skew Protection enabled.
- For frameworks using query-parameter-based Skew Protection, such as Next.js, Vercel saw 17% fewer CDN requests and 24% fewer bytes transferred for static content.
- Deployments complete up to 30% faster on average.
- Frequently deployed projects can see up to a 60% reduction in global Time to First Byte, since immutable assets can stay cached across deployments.
Next.js 16.3 preview and later have this enabled out of the box, with support for additional frameworks, including Nitro, coming soon. No configuration is needed beyond upgrading to a supported framework version, according to the announcement.
