Vercel supports Next.js 16.3

Next.js 16.3 introduced immutable static assets under the path /_next/static/immutable/*. Vercel’s CDN now treats that prefix specially, reusing the same files between deployments instead of re-uploading them. For developers the change is transparent, upgrading the framework version is enough, but it only applies to assets generated by Next.js and will not affect custom static files placed elsewhere. Projects that do not use Next.js or that disable the immutable flag will not benefit from the reduced CDN traffic.

The platform also overhauled how route metadata is cached: individual segment entries are merged into JSONL-formatted shards, and both in-process and remote caches were tuned around those shards. This reduces cache-miss rates and halves the p99 time-to-first-byte for route resolution on large sites. No code changes are required, but the improvement is limited to deployments that use Vercel’s Build Output API; other hosting environments will continue to see the older, slower lookup path.

Vercel added observability hooks that label prefetch requests and surface ISR revalidation events, including both time-based and on-demand triggers. Engineers can query these signals via the Vercel Observability UI or the query builder, giving concrete metrics for performance tuning and security monitoring. The data is only available on Vercel-hosted deployments, so self-hosted or alternative CDNs will not have the same visibility.

From a security perspective, immutable assets remove the possibility of serving outdated, potentially vulnerable code after a redeploy, because the browser cache is guaranteed to match the current deployment version. Faster, more reliable route metadata reduces the chance of routing errors that could expose internal endpoints. The new observability layers let teams detect unexpected prefetch spikes or ISR revalidations that might signal abuse or misconfiguration, though they rely on Vercel’s logging pipeline.

Overall, the changes lower operational overhead: fewer CDN requests, smaller payloads, and quicker deployments because unchanged assets are skipped. Engineers gain clearer insight into runtime behavior without adding instrumentation code. The benefits stop at the Vercel platform, projects hosted elsewhere or using custom CDNs will need to implement similar caching and observability mechanisms themselves.