How Makers Build
Check my stackPlan my stack
Menu

Next.js vs React

Two sides of the frontend framework decision: react full-stack and UI library (with Vite). When each fits, what it costs, who moves from one to the other, and what makers who chose it say.

Next.jsReact full-stackllms.txtCLI
ReactUI library (with Vite)llms.txt
Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Which fits you

Choose Next.js if
  • Public pages need server rendering and you want server code in the same React project

Use it whenYou want the most tutorials and boilerplates to lean on.

Trade-offServer components and caching rules add concepts to learn, and some features work most smoothly on Vercel.

Choose React if
  • Your app lives behind a login and doesn't need search traffic

Use it whenYour app lives behind a login and doesn't need server rendering, or you want to pick routing and data libraries yourself.

Trade-offOn its own it has no routing, data loading or server rendering; you assemble those from separate libraries or move to a React framework.

At a glance

Next.jsReact
Used by1506 makers' products · 302 open-source projects199 makers' products · 1193 open-source projects
Moved to it on GitHubpull requests since Oct 202473+ from React21+ from Next.js
Downloads52M/wk+7% vs npm155.8M/wk+2% vs npm
PricingFree (open source).Free (open source, MIT).
Free tierYesYes
Open sourceYes · self-hostableYes

Who moves from one to the other

Public pull requests on GitHub since Oct 2024 whose title says "Next.js to React" or the reverse — real code changes, by developers in general rather than makers only.

React → Next.js73+ PRs
All matching pull requests on GitHub ↗
Next.js → React21+ PRs
All matching pull requests on GitHub ↗

What makers say

Makers on using it for frontend framework, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.

On Next.js
Next.js powers the imejis.io website, dashboard and the visual editor. One framework for marketing pages, the app and API routes keeps our stack small enough for two people to run.
Imejis.io, the makerSep 2026 ↗
Built the foundation for a lightning-fast product experience with modern full-stack capabilities. From performance to scalability, it helped us move from idea to execution rapidly.
Nautis, the makerSep 2026 ↗
Built the foundation for a lightning-fast product experience with modern full-stack capabilities. From performance to scalability, it helped us move from idea to execution rapidly.
Nautis, the makerJul 2026 ↗
201 more on the Next.js page →
On React
Powers our frontend. It made building an intuitive and fast interface so much easier, and its huge ecosystem gave us the confidence to experiment without worrying about running into walls.
Incerto, the makerSep 2026 ↗
React gives us the perfect balance of flexibility and performance. The component-driven structure allows clean reuse and faster iteration, and the ecosystem is richer and more battle-tested.
AidaJet, the makerSep 2026 ↗
gridland allows you to render React into both the browser and the terminal. In the browser, it renders to a custom HTML canvas. In the terminal, it renders with OpenTUI.
gridland, the makerSep 2026 ↗
96 more on the React page →

Loved and watch-outs

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

Next.js
Most loved
  • Frontend, API routes and server actions live in one codebase with a single deploy, so no separate backend is needed. PHPH 2PH 3PH 4
  • Server rendering and static generation give fast, SEO-friendly pages out of the box. PHPH 2PH 3PH 4
  • Routing, data fetching and sensible defaults come built in, so small teams skip frontend plumbing. PHPH 2PH 3PH 4
Watch-outs
  • It has quirks, complexity and undocumented behavior, and features like parallel routes do not work as documented. HN
On Product Hunt: 5.0★, 525 reviews · mentioned most: fast performance, server-side rendering, developer experience · complaints: caching issues, learning curve
React
Most loved
  • Its component model breaks complex interfaces into small reusable pieces that are easy to maintain. PHPH 2PH 3PH 4
  • The ecosystem of libraries and tools is huge and battle-tested. PHPH 2PH 3PH 4
  • The same approach carries over to web and native mobile apps. PHPH 2PH 3
On Product Hunt: 5.0★, 189 reviews · mentioned most: component-based architecture, dynamic user interfaces, flexibility

Who uses each

Next.js1506 makers' products
1752vc Pitch Deck Analyzer21stAgentCenter for OpenClawAINaveAiTermAntispaceAPIRadarAppllamaAppSignalsArtMathCodeAskiva AIAstra Security+1494 more
React199 makers' products
3D AI StudioAI SearchAidaJetAirial TravelAritectAveksanaBank Statement ConverterBasedLabs.aiBaselightBaxter Inc.Bebop.aiBeppo+187 more
Used by both — often one replacing the other, or each for a different part of the product
gridlandKanbanqMoneo AINeedleOptimizeGEO.aiPluto DoorQualGentserenitiesSwift AppTempothefrontkitVisionAR

What makers pair each with

With Next.js
Transactional Email
Database
Hosting
LLM API
With React
Payments
Transactional Email
Hosting
Web Analytics

Neither quite right?

See the whole frontend framework decision →
React RouterReact full-stackReact apps built around web standards — loaders, actions and forms — in the lineage of Remix.
TanStack StartReact full-stackType-safe routing and server functions for React or Solid, built on TanStack Router.
SvelteKitSvelte or Vue full-stackApps written in Svelte, with less boilerplate and small client bundles.
NuxtSvelte or Vue full-stackVue apps, with a large module ecosystem for auth, content, images and SEO.vs Next.js →vs React →
AstroContent-firstMarketing sites, docs and blogs that ship minimal JavaScript, with interactive islands from any UI library.vs Next.js →