Next.js 16: what's new for app builders

We rebuilt this entire site on Next.js 16, so we've had a front-row seat to what the new release does well. If you're planning a new project — or wondering whether to upgrade — here's the short version, plus the details nobody puts in the release notes.

Turbopack is the default

The headline change: Turbopack now powers both development and production builds. In our experience, dev startup went from seconds to near-instant, and full production builds are roughly 3–4x faster than the Webpack days. For a small collective that ships often, that's a real quality-of-life win.

React 19 and Server Components are the baseline

Next.js 16 leans fully into React 19: async params, Server Components as the default rendering model, and stable Actions for mutations. The mental model is simpler than it sounds:

• Server Components run once, on the server, and send HTML
• Client Components opt in with "use client" when you need interactivity
• Actions handle form submissions without building an API first

The numbers from this site

Concrete numbers beat marketing, so here's what we measured on the Cerebrix site:

• Build time: roughly 3x faster than the equivalent Next 15 config
• Dev cold start: under a second on this machine
• Zero configuration changes — the speed came from upgrading, not tuning

Your mileage will vary with project size, but the direction of the change is consistent.

What stays the same

The good news is the fundamentals didn't move: file-based routing, layouts, and the app directory all work the way they did in 15. Most upgrades are a matter of updating a few APIs and letting the compiler tell you what changed.

Gotchas we hit

Three things cost us a few minutes each, so you can skip the search:

• Async APIs everywhere — params and searchParams are now promises; await them in pages and layouts
• Image defaults — stricter defaults mean a few next/image props needed explicit values
• Cached-by-default — more things are cached than before; if a page looks stale, check the fetch cache before the code

Should you upgrade?

If you're starting fresh, absolutely — the defaults are faster and the DX is better. If you're on an older version with a large codebase, the migration path is well documented, and the build-time speedup pays for the effort quickly.