Next.js 16.4: Cache Components now recommended for every app

Next.js 16.4 was released on 6 October 2026, and the team said for the first time that it recommends the Cache Components model for every app. New projects start with this model, and it becomes the default in Next.js 17.

What are Cache Components?

According to the release announcement, Cache Components let you mark at component level which parts of a page may be cached; the team describes it as the component-level counterpart of the HTTP Cache-Control header. A single page can then stream prepared (static) parts together with parts rendered at request time. In earlier releases the team did not recommend it universally; with 16.4 it says the remaining gaps are closed.

What is new in Next.js 16.4?

The release adds an ensureStatic setting that guarantees a page stays fully static, navigation and prefetch functions for choosing what to leave out of a prefetch, smaller Turbopack output and React 19.3. The next upgrade --agent command, which helps migrate existing apps, gives a coding agent version-specific upgrade guidance.

What it means for a business

This is developer news, but it leaves a concrete question for whoever built your site: which version is mine and what is the upgrade plan? On a framework whose caching model is changing, postponing the upgrade gets more expensive over time. We explained why security updates belong in the maintenance scope in a separate guide; if you are planning a new site, see our web design page.