Next.js 16.3.0

Vercel has released Next.js 16.3.0, the latest stable version of its React framework, on August 3, 2026. The update lands roughly a week after 16.2.12 and rolls in the tail end of the 16.3 canary line, including the Turbopack build cache that had been flagged as experimental in earlier milestones.

What Changed

The headline item is that Turbopack's build filesystem cache is now enabled by default. Previously opt-in, the cache lets repeated builds skip recompiling unchanged modules, which should cut cold-start build times on CI and local machines alike.

The release also upgrades React to the cbb046ab-20260731 build, continuing the sync cadence that has defined the 16.x series, and adds a deprecation warning for experimental.useCache — a signal that the cache API is heading toward a stable, renamed form.

Why It Matters

Prefetching got a structural rework. Next.js now attempts a static prefetch before resorting to a runtime prefetch, and the allow-runtime option has been unified with Partial Prefetching so the two no longer fight each other. For sites serving configured HTML bots, a Partial Prerendering fix ensures the right response is produced without buffering the full document.

Two reliability fixes stand out: hybrid Pages/App Router applications no longer break the not-found page when rendering through adapters, and fragment-scroll navigations stop blurring the input that triggered them. Turbopack's HMR also shares chunk versioning, diffing, and merging between browser and server, which should reduce duplicate work during development.

What's Next

With the filesystem cache on by default and the useCache deprecation in place, the 16.3 line appears to be settling toward stabilization rather than new surface area. Teams upgrading from 16.2.x should find the transition routine, though anyone relying on the old experimental.useCache behavior will want to review the deprecation warning before it is removed.

Next.js 16.3.0 is available now via npm i [email protected].