Next.js 16 for Business Websites: What Changed and When It's the Right Choice

What Next.js is, in one paragraph

Next.js is a framework built on top of React. React gives a developer the building blocks for an interactive website; Next.js adds the parts every real website needs around them: page routing, pre-built pages that load fast, image optimization, and the metadata search engines read. If a developer recommends "a custom React site", there is a good chance they mean a Next.js site. This website runs on Next.js 16.

What changed in Next.js 16

Next.js 16 was released on October 21, 2025. The changes that matter if you are paying for a site, rather than writing one:

Faster builds by default (Turbopack)

Turbopack, the tool that packages a site's code, is now stable and the default for all Next.js apps. The Next.js team says to expect 2–5x faster production builds and up to 10x faster Fast Refresh, the instant preview developers see while editing (Next.js 16 release notes). For you, that mostly means less developer time spent waiting, and quicker turnaround on small changes.

Caching is now explicit (Cache Components)

Earlier versions of the App Router cached things implicitly, which sometimes meant a page kept showing stale information after you updated it. In Next.js 16, caching through the new Cache Components model is entirely opt-in: dynamic content runs fresh on every request unless the developer deliberately caches it. That is a more predictable default. When you update a price, a listing or a blog post, you should see it, and when something is cached it is because someone chose to cache it.

Automatic performance tuning (React Compiler support)

Built-in support for the React Compiler is now stable. The compiler automatically applies optimizations developers used to write by hand. It is not switched on by default yet, because it makes builds slower, so ask your developer whether your project uses it. Our article on what React 19 means for business websites covers the React side of this.

Middleware is now "proxy"

The file that runs before every request (used for redirects, logins and similar rules) has been renamed from middleware.ts to proxy.ts. The old name still works but is deprecated. If you inherit an older Next.js site, this is one of the many small upgrade steps a developer will need to plan for.

Older setups are no longer supported

Next.js 16 requires Node.js 20.9 or newer and drops support for Node.js 18. It also removed AMP support and several older configuration options (full list). If your site is on an older Next.js version, upgrading may mean updating your hosting environment too.

Why keeping up matters: the December 2025 security advisory

In December 2025 the React team disclosed a critical vulnerability in React Server Components (CVE-2025-55182), rated 10.0 out of 10, which affected frameworks including Next.js. Patched versions were released across the Next.js 14, 15 and 16 lines, and the advice was to upgrade immediately. Sites on versions nobody was updating had no patch until someone installed one.

That is the real lesson for a business owner: a Next.js site is fast and flexible, but it is software, and it needs someone keeping it current. Ask any developer who will apply updates like this one, and how quickly. Our React and Next.js maintenance covers exactly that.

When Next.js is the right stack

• Your site needs custom functionality, such as search, booking, quoting, portals or integrations with your own systems.
• Speed and search visibility matter, and you want pages pre-built as HTML so they load quickly and are easy for search engines to read.
• You expect the site to grow into something more like an application over time.

A real example: Modern Solution Realty runs on a custom React front end with its own property search and blog management, and we have maintained it for over three years.

When it's overkill

• A brochure site your team edits often. WordPress gives non-technical staff an editing screen out of the box. See WordPress development.
• A standard online store. Shopify handles payments, checkout and inventory for you. See our Shopify vs WordPress comparison.

Questions to ask a developer who recommends Next.js

1. Which Next.js version will you build on, and how will upgrades be handled?
2. How will my team edit content? Is there a CMS, and what does it look like?
3. Where will it be hosted, and is the hosting account in my name?
4. Which pages are cached, and how quickly do my edits appear on the live site?
5. Who watches for security advisories and applies patches?

If you are deciding whether a custom build makes sense, our custom React and Next.js development page explains how we work, or contact us for a straight answer on whether you need one.