Next.js 16.4 Shrinks the Turbopack Cache by Up to a Quarter

What Every App Gets

Next.js 16.4 was released on October 6, 2026. Several of its changes apply to every app with no configuration:

• Turbopack's disk cache uses 20 to 25 percent less space. Most of the cached data is now compressed with Zstandard, metadata stays on LZ4 for fast lookups, and stale data is dropped more efficiently.
• Production bundles are smaller. Turbopack emits shorter CSS Module class names in production builds and shortens the internal export names that link modules together.
• Server hot reloading in development is lazy. Editing a shared server module no longer recompiles pages you are not looking at.
• The Turbopack runtime ships as one chunk shared across routes, which cuts download size and improves cache hit rates.
• React 19.3 is included, with stable View Transitions and Fragment Refs.

Cache Components Become the Recommendation

The bigger news is a recommendation. Cache Components, the opt-in caching model built around the 'use cache' directive, is now what the Next.js team recommends for every app. New projects created with create-next-app have it switched on by default, and the team says it becomes the default in Next.js 17.

16.4 also adds ensureStatic, a route setting that fails the build when dynamic content slips into a page that should stay static, and a way to keep part of a page out of a prefetch until the visitor actually navigates. For existing apps there is next upgrade --agent, which gives coding agents version-specific upgrade guidance.

What to Do With It

Moving to 16.4 is a minor version bump, npm install next@latest, and the cache and bundle gains come with it. Moving an existing app to Cache Components is a separate decision, because it changes how caching works across the whole app. It deserves its own branch and a test of the caching behavior rather than being folded into a routine upgrade. Our guide to Next.js caching layers explains what each layer does today.

One detail matters for self-hosted builds. The new experimental worker-thread mode for Turbopack's plugin runtime falls back to child processes on Node.js 24.13.1 and newer because of a Node.js bug, so switching it on changes nothing there for now.

If you run Next.js on your own infrastructure and want upgrades like this rolled out with a way back, that is what our Next.js on Kubernetes service does.

Sources

• Next.js 16.4