“Shoutout to Next.js for pushing the boundaries of web performance! With Turbopack, Dokploy builds are now faster and smoother than ever. Thanks for redefining the dev experience!”
Frontend FrameworkMaker says so +2 · source ↗
Next.js
React framework for server-rendered and static web apps, with file-based routing, API routes, and built-in bundling.
1,731 makers' products we track use Next.js. For frontend framework it's the most chosen of 15 options: 1,731 of the 2,289 makers' products we know the frontend framework of (76%). Among the 452 launched in 2026, 78% chose it, against 71% of those launched in 2024 or earlier. 364 open-source projects also declare it in their code. What makers like most: Frontend, API routes and server actions live in one codebase with a single deploy, so no separate backend is needed. Their most common complaint: It has quirks, complexity and undocumented behavior, and features like parallel routes do not work as documented. On GitHub, 204 public pull requests moved projects to Next.js from tools we list, and 348 moved them away.
Profile checked
Works with AI agents:llms.txtCLI- Oct 2026 1372 more makers' products found using Next.js (now 1731).
How makers use Next.js
Makers' products we track use Next.js for frontend framework (1,731), most often alongside Vercel (63%), Resend (29%), Stripe (20%).
What Next.js is used for
Next.js vs the alternatives makers chose
For frontend framework, 1,731 of the 2,289 makers' products we know the choice of picked Next.js (76%), the most of 15 options. Among those launched in 2026 it's 78%.
| Option | Makers' products | 2026 launches | Open source | |
|---|---|---|---|---|
| 1,731 76% | 78% | Yes | ||
| 270 12% | 13% | Yes | Compare → | |
| 235 10% | 8% | Yes | Compare → | |
| 67 3% | 2% | Yes | ||
| 43 2% | 1% | Yes | ||
| 28 1% | 1% | Yes | Compare → |
For frontend framework: how many of the 2,289 makers' products we know the frontend framework of chose each option, and the share among the 452 launched in 2026, since a tool that came first has products from every year.
Often paired with
Share of the 1,731 makers' products on Next.js that show this choice.Markets that build with it most
Product Hunt markets where Next.js is in far more of the stacks we know than across every market (23%).
When to use Next.js, and when not
Pick Next.js if
- Public pages need server rendering and you want server code in the same React project. Frontend Framework →
Next.js is a React framework for full-stack web apps. It adds file-based routing, server rendering, static generation, API endpoints and a configured build pipeline around React, so one project covers both the pages and the server code behind them.
More about Next.js
New projects use the App Router: folders under app/ define routes, layouts nest, and components are React Server Components by default, so they can read a database directly and only send rendered output to the browser. Components marked "use client" run in the browser, and Server Functions handle form posts and mutations. The older Pages Router is still supported for existing apps.
For a small team the useful parts are per-route choice between static, cached and dynamic rendering (with incremental regeneration of static pages), built-in image, font and metadata handling, and middleware-style request handling through a proxy file. It deploys as a Node.js server or Docker container with every feature, as a static export with a reduced set, or through platform adapters.
The main limits are conceptual weight and hosting nuance. Server versus client components and the caching rules take time to learn, and once you run more than one instance you have to share the cache and Server Function encryption key yourself; on other platforms, feature support depends on their integration.
How Next.js itself is built
14 tools, from its own code, website and Product Hunt page.
Next.js pros and cons
What makers like most: Frontend, API routes and server actions live in one codebase with a single deploy, so no separate backend is needed. Their most common complaint: It has quirks, complexity and undocumented behavior, and features like parallel routes do not work as documented.
Pros
- 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
- Makers credit it with shipping MVPs and SaaS products quickly. PHPH 2PH 3PH 4
Cons and watch-outs
- It has quirks, complexity and undocumented behavior, and features like parallel routes do not work as documented. HN
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.
5.0★ from 529 reviews on Product Hunt ↗What Hacker News says about Next.js
On Hacker News, 4% of comments about Next.js recommend it and 18% criticize it: net praise −14%, 13th best liked of 14 tools HN discusses for frontend framework. Commenters chose it 2.3× as often per month in 2026 as in 2025.
By year
| Year | Comments choosing it, per month | Net praise |
|---|---|---|
| 2023 | 15 | −8% |
| 2024 | 19 | −16% |
| 2025 | 16 | −24% |
| 2026 (8 mo) | 35 | −4% |
In their words
- “I recommended some to simply learn HTML, CSS, JavaScript and then React, Next.js or Node, Express etc.” HN, May 2024
- “Personally I'm at the most productive state when working with Next.js + TailwindCSS & Prisma.” HN, May 2024
- “I found myself moving away from vercel and next.js whenever I start a new project.” HN, Apr 2026
Hacker News comments January 2023 to August 2026 that name Next.js in a sentence like "I use" or "we moved to", Claude read a sample of 100 and the counts scale it to all of them; net praise is comments recommending it minus comments criticizing it, as a share of all comments about it. How it's counted, and how HN compares with makers.
Reliability and open issues
The most wanted open issue on GitHub has 328 👍.
Most wanted on GitHub
- [NEXT-1151] App router issue with Framer Motion shared layout animations👍 328 · opened May 2023 · active Sep 2026
- RSC and CDN interaction makes next.js inefficient for highload projects👍 116 · opened May 2024 · active Jul 2026
- Add `app/` directory support for custom title in Error page👍 86 · opened Feb 2023 · active Oct 2025
- [ESLint v10]: TypeError: contextOrFilename.getFilename is not a function when running ESLint v10👍 82 · opened Feb 2026 · active Sep 2026
- Inconsistent CSS resolution order with App Router👍 69 · opened Apr 2024 · active Sep 2026
Who switches
More projects move away from Next.js: 204 pull requests in, 348 out; the most come from React and leave for Astro.
React → Next.js73+ PRs
- 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
React Router → Next.js49 PRs
- feat: migrate portfolio from Vite + React Router to Next.js 16CodesofAkash/Personal-Portfolio · 2026-09-27
- Migrate from Vite + React Router to Next.js App Routerchathurrsan-aram/aramrecruitment · 2026-09-06
- refactor!: migrate React Router SPA to Next.js App Router (public site + admin CMS unified, src/pages -> src/features, localStorage repo unchanged)tenSunFree/travel-audio-guide-nextjs · 2026-08-03
- Migrate from React Router to Next.js App Routerkebo3868-dev/Winnersbookmark-Incorporated- · 2026-07-11
- feat: Migrate frontend from Vite/React Router to Next.js App Routeriamdevlucas123/Quantum_Ed · 2026-07-06
- chore: migrate from Vite/React Router SPA to Next.js 16 App Routernicolasnunescampos-code/native-english-dashboard · 2026-07-02
- Migrate from Vite/React Router SPA to Next.js 15 App Routerdczii/Tyme · 2026-06-25
- Migrate from React Router + Vite to Next.js App RouterAkshatg102002/Optimantix-Global-Next · 2026-06-24
- feat: Migrate frontend from Vite/React Router to Next.js 16 + TypeScr…rashaduldev/Tourist-Guide-Client · 2026-06-13
- Migrate from Vite/React Router to Next.js with Supabase backendjasperkoningnl/vakantie · 2026-06-04
Astro → Next.js48 PRs
- Convert website from Astro to Next.js (App Router)digigrow100/The-Road-Rescue-Guys · 2026-09-15
- Migrate from Astro to Next.js 16 with App Routert-aize/portfolio · 2026-09-08
- Migrate docs-site from Astro Starlight to Fumadocs on Next.jsyeager-j/pdx-ts-sdk · 2026-08-20
- Migrate site from Astro to Next.js and publish Creator Bundle.axce-022/ShiftedInteriors · 2026-08-10
- Migrate from Astro to Next.js (App Router) + Reactluisgraterol/vinclorealestate.com · 2026-07-24
- Migrate site from Astro to Next.js App Routerdylanfernandezdelara/dylanfdl_website · 2026-07-21
- Migrate the Personal Site from Astro to Next.jsmarco-machado/marcomachado-dev · 2026-07-18
- feat: port gurukul from Astro to Next.js App Routerdevalok-design/gurukul · 2026-07-12
- Migrate marketing site (apps/web) from Astro to Next.jsletmepost/letmepost.dev · 2026-07-07
- Migrate Astro site to Next.js 15 App RouterLetMeHelpYouREALTY/sunstonelasvegashomes.com · 2026-07-06
Nuxt → Next.js14 PRs
- 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
SvelteKit → Next.js11 PRs
- feat(shop): Migrate core ordering flow from SvelteKit to Next.jsAgustin-Perezz/pedifast · 2026-09-28
- Migrate SvelteKit web app to Next.jsnu31hackerspace/prismo · 2026-08-05
- Migrate from SvelteKit to Next.js with App Routeralexisbohns/melogram · 2026-07-10
- Rewrite from SvelteKit to Next.js (static export)jerzabek/portfolio · 2026-06-29
- Migrate from SvelteKit to Next.js 15 with full e-sports redesignmatt-gree/ProjectRio-frontend · 2026-06-16
- Migrate from SvelteKit to Next.js 15 with full e-sports redesignProjectRio/ProjectRio-frontend · 2026-06-16
- feat: migrate frontend from SvelteKit to Next.js 14 App RouterAfoD3V/poke-hub · 2026-05-21
- D3: Port client portal modules from SvelteKit to Next.jsoliverstreetcreative/osc-website · 2026-04-14
- Port SvelteKit application to Next.jsalexkibler/bikeapelago · 2026-04-06
- Convert SvelteKit application to Next.js frontend-only with expandable sidebarenskiilda/webui2 · 2025-12-07
Next.js → Astro178 PRs
- Migrate from Next.js 14 to Astro 7TetraspaceW/infinite-todo-list · 2026-10-02
- feat: move from Next.js to Astrojoshuaellis/joshellis-site · 2026-10-01
- Migrate portfolio from Next.js to Astro and redesignVarithPheng/portfolio · 2026-09-28
- Migrate site from Next.js + Nextra to Astro 7victor-foster/victorsfoster.dev · 2026-09-28
- Migrate Next.js to Astroluicho9/joseluisflores · 2026-09-27
- Migrate from Next.js to Astronicholasdevries/nicholasdevries.github.io · 2026-09-25
- Migration from Next.js to Astroiamzoka/madebyzoka · 2026-09-25
- Migrate site from Next.js to Astroiamzoka/madebyzoka · 2026-09-25
- Move the study desk from Next.js to Astro islandsjondmarien/cert-study · 2026-09-22
- Redesign personal portfolio and migrate from Next.js to Astrodevalnor/maxime.io · 2026-09-16
Next.js → TanStack Start92 PRs
- Migrate from Next.js to TanStack Start with multi-language supportccallsinc-boop/aaaaaaaaa · 2026-10-01
- Move frontends from Next.js to TanStack Start + Query, with e2e tests and CImonish8805/carepulse · 2026-09-30
- Migrate from Next.js to TanStack Start and switch to pnpmkelvinguchu/astraque_softwares · 2026-09-22
- Migrate from Next.js to TanStack Startturbostarter/loading-ui · 2026-09-16
- feat(app): migrate from Next.js to TanStack StartNiftyLeague/nifty-fe-monorepo · 2026-09-11
- content: add post on migrating from Next.js to TanStack Startkulcsarrudolf/kulcsarrudolf.com · 2026-09-09
- refactor: migrate from Next.js to TanStack Startkulcsarrudolf/kulcsarrudolf.com · 2026-09-09
- feat!: Move from Next.js to Tanstack StartaXenDeveloper/vitnode · 2026-08-31
- migrated web app from next.js to tanstack starttashifkhan/BingeBeacon · 2026-08-20
- feat: migrate from Next.js to TanStack Starthaneulcha/haneulchadotcom · 2026-08-18
Next.js → React Router25 PRs
- 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
- Migrate the marketplace from Next.js to React Router 7.matthewhill8286/NextBazar-Marketplace · 2026-08-20
- 🏗️(front) migrate the frontend from Next.js to Vite and React Routersuitenumerique/conversations · 2026-08-11
- Migrate documentation site from Next.js to React Router and Vitetaskmigo/docs · 2026-08-06
- Migrate from Next.js to Vite with React Routerpeempumrapee/peempumrapee.github.io · 2026-04-22
- Migrate stats-web from Next.js to Vite with React Routerakash-network/console · 2026-02-20
- Migrate `@workflow/web` from Next.js to React Router v7vercel/workflow · 2026-02-11
- refactor: Migrate frontend from Next.js App Router to Vite and React Router.shivajee98/open-score-frontend · 2026-02-07
- Migrate app from Next.js App Router to React Router SSRpingdotgg/lawn · 2026-02-03
Next.js → SvelteKit22 PRs
- feat(web): migrate frontend from Next.js to SvelteKit 2 (Svelte 5)deus-meus/padelhive · 2026-08-29
- feat: Migrate blog from Next.js 16 to SvelteKit 2 (Svelte 5 + Tailwind CSS + Bits UI)jaeyoung0509/jaeyoung0509.github.io · 2026-08-16
- Migrate from Next.js to SvelteKittiennm99/loldle · 2026-07-25
- Converts site from Next.js to SvelteKitmanovotny/manovotny.com · 2026-07-24
- feat: Migrate entire portfolio from Next.js to SvelteKitaquinofroilan/aquinofroilan · 2026-07-17
- Migrate site from Next.js to SvelteKitKentokamoto/kentokamoto.github.io · 2026-07-10
- Migrate frontend from Next.js to SvelteKit + BunJeffreyyvdb/MusicHoarder · 2026-05-19
- feat: migrate from Next.js to SvelteKit + Svelte 5jscastanos/jscastanos-dev · 2026-05-19
- chore: migrate frontend from Next.js to SvelteKitshamwari-ai/shamwari · 2026-05-05
- Convert site from Next.js to SvelteKitifireball/reading-list · 2026-04-27
Next.js → React21+ PRs
- 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
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general.
Who uses it
1,731 makers' products, each linked to the source that shows it, and 364 open-source projects that declare it in their code. The best known on Product Hunt: Raycast (35,521 followers), Writesonic (9,263 followers), VEED (6,905 followers), Happycapy (6,371 followers), Recall (6,204 followers). 12 of the makers' products are gone now (domain lapsed, up for sale or taken down); they chose Next.js while live.
“Next.js makes it really easy to combine all facets of full-stack development in one application. Pls fix caching tho, Guillermo 🙏”
Frontend FrameworkMaker says so +2 · source ↗“Next.js enables us to build great software with stellar developer experience.”
Frontend FrameworkMaker says so +2 · source ↗“Changed the world, and my life too!”
Frontend FrameworkMaker says so +2 · source ↗“This contains the primary web app built with Next.js”
Frontend FrameworkMaker says so +2 · source ↗“We built supermemory with Nextjs. Amazing developer experience and fast iteration.”
Frontend FrameworkMaker says so +2 · source ↗“Finally frontend is fun.”
Frontend FrameworkMaker says so +1 · source ↗“The foundation of Sentra’s frontend and IDE extensions.”
Frontend FrameworkMaker says so +1 · source ↗“The framework behind our entire frontend, dashboard and docs”
Frontend FrameworkMaker says so +1 · source ↗“Next.js because it offers seamless full-stack capabilities with SSR, SSG, and API routes, optimizing performance and simplifying deployment. Its built-in TypeScript support and ease of use make it ideal for modern web development”
Frontend FrameworkMaker says so +1 · source ↗“Lightning-fast, interactive sales intelligence dashboard deployed on Cloud Run. Server-side rendering for SEO and performance.”
Frontend FrameworkMaker says so +1 · source ↗“Powers our blazing-fast dashboard and smooth interactions. Shipping updates feels instant because the framework is, too.”
Frontend FrameworkMaker says so +1 · source ↗“My fav language:D, I built my landing page built with it”
Frontend FrameworkMaker says so +1 · source ↗“We use Next.js to build fast and scalable web apps. It makes routing and server-side rendering easy.”
Frontend FrameworkMaker says so +1 · source ↗“Next.js made it possible to ship full-stack features fast; every view, API route, and real-time function is right where we need it.”
Frontend FrameworkMaker says so +1 · source ↗“App Router framework (React, server components, API routes)”
Frontend FrameworkMaker says so +1 · source ↗“The best DX among all React frameworks. If you want to ship fast that's what you should use.”
Frontend FrameworkMaker says so +1 · source ↗“Full-stack React framework powering our frontend and backend APIs for seamless development.”
Frontend FrameworkMaker says so +1 · source ↗“Next.js was the obvious choice for Pluto Door’s website. The App Router, file-based routing, and Server Components let us keep the frontend, API routes, and logic like payments, downloads, and emails in a single codebase. We use SSG for marketing pages, server routes for APIs, and client components for interactivity. Compared to Gatsby, Remix, or plain React, Next.js gave us the most with the least setup — letting us ship fast and worry less.”
Frontend FrameworkMaker says so +1 · source ↗“App Router + Server Components = fast SSR without the complexity. API routes keep everything in one repo.”
Frontend FrameworkMaker says so +1 · source ↗“Flashy React 19 and server components in the flesh”
Frontend FrameworkMaker says so +1 · source ↗“Built our dashboard and even API in Next.js”
Frontend FrameworkMaker says so +1 · source ↗“Thank Next.js for faster load times and performance”
Frontend FrameworkMaker says so +1 · source ↗“Next.js gives us the foundation to build and ship a fast, modern analytics experience across the entire Open Analytics platform.”
Frontend FrameworkMaker says so +1 · source ↗“Speed, seo and past experience (personal preference due to syntactic sugar)”
Frontend FrameworkMaker says so +1 · source ↗“Modern full-stack React with streaming and server components. Everything runs in a single codebase with serverless functions.”
Frontend FrameworkMaker says so +1 · source ↗“Used Next for all user facing pages, including landing page, blog and docs (Nextra)”
Frontend FrameworkMaker says so +1 · source ↗“We use Next.js for building our frontend and our chat interface.”
Frontend FrameworkMaker says so +1 · source ↗“Next.js is the powerhouse behind the IMGPT V2 Launch. Having serverless APIs, combined with Vercel, makes our app infra scalable, fast, and cost effective.”
Frontend FrameworkMaker says so +1 · source ↗“The backbone of the frontend, making it fast, scalable, and SEO-friendly right out of the box. Plenty starter templates to get going and get inspiration from.”
Frontend FrameworkMaker says so +1 · source ↗“Server components make it much more efficient to reason about server side rendering and using / optimising assets. It also draws a clear line between what is client / server side rendered. The App router makes routing easy and allows for a nice folder structure.”
Frontend FrameworkMaker says so +1 · source ↗“Without them none of our projects are possible.”
Frontend FrameworkMaker says so +1 · source ↗“Good for website development”
Frontend FrameworkMaker says so +1 · source ↗“Next is a framework our app is built on”
Frontend FrameworkMaker says so +1 · source ↗“The only option for modern SEO-ready monorepo fullstack web apps that allow you to ship 10x faster”
Frontend FrameworkMaker says so +1 · source ↗“Server-Side Rendering out of the box”
Frontend FrameworkMaker says so +1 · source ↗“Inititally when I started with Next.js it was purely because i had heard a lot about it and was curious what the fuss was about. Now though its become the beating heart of Kanbanq, and its made developement super easy and the end product is just so fast now i never thought it possible. I looked into Vue and other similar platforms, but next.js just seemed easier to use and its constant updates and new features kept me with them.”
Frontend FrameworkMaker says so +1 · source ↗“Next.js allows us to build complex web apps quickly and efficiently.”
Frontend FrameworkMaker says so +1 · source ↗“Our core technology — the framework that lets us build ideas as fast as we can think them.”
Frontend FrameworkMaker says so +1 · source ↗“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.”
Frontend FrameworkMaker says so +1 · source ↗“Used nextJS to build the entire frontend using the App directory.”
Frontend FrameworkMaker says so +1 · source ↗“I have been using NextJS for years and I love it! One codebase serves the dashboard, the marketing site, customer-hosted pages, and our API routes. The App Router plus server components kept the hosted pages fast without a separate backend.”
Frontend FrameworkMaker says so +1 · source ↗“Easy to use, huge community”
Frontend FrameworkMaker says so +1 · source ↗“Builded on NextJs, its help me to build Taskek.com in a few month instead of probably years”
Frontend FrameworkMaker says so +1 · source ↗“Next.js makes it super easy to manage CI/CD for my project”
Frontend FrameworkMaker says so +1 · source ↗“We utilize Next.js for its incredibly powerful frameworks and tools, which form the backbone of Lambda’s web application. Next.js enables us to develop highly performant and scalable applications with features like SSR, SSG, and seamless API integration.”
Frontend FrameworkMaker says so +1 · source ↗None of these in makers' own words.
Open source: a project that declares Next.js as a dependency in its public code — verifiable, but not necessarily a live product.
What its projects tell coding agents
AGENTS.md and CLAUDE.md examples for Next.js: real files, what they cover, a starting file →
What open-source projects' AGENTS.md and CLAUDE.md files say about Next.js, in our words — from the 93 files that name it:
Named as the web frontend, dashboard or docs site app inside a monorepo.13 files
Use App Router conventions.5 files
Read the Next.js docs bundled in node_modules before framework work; remembered knowledge may be outdated.4 files
Keep backend and server logic in separate packages; Next.js is only the web frontend or dashboard.4 files
Route browser calls to the backend through a Next.js proxy or BFF layer rather than directly.3 files
231 of the 376 open-source products built with Next.js that were worked on in the last 180 days keep instruction files for coding agents — 61%, against 53% of all the projects we read. AGENTS.md is in 186, CLAUDE.md in 138.
Alternatives to Next.js
All alternatives by situation →Further reading
Questions makers ask about Next.js
Is Next.js good for production?
1,731 makers' products we track run on it, and 12 of them have since gone (the product, not necessarily because of Next.js). On GitHub, 204 public pull requests moved projects to Next.js from tools we list, and 348 moved them away. The watch-out makers raise most: It has quirks, complexity and undocumented behavior, and features like parallel routes do not work as documented.
What is Next.js used for?
React framework for server-rendered and static web apps, with file-based routing, API routes, and built-in bundling. Makers' products we track use it for frontend framework (1,731).
What are the pros and cons of Next.js?
Pros makers name: Frontend, API routes and server actions live in one codebase with a single deploy, so no separate backend is needed. Server rendering and static generation give fast, SEO-friendly pages out of the box. Routing, data fetching and sensible defaults come built in, so small teams skip frontend plumbing. Cons: It has quirks, complexity and undocumented behavior, and features like parallel routes do not work as documented.
What are the alternatives to Next.js?
For frontend framework, the other options makers' products we track chose most are Astro (270), React (235), Vue.js (67), Svelte (43), Nuxt (28). Open source or self-hostable among them: Astro, React, Vue.js, Svelte, Nuxt. Each alternative, with the situation it fits, is on the Next.js alternatives page.
Is Next.js still popular with new products?
About as much as before: among the 452 makers' products launched in 2026 that made the frontend framework choice, 78% chose Next.js, against 71% of the 556 launched in 2024 or earlier.
Do developers switch to or away from Next.js?
On GitHub, 204 public pull requests moved projects to Next.js from tools we list, most from React (73), React Router (49), Astro (48); 348 moved them away, most to Astro (178), TanStack Start (92), React Router (25).
When should you use Next.js?
Public pages need server rendering and you want server code in the same React project (frontend framework). Something else fits better if: your app lives behind a login and doesn't need search traffic, pick React; you already know Vue, or Svelte, and need server rendering, pick Nuxt or SvelteKit.
Can I host Next.js without Vercel?
Yes. Running it as a Node.js server with next start or in a Docker container supports every feature, on any provider that runs Node or containers. source ↗
Can I export it as a static site?
Yes, with output set to export, which writes HTML, CSS and JS you can serve from any static host. Features that need a server at request time, such as Server Actions, cookies, rewrites, redirects, incremental regeneration and the default image optimizer, are not available in that mode. source ↗
Should I use the App Router or the Pages Router?
The App Router is the newer one and supports Server Components; the Pages Router is the original and is still supported. The App Router ships with built-in React canary builds, while the Pages Router uses the React version in your package.json. source ↗
How well does it run on Cloudflare or Netlify?
Those platforms ship their own Next.js integrations, which are not yet built on the official adapter API or verified by the Next.js team, so feature coverage can vary. Vercel and Bun have verified adapters that run the full compatibility test suite. source ↗
What changes if I run several server instances?
The page and data cache lives on each instance's local disk by default, so you need to configure a shared cache location. All instances also need the same Server Functions encryption key, or actions fail between instances. source ↗
Does image optimization work when self-hosted?
Yes. next/image optimizes images with no extra setup under next start; you can also plug in an external image loader or turn optimization off. source ↗
How long is a major version supported?
The current major gets features, fixes and security patches. The previous major gets only critical fixes and security updates, for two years after its initial release. source ↗
Is Next.js free?
Yes — it is free, open-source software.
Is Next.js open source or self-hostable?
Open source, and you can self-host it. source ↗
Can AI coding agents work with Next.js?
It serves an llms.txt docs index; it has an official CLI (next).
Who uses Next.js?
1,731 makers' products we track, each with a source, and 364 open-source projects declare it in their code. The best known of them on Product Hunt: Raycast (35,521 followers), Writesonic (9,263 followers), VEED (6,905 followers), Happycapy (6,371 followers), Recall (6,204 followers). source ↗