Next.js 16.4 makes Cache Components the default for new apps

Victoria Shinder08 October 2026, 07:161 min read

The Next.js team released Next.js 16.4 on 6 October, and its headline is a recommendation rather than a feature: Cache Components — the programming model introduced across the 16.x releases — is now advised for every Next.js app.

What Cache Components are. A set of features that let a developer mark parts of the component tree as eligible for caching. The release post's comparison: 'use cache' is a component-level version of the Cache-Control HTTP header. The team says the model brings fast initial loads even for personalised pages, instant client navigations for server-rendered apps, and caching that is opt-in, declarative and composable.

Why only now. Until this release the team did not recommend the model universally, because in some cases it could not match the cost and performance guarantees of the previous model. The post says 16.4 includes the features that close those gaps.

What changes for developers.

• New apps: every app created with create-next-app now has Cache Components enabled by default.
• Existing apps: a new next upgrade --agent command gives coding agents version-specific upgrade guidance, and dedicated Skills help agents with the refactoring needed to adopt Cache Components.
• The roadmap: Cache Components will become the default in Next.js 17.

For all apps, 16.4 also brings lower memory use and disk size in development, shorter compile times, smaller production bundles and React 19.3. The GitHub release lists the detailed changes, including Turbopack fixes such as stripping a leading byte-order mark before parsing CSS.