Astro vs Next.js
Of the 2,289 makers' products we know the frontend framework of, 1,731 chose Next.js (76%) and 270 Astro (12%); 19 use both. Among the 452 launched in 2026, Astro is in 13% and Next.js in 78%, against 10% and 71% of those launched in 2024 or earlier. They're different kinds of tool, content-first and react full-stack, so the counts don't measure the same choice. On GitHub, 48 public pull requests moved projects from Astro to Next.js, and 178 the other way: more move to Astro, though fewer products use it in total.
Two sides of the frontend framework decision: content-first and react 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
- You're building a marketing site, docs or a blog
Use it whenMost pages are content and only a few parts need to be interactive.
Trade-offNot designed for app-like dashboards with lots of client-side state.
- 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.
At a glance
| Used by | 270 makers' products · 80 open-source projects | 1731 makers' products · 364 open-source projects |
|---|---|---|
| Moved to it on GitHubpull requests since Oct 2024 | 178 from Next.js | 48 from Astro |
| Downloads | 5.5M/wk+99% vs npm | 56M/wk+10% 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 | 10% 8 | 75% 58 | 77 |
| 2023 | 9% 5 | 82% 46 | 56 |
| 2024 | 10% 44 | 68% 288 | 423 |
| 2025 | 10% 44 | 78% 348 | 446 |
| 2026 | 13% 60 | 78% 354 | 452 |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Astro to Next.js" or the reverse — real code changes, by developers in general rather than makers only.
- 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
- 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
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.
In ASO.dev, we love using Astro Starlight theme, it’s a fantastic choice, especially for building FAQ sections. If you’re looking to optimize your site’s performance while keeping things simple and flexible, it is a great fit!
Built the iVox landing page with Astro. Fast, minimal, does exactly what a static marketing site needs to do — nothing more.
The perfect blend of speed and simplicity. Our site is built with Astro — delivering content faster and cleaner than ever.
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.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- It ships zero JavaScript by default, giving fast, SEO-friendly static pages with top Lighthouse scores. PHPH 2PH 3
- Islands let you drop in React, Svelte or other components only where interactivity is needed. PHPH 2PH 3
- Content collections, MDX and the Starlight theme make docs sites fast to build. PH
- 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
Astro or Next.js: which do makers choose?
Of the 2,289 makers' products we know the frontend framework of, 1,731 chose Next.js (76%) and 270 Astro (12%); 19 use both. Among the 452 launched in 2026, Astro is in 13% and Next.js in 78%, against 10% and 71% of those launched in 2024 or earlier. They're different kinds of tool, content-first and react full-stack, so the counts don't measure the same choice. On GitHub, 48 public pull requests moved projects from Astro to Next.js, and 178 the other way: more move to Astro, though fewer products use it in total. Choose Astro if you're building a marketing site, docs or a blog; choose Next.js if public pages need server rendering and you want server code in the same React project.
Can you use Astro and Next.js together?
19 makers' products we track use both, often one replacing the other or each for a different part of the product: Sell to State, UXAudit.Now, adomate, Coval, Design Foundations and others.
When should I pick Astro over Next.js?
Pick Astro if: You're building a marketing site, docs or a blog.
When should I pick Next.js over Astro?
Pick Next.js if: Public pages need server rendering and you want server code in the same React project.
Are people switching from Astro to Next.js?
Public GitHub pull requests since 2024-10-02: 48 from Astro to Next.js, 178 from Next.js to Astro.
