Vercel now reuses static files across deployments for frameworks that output content-addressed assets. The results are concrete: 17% fewer CDN requests, 24% fewer bytes transferred, deployments completing up to 30% faster, and a 60%+ reduction in global TTFB for frequently deployed projects. Next.js 16.3 preview ships with this enabled by default. Nitro support is coming.
The mechanism is Framework-defined Infrastructure handling hash collisions, file lifecycles, and routing automatically. Immutable assets stay cached across deployments instead of being invalidated on every push. No configuration required. Upgrading to a supported framework version is the entire action item.
The full changelog is worth reading for one specific reason: the breakdown of how Skew Protection interacts with query-parameter-based asset versioning, and what that means for cache hit rates at scale. Framework authors looking to implement this themselves should go straight to the Build Output API docs, immutable static files section.
[READ ORIGINAL →]