This question is asked constantly and it contains a false premise. Next.js and React are not two options on a shelf. Next.js is React, with a framework around it.

Choosing Next.js is choosing React plus a set of decisions already made for you. The real question is whether you want those decisions.

What React gives you

React is a library for building user interfaces out of components. It handles one job: keeping what the user sees in sync with underlying data, efficiently, without you writing manual DOM updates.

That is genuinely all it does. It has no opinion about:

  • How URLs map to pages
  • How data is fetched
  • Where HTML is generated
  • How images are optimised
  • How page titles and meta tags are set
  • How the project is built and deployed

Each of those is left to you. That flexibility is a feature for some projects and a tax for most.

What Next.js adds

File-based routing. A file at app/about/page.tsx serves /about. No router configuration.

Rendering strategies, per route. The important one. Each page can be:

  • Statically generated at build time — fastest possible, no server needed
  • Server rendered per request — for personalised or rapidly changing content
  • Client rendered — for anything behind a login where SEO is irrelevant

Mixing these per route is the single biggest architectural advantage, and it is not something you get from React alone.

Metadata handling. Titles, descriptions, canonical URLs, Open Graph tags, generated per page, server-side, so crawlers see them.

Image optimisation. Correct sizes, modern formats, lazy loading, no layout shift — handled rather than hand-rolled.

Built-in conventions for layouts, loading states, error boundaries and not-found pages.

The SEO difference, concretely

This is the deciding factor for most business websites.

A plain React application serves something like this to the first request:

<div id="root"></div>
<script src="/bundle.js"></script>

The content appears only after JavaScript downloads, parses and runs. Google can render JavaScript, but it costs crawl budget and it is slower. Other crawlers and AI retrieval systems handle it less well or not at all. And the user stares at a blank screen while the bundle loads.

Next.js, rendering statically or on the server, delivers complete HTML with the content already in it. The crawler gets the content immediately; so does the user.

For a marketing site, blog, ecommerce store or anything else that needs to be found, this is decisive.

When plain React is right

Next.js is not always the answer. Choose React alone when:

  • The app sits entirely behind a login. No SEO requirement, and the data is personal anyway.
  • You are embedding into an existing page. A widget inside a Rails or Laravel application.
  • You need total control of the build. Unusual requirements that a framework would fight.
  • It is a desktop or mobile shell. Electron, or React Native, where there is no URL.

For an internal dashboard where every page requires authentication, the extra Next.js machinery buys you little.

Static export, which is underrated

Next.js can output a site as plain files — HTML, CSS, JavaScript — with no server component at all.

The consequences are good:

  • Hosts anywhere, including cheap shared hosting
  • No server to crash, patch or be compromised
  • Near-instant page loads, since the server just hands over a file
  • Trivially easy to put behind a CDN

You give up server-side features: no API routes, no per-request rendering, no server-side personalisation. For a marketing site that is rarely a loss, and this site is built exactly that way.

What Next.js costs you

Honesty requires naming the downsides.

Conceptual surface area. Server components, client components, the boundary between them, caching behaviour, and when each rendering strategy applies. This genuinely takes time, and the model has changed more than once.

Opinions you may disagree with. Frameworks make choices. When yours differs, you work around it.

Framework churn. Next.js has had significant architectural shifts. Upgrades have occasionally been real work rather than a version bump.

Vercel gravity. Next.js is made by Vercel, and the smoothest path leads there. It runs fine elsewhere, including as a static export on shared hosting, but the default documentation assumes Vercel.

The decision, simply

Ask one question: do these pages need to be found in search?

  • Yes → Next.js, or an equivalent meta-framework.
  • No, it is behind a login → plain React is fine, and simpler.

Then a second: does it need a server at all?

  • No → Next.js with static export. Cheapest, fastest, most robust.
  • Yes → Next.js with server rendering on the routes that need it.

For most business websites the answers are yes and no, which lands on a Next.js static export — fast, cheap to host, and fully crawlable.

If you are planning a build and want a view on which fits, tell us what you are making.