Next.js 16.4.6
Next.js 16.4.6 landed on November 9, 2026, and the release notes open with a warning label: this is a backport of bug fixes and does not include pending features from canary. That framing is honest, and it should set your expectations. There are three cherry-picked changes here, two of them tooling or dev-server concerns, and one that touches production request handling.
What Is Actually In It
- Tailwind pinned to 4.3.3 inside
create-next-appand the corresponding test fixtures (#101061, #101176, backported as #101307). The generator no longer resolves a floating Tailwind range, which means new projects stop inheriting whatever patch shipped most recently upstream. - Route handler responses are compressed automatically if they are not already compressed (#101280). Previously, a route handler returning a large JSON payload or an HTML fragment could ship uncompressed depending on how the response was constructed.
- Turbopack garbage collection fixes for the dev server (#100279, #100370, backported as #101308). These target memory growth during long dev sessions, which will sound familiar to anyone who has watched the dev process climb past several gigabytes after a few hours of hot reloads.
Credits go to @lukesandberg and @eps1lon. No new APIs, no deprecations, no changes to the build output contract.
Let's Not Get Carried Away
The compression change is the one that can alter behaviour. If your infrastructure already compresses at the edge, or if a route handler sets its own Content-Encoding, this patch is supposed to leave it alone: the fix only acts when the response is not already compressed. In practice, "already compressed" detection is exactly the kind of check that tends to miss a case. If you return pre-compressed bytes from a handler, or stream a response with a manually set encoding header, test that path rather than assuming it is untouched.
The second caveat is the Tailwind pin. Pinning create-next-app to 4.3.3 makes scaffolding reproducible, but it also means freshly generated projects can lag behind the Tailwind version you already use by hand. If your team is on a newer 4.x line, expect a one-line dependency edit right after scaffolding.
The Turbopack Fix Is the Interesting One
Memory behaviour in the dev server has been the least glamorous and most persistent complaint about Turbopack adoption. Two garbage collection fixes in a patch release suggests the team is treating dev-mode stability as a release blocker rather than a canary-only problem, which is the correct priority if Turbopack is the default for local development. Whether it fully closes the leak is a separate question; leaks of this shape usually take several rounds of fixes before the growth curve flattens.
Who Should Upgrade
If you run Next.js in production behind a CDN that handles compression, this patch is close to a no-op for you. Upgrade on your normal schedule: npm install [email protected]. There is no migration work, no config change, and no reason to schedule a deploy window.
If you serve large route-handler responses from your own origin without edge compression, the automatic compression is a real bandwidth win and worth verifying with a quick curl -H "Accept-Encoding: gzip" against a representative endpoint after deploying.
If you are on canary chasing features that have not been backported, this release will look thin. That is expected: the LTS line only receives fixes, and anyone waiting on newer capabilities still needs canary. Check the specific issue you care about against the backport PRs before assuming 16.4.6 covers it, because the release notes make no claim to completeness.