Next.js 16.3 support on Vercel
By Steven Van ·
Yesterday the Next.js team announced the release of Next.js 16.3, with leaner prefetching, immutable static assets, and instant navigations.
Vercel announced Next.js 16.3 support on Vercel on August 4, 2026.
What changed
Yesterday the Next.js team announced the release of Next.js 16.3, with leaner prefetching, immutable static assets, and instant navigations. As part of this release, we worked with the Next.js team to fully support 16.3 on Vercel, including better performance and additional observability. Applications that have upgraded have seen: Fewer prefetch requests: Apps upgrading from 16.2 to 16.3 saw 45% fewer prefetch requests on average, with some seeing reductions over 70%. Lower static asset costs: With immutable static assets, upgraded apps saw 17% fewer CDN requests and 24% fewer bytes transferred for static content, and up to 60% global TTFB reductions for frequently deployed projects. Faster routing at scale: Routing metadata improvements in the critical serving path deliver ~2x faster p99 route resolution for large sites. Platform improvements Next.js 16.3 ships leaner prefetching and enables immutable static assets by default. Supporting both meant changing the platform too, in how it caches static assets, resolves routes, and surfaces what happened in production. Immutable static assets Vercel now supports reusing immutable static assets across deployments for Next.js. Immutable
