prefetchInlining

When the App Router prefetches a route, it can bundle small segment responses into a single response instead of requesting each one separately. This reduces the number of prefetch requests at the cost of duplicating some shared segment data across routes. This behavior is on by default, and most apps should leave it that way.

The experimental.prefetchInlining option lets you override this behavior or disable inlining while debugging navigation issues or measuring request volume. For most applications, there is no need to change the default behavior.

Usage

To turn off prefetch inlining, set experimental.prefetchInlining to false:

import type { NextConfig } from 'next'
 
const nextConfig: NextConfig = {
  experimental: {
    prefetchInlining: false,
  },
}
 
export default nextConfig

To override the thresholds instead of disabling inlining, pass an object. Any value you omit keeps its default:

import type { NextConfig } from 'next'
 
const nextConfig: NextConfig = {
  experimental: {
    prefetchInlining: {
      maxSize: 2048,
      maxBundleSize: 10240,
    },
  },
}
 
export default nextConfig

Reference

When you pass an object, the following options control the thresholds. Both are measured in bytes of the gzip-compressed segment response:

Lower thresholds keep more per-segment deduplication; higher thresholds inline more data and cut request count further.

Version History