Next.js vs React
Of the 2,289 makers' products we know the frontend framework of, 1,731 chose Next.js (76%) and 235 React (10%); 68 use both. Among the 452 launched in 2026, Next.js is in 78% and React in 8%, against 71% and 10% of those launched in 2024 or earlier. They're different kinds of tool, react full-stack and UI library (with Vite), so the counts don't measure the same choice. On GitHub, 21 public pull requests moved projects from Next.js to React, and 73 the other way.
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.
Which fits you
- 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.
- 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
| Used by | 1731 makers' products · 364 open-source projects | 235 makers' products · 1405 open-source projects |
|---|---|---|
| Moved to it on GitHubpull requests since Oct 2024 | 73+ from React | 21+ from Next.js |
| Downloads | 56M/wk+10% vs npm | 168M/wk+6% vs npm |
| Pricing | Free (open source). | Free (open source, MIT). |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | Yes |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the frontend framework decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2022 or earlier | 75% 58 | 13% 10 | 77 |
| 2023 | 82% 46 | 5% 3 | 56 |
| 2024 | 68% 288 | 9% 40 | 423 |
| 2025 | 78% 348 | 10% 45 | 446 |
| 2026 | 78% 354 | 8% 37 | 452 |
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.
- Migrate from Vite + React to Next.js with bilingual catalogsaraitmanar/FlashElectronicsWebsite · 2026-10-02
- Migrate from Create React App to a Next.js static exportFremen1990/react-portfolio-devthomas · 2026-09-30
- Upgrade React.dev to Next.js 15.5.26devjiwonchoi/next-agent-upgrade-dogfood · 2026-09-28
- Migrate React project to Next.jsfiqriachmada/fe-my-indekos · 2026-09-27
- Refactor: Migrate from React Native to Next.js web appRocmaDL/DebtTracker · 2026-09-27
- feat: migrate portfolio from Vite + React Router to Next.js 16CodesofAkash/Personal-Portfolio · 2026-09-27
- Migrate from Vite/React to Next.js with TypeScriptkunospw/deesprofesionalportfolio · 2026-09-26
- Migrate from Vite/React to Next.js and restructure projectvovineb/Queensy-BnB · 2026-09-25
- Migrate from Create React App to Next.js 16edboaden/chessdailypuzzle · 2026-09-23
- Migrate frontend from React to Next.js App Routernaveensnsgroups/Todo_Mern · 2026-09-23
- Migrate from Next.js web app to Expo React Native mobile app1001pranav/expenseMonster · 2026-10-01
- Convert frontend from Next.js to React + ViteAsheesh7298/customer-churn-detection-project-final · 2026-09-29
- Fix Netlify deploy error by upgrading Next.js to support React 19 stablefireflyyogaretreatbali-svg/jevel-s-by-vinza · 2026-09-26
- [FE-01] Migrate frontend from Next.js to React + Vitesaumyashah0510/Multi-Agent-Research-System-Architecture · 2026-09-26
- chore(frontend): upgrade Next.js 14 to 15 with React 19PaladinKnightMaster/ai-image-edit · 2026-09-22
- refactor: :recycle: Migrate from Next.js to Vite with React Routeralessioforte/beehive · 2026-09-17
- Migrate from Next.js to React Router with Cloudflare Workerszackdotcomputer/my-homepage · 2026-09-12
- refactor: next.js to react+vitemaat-apps/routines · 2026-09-10
- chore: upgrade Next.js 15 to 16.3.4 with React 19.2crispal94/Analyzer-shoes-AI · 2026-09-02
- Refactor: Migrate from Expo+Next.js to single responsive React PWAalonbenitzhak-alt/horse-farm-platform · 2026-08-25
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.
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.
Next.js makes building full-stack SaaS ridiculously smooth. API routes, SSR, and all the dev DX you could ask for. It’s the reason I could focus on the product and not the boilerplate.
With built-in static site generation, server-side rendering, and a vibrant community, Next.js empowers developers to deliver world-class web experiences effortlessly. Thank you, @vercel.
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.
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.
React gives us the flexibility and component-driven architecture we need to build maintainable, modular features. It’s battle-tested and backed by a huge community.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- 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
- It has quirks, complexity and undocumented behavior, and features like parallel routes do not work as documented. HN
Who uses each
What makers pair each with
Neither quite right?
See the whole frontend framework decision →Questions
Next.js or React: which do makers choose?
Of the 2,289 makers' products we know the frontend framework of, 1,731 chose Next.js (76%) and 235 React (10%); 68 use both. Among the 452 launched in 2026, Next.js is in 78% and React in 8%, against 71% and 10% of those launched in 2024 or earlier. They're different kinds of tool, react full-stack and UI library (with Vite), so the counts don't measure the same choice. On GitHub, 21 public pull requests moved projects from Next.js to React, and 73 the other way. Choose Next.js if public pages need server rendering and you want server code in the same React project; choose React if your app lives behind a login and doesn't need search traffic.
Can you use Next.js and React together?
68 makers' products we track use both, often one replacing the other or each for a different part of the product: gridland, Kanbanq, Moneo AI, Needle, OptimizeGEO.ai and others.
When should I pick Next.js over React?
Pick Next.js if: Public pages need server rendering and you want server code in the same React project.
When should I pick React over Next.js?
Pick React if: Your app lives behind a login and doesn't need search traffic.
Are people switching from Next.js to React?
Public GitHub pull requests since 2024-10-02: 21+ from Next.js to React, 73+ from React to Next.js.

