Next.js 16.2 Introduces Experimental Cached Navigations: Faster Page Transitions Are Coming

Next.js 16.2 Canary Lands Game-Changing Cached Navigations Feature

The Next.js team at Vercel has been quietly shipping one of the most exciting performance improvements in recent memory. The latest canary builds of Next.js 16.2 introduce an experimental cachedNavigations feature that promises to dramatically speed up client-side page transitions by caching navigation data in the segment cache.

What Is Cached Navigations?

Cached Navigations is a new experimental feature flag (experimental.cachedNavigations) that enables the Next.js router to cache the results of navigation requests — including both fully static pages and the runtime stage of partially static pages. This means that when a user navigates back to a previously visited page, Next.js can serve the cached version instantly rather than making a new network request.

The feature was introduced across several canary releases in early March 2026:

  • v16.2.0-canary.78 (March 4): Added “Cached Navigations: Cache visited fully static pages in the segment cache” and “Cache static stage of partially static initial HTML”
  • v16.2.0-canary.78: Added “Cache runtime stage data from navigation requests”
  • v16.2.0-canary.83 (March 6): Added the experimental.cachedNavigations feature flag to allow opt-in testing

How It Works

The Cached Navigations system works at the segment cache level — the same infrastructure that powers Next.js’s Partial Pre-Rendering (PPR). When a user visits a page, the router now stores the rendered output in a client-side cache. On subsequent visits to the same route, the cached data is served immediately, eliminating round-trip latency.

The caching strategy is intelligent: it differentiates between fully static pages (which can be cached indefinitely) and partially static pages (which cache the static shell while still fetching dynamic data). This ensures users always see fresh dynamic content while benefiting from instant static rendering.

How to Enable It (Experimental)

To try the Cached Navigations feature in your Next.js 16.2 canary project, add the following to your next.config.js:

/** @type {import('next').NextConfig} */
const nextConfig = {
  experimental: {
    cachedNavigations: true,
  },
};

module.exports = nextConfig;

Note: This is an experimental feature available only in canary builds. It is not yet available in stable Next.js releases and the API may change before general availability.

Why This Matters

Navigation performance is one of the most impactful factors in user experience. Studies consistently show that faster page transitions lead to higher engagement and lower bounce rates. With Cached Navigations, Next.js is taking a significant step toward making multi-page applications feel as snappy as single-page applications — without sacrificing the SEO and performance benefits of server rendering.

This feature complements other recent Next.js performance investments, including:

  • Turbopack — the Rust-based bundler now powering 100% of Next.js builds in development
  • Partial Pre-Rendering (PPR) — serving static shells instantly while streaming dynamic content
  • Prefetch inlining — embedding prefetch data directly in the initial HTML response

What’s Next for Next.js 16.2

The 16.2 canary series has been extremely active, with daily releases pushing improvements to Turbopack, routing, and caching. Based on the current trajectory, Next.js 16.2 stable is expected to ship with Cached Navigations as a production-ready feature, potentially making it one of the most impactful releases since Next.js 15 introduced the App Router stability improvements.

Developers building performance-critical applications should keep a close eye on this feature as it matures through the canary channel.

Key Takeaways:

  • Next.js 16.2 canary introduces experimental.cachedNavigations for faster page transitions
  • The feature caches both fully static and partially static page navigation data
  • Available now in canary builds via the experimental.cachedNavigations: true flag
  • Builds on top of the existing segment cache and PPR infrastructure
  • Expected to ship as stable in the Next.js 16.2 release

Hashtags: #NextJS #React #WebDevelopment #JavaScript #Performance #Vercel #WebPerformance #FrontendDev

Sources & References:

Search

Categories

Archives