# Next.js 16.3 support on Vercel

DevFeed: [Next.js 16.3 support on Vercel](<https://devfeed.tech/articles/next-js-16-3-support-on-vercel-789.md>)

Original publisher: [Read original article](<https://vercel.com/blog/vercel-supports-next-js-16-3>)

Author: Mark Knichel

Published: 2026-08-04T07:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Next.js](<https://devfeed.tech/topics/next-js.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>)

Tags: [cache](<https://devfeed.tech/tags/cache.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [observability](<https://devfeed.tech/tags/observability.md>), [performance](<https://devfeed.tech/tags/performance.md>), [release](<https://devfeed.tech/tags/release.md>), [routing](<https://devfeed.tech/tags/routing.md>), [support](<https://devfeed.tech/tags/support.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel adds full support for Next.js 16.3, including immutable static asset reuse, leaner prefetching, faster route resolution, and additional observability. The article reports reduced prefetch and CDN requests, lower static-content transfer, and faster deployments for upgraded applications.

## Source excerpt

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 static assets can't suffer from version skew, even for projects without Skew Protection enabled, and the browser cache survives redeploys. Because Next.js uses query-parameter-based Skew Protection, this change cut CDN requests by 17% and bytes transferred by 24% for static content. Deployments also complete up to 30% faster on average, since unchanged assets skip re-upload. In Next.js 16.3, immutable static assets are enabled by default. Next.js 16.3 outputs immutable content-addressed static assets under the public path /_next/static/immutable/*. The Vercel CDN uses this prefix to differentiate immutable static assets from other static assets. 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