Next.js vs Nuxt
Of the 2,289 makers' products we know the frontend framework of, 1,731 chose Next.js (76%) and 28 Nuxt (1%). Among the 452 launched in 2026, Next.js is in 78% and Nuxt in 1%, against 71% and 3% of those launched in 2024 or earlier. On GitHub, 10 public pull requests moved projects from Next.js to Nuxt, and 14 the other way.
Two sides of the frontend framework decision: react full-stack and svelte or Vue full-stack. 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.
- You already know Vue, or Svelte, and need server rendering
Use it whenYou already know Vue.
Trade-offSmaller ecosystem and fewer AI-generated examples than React.
At a glance
| Used by | 1731 makers' products · 364 open-source projects | 28 makers' products · 49 open-source projects |
|---|---|---|
| Moved to it on GitHubpull requests since Oct 2024 | 14 from Nuxt | 10 from Next.js |
| Downloads | 56M/wk+10% vs npm | 2M/wk−42% vs npm |
| Pricing | Free (open source). | Free (open source). |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | Yes · self-hostable |
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 | 0% 0 | 77 |
| 2023 | 82% 46 | 2% 1 | 56 |
| 2024 | 68% 288 | 4% 16 | 423 |
| 2025 | 78% 348 | 2% 7 | 446 |
| 2026 | 78% 354 | 1% 4 | 452 |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Next.js to Nuxt" or the reverse — real code changes, by developers in general rather than makers only.
- refactor!: port the app from Nuxt 4 to Next.js 16 App RouterDarthSaul/jl-portfolio · 2026-08-11
- Migrate site from Nuxt 3 to Next.js 16 + shadcn/uikimwwk/corp-website · 2026-07-25
- Refactor portfolio from Nuxt to Next.jsslavoyar/portfolio · 2026-07-08
- feat: migrate landing page from Nuxt.js to Next.js App Router. Making use of new figma design.Timeswap-Labs/timeswap-landing · 2026-05-03
- Migrate UI from Nuxt to Next.js 16 + Catalystkenguru33/warren · 2026-05-01
- Update front-end framework from Nuxt.js to Next.jsDeepSourceCorp/good-first-issue · 2026-04-27
- refactor(nuc_dialog + nuc_loading): migrate from nuxt to next.jsNucleify/Nucleify-React-Next · 2026-04-25
- migrate from Nuxt to Next.js 15 with Tailwind v4sigstore/sigstore-website · 2026-03-16
- Migrate frontend from Nuxt 3 to Next.js + PrimeReactbeforetheshoes/theseedbed · 2026-02-17
- Migrate entire application from Vue/Nuxt to Next.js (React)toy-project-kyungsle/saving-money · 2026-02-14
- Port Next.js identity safety fixes to Nuxt core and client [OPS-898]ops-ai/Toggly.FeatureManagement · 2026-09-05
- refactor: rewrite demo site from Next.js to Nuxt 3 (Cloudflare Pages)siaamak-ghodsi/baaxi.ir · 2026-08-24
- feat: migrate portfolio from Next.js to Nuxt 3OscarGE11/oscar-garcia-portfolio · 2026-08-02
- Migrate from Next.js to Nuxt 3 with Pinia state managementskyfly200/cadence · 2026-07-28
- Migrate frontend from Next.js to Nuxt 3 (Vue) + notes serviceduongdk099/cluster-offline · 2026-05-27
- feat: migrate frontend from next.js to nuxt 4AshvinBambhaniya/nexus-tasks · 2026-04-30
- feat: M0 - migrate frontend from Next.js 16 to Nuxt.js 3kojikawazu/stamped-map-web-app · 2026-04-02
- Migrate landing from Next.js to Nuxt.jshermes-logistic/landing · 2025-12-05
- Convert Next.js app to Nuxt 3darkSalvation/bulletproof-react · 2025-11-29
- refactor: migrated from Next.JS to Nuxt.JStim-rayner/sync-wander-work · 2024-11-29
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 octrafic.com. I needed a landing page that's fast, SEO-friendly, and looks professional - Nuxt delivered all three with minimal setup. From zero to production in a weekend.
I love Nuxt 3 : no more explicit router, no need to manually write import of components and hybrid rendering is perfect to have a website + app at the same place.
My all-time favorite. After using react and even a bit Angular - I find vuejs and Nuxt so easy to set up and understand, while being so scalable and powerful. SEO is amazing too.
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
- It is a full-stack Vue framework with API endpoints and hybrid rendering, so a website and app share one project. PHPH 2PH 3PH 4
- Auto-imports and file-based routing remove boilerplate like manual router setup and component imports. PHPH 2PH 3
- The Nuxt UI component library speeds up building polished, accessible interfaces. PH
Who uses each
What makers pair each with
Neither quite right?
See the whole frontend framework decision →Questions
Next.js or Nuxt: which do makers choose?
Of the 2,289 makers' products we know the frontend framework of, 1,731 chose Next.js (76%) and 28 Nuxt (1%). Among the 452 launched in 2026, Next.js is in 78% and Nuxt in 1%, against 71% and 3% of those launched in 2024 or earlier. On GitHub, 10 public pull requests moved projects from Next.js to Nuxt, and 14 the other way. Choose Next.js if public pages need server rendering and you want server code in the same React project; choose Nuxt if you already know Vue, or Svelte, and need server rendering.
When should I pick Next.js over Nuxt?
Pick Next.js if: Public pages need server rendering and you want server code in the same React project.
When should I pick Nuxt over Next.js?
Pick Nuxt if: You already know Vue, or Svelte, and need server rendering.
Are people switching from Next.js to Nuxt?
Public GitHub pull requests since 2024-10-02: 10 from Next.js to Nuxt, 14 from Nuxt to Next.js.

