Next.js is one of the most popular ways to build modern websites and web apps; our own site runs on it. Version 16 brought some of the biggest changes in years. If you own a Next.js website, or you're deciding what to build on, here's what matters in plain English.

What changed in Next.js 16

ChangeWhat it means for you
Turbopack is the default bundlerMuch faster builds and development, so changes ship quicker
Cache Components (with Partial Prerendering)Pages can show static content instantly and fill in dynamic parts, helping speed
React 19.2New features such as view transitions and better background rendering
React Compiler support is stableAutomatic performance optimisation of components (opt-in)
middleware renamed to proxyA code change during upgrade; clearer purpose
Async request APIs requiredDevelopers must update older code patterns
Image component defaults changedBetter caching and security defaults; some sites need config tweaks
Node.js 20.9+ requiredOlder servers need updating
Build adapters API (alpha)Easier hosting on platforms other than Vercel
AMP support and next lint removedOld AMP pages need replacing; linting runs through ESLint directly

Why these changes matter to a business

Faster development means cheaper changes

Turbopack makes builds and local development significantly faster. Developers wait less, so the same work costs less and releases happen sooner.

Faster pages, with less compromise

Websites often had to choose between fast static pages and personalised dynamic ones. With Cache Components and Partial Prerendering, a product page can show its cached content instantly while stock levels or a personalised banner stream in. That helps Core Web Vitals and conversions.

More hosting choice

Next.js always ran on any Node.js server, but some features worked best on Vercel. The new adapters API aims to make other platforms first-class. We moved our own site from Vercel to a dedicated server with a CDN in 2026, and Next.js 16 made that straightforward.

Should you upgrade?

Your situationRecommendation
On Next.js 15 and receiving security updatesPlan an upgrade in the next few months; no emergency
On Next.js 14 or olderUpgrade soon; older versions stop getting fixes
On the Pages Router with a stable siteUpgrade the version; migrating to the App Router can be separate
Building something newStart on Next.js 16
Using AMP pagesPlan replacements before upgrading

Whatever you decide, apply security releases promptly. Next.js publishes security releases for supported versions, including one in early November 2026.

What an upgrade involves

  1. Check requirements: Node.js 20.9 or newer, TypeScript 5.1+ if used.
  2. Run the official codemod, which updates many patterns automatically.
  3. Rename middleware to proxy (or keep middleware if you rely on the edge runtime, as proxy runs on Node.js).
  4. Update async request APIs such as cookies, headers and params.
  5. Review image settings if you use query strings on local images or rely on old defaults.
  6. Check dependencies for compatibility.
  7. Test thoroughly: key pages, forms, checkout, logins, redirects and SEO tags.
  8. Measure speed before and after. Note that next build no longer prints "First Load JS" sizes; use Lighthouse or real user data instead.

A typical small marketing site takes a day or two. Complex apps with many integrations take longer.

SEO checks after any framework upgrade

Upgrades can quietly break SEO. After deploying:

Is Next.js right for your next website?

Next.js suits businesses that want a fast, custom website or web app, plan to grow features over time and have access to developers. If you need non-technical staff to manage content daily, pair it with a headless CMS. Read Next.js vs WordPress, headless CMS explained and how to choose a tech stack.

The short version

Next.js 16 made Turbopack the default for much faster builds, introduced Cache Components for pages that are both fast and dynamic, adopted React 19.2 and renamed middleware to proxy. Upgrade within a few months if you're on version 15, sooner if older, apply security releases straight away and check SEO carefully after deploying.

Need an upgrade done safely or a new site built? Our web development team builds and maintains Next.js sites, and our maintenance team keeps them patched.