Release
Next.js 16.4.6 Now Gzips Route Handlers. I Checked Streams, Downloads and Pre-Compressed Bodies
The Brief
- Next.js 16.4.6 automatically compresses route handler responses that are not already compressed.
- The release note reads: "Automatically compress route handler responses if not already compressed."
- For self-hosted apps running next start, API routes were not gzipped before this release and now are.
Why it matters
If you self-host with next start, your route handler responses are now gzipped, which changes the bytes your API sends and may affect anything that depends on the previous behaviour.
Who’s affected
- Teams self-hosting Next.js with next start
- Next.js 16 users upgrading to 16.4.6
- Next.js 16.4.6
- #nextjs
- #compression
- #gzip
- #route-handlers
- #release
Next.js 16.4.6 shipped overnight with a one-line release note: "Automatically compress route handler responses if not already compressed." If you self-host with next start , that's a real change. Your API routes were never gzipped before, and now they are. Compression and…
Timeline
Next.js 16.4.6 shipped with the route handler compression change
DEV Community: javascript
Next.js 16.4.6 Now Gzips Route Handlers. I Checked Streams, Downloads and Pre-Compressed Bodies