In short
Choose Astro if your site mainly has to inform and be found: pages are built in advance as HTML by default, and JavaScript only comes along where you ask for it. Choose Next.js if you are building an application, with logins, data per user and lots of interaction. Both can do more than their reputation suggests, so choose on the job, the team and the maintenance.
The comparison at a glance
| Criterion | Astro | Next.js |
|---|---|---|
| Strongest ground | Content, marketing, findability | Applications, dashboards, portals |
| JavaScript to the visitor | Almost none, only where needed | More, with server components as a brake |
| Findability & GEO | Static, clean HTML every crawler reads | Doable, requires more discipline |
| Interaction & app features | Separate islands, no full app | Home turf: login, data, realtime |
| Maintenance | Few moving parts | More dependencies, more frequent updates |
| Choose it when | Your site mainly has to tell and sell | Your site mainly has to do and process |
The table above gives the broad picture. Below you will read what Astro and Next.js do according to their own documentation, where they really differ, why the HTML matters for search engines and AI assistants, when to choose which, what else there is to choose from and which questions to ask beforehand. Our own site runs on Astro; for clients we also build in Nuxt and Next.js.
What is Astro?
Astro is a framework for websites that turns most of a page into plain HTML. According to the documentation, Astro renders every component to just HTML and CSS by default, and automatically strips out all client-side JavaScript. What the visitor receives is therefore a ready-made page. A text, a table or a list then costs the browser no script, only rendering.
If you do want something interactive, such as a calculator or a search box, you make it an island: a separate component that does get JavaScript. A directive sets when it loads, for example only when the browser is idle (client:idle) or only when the component comes into view (client:visible). The rest of the page stays plain HTML. Such an island may be written in React, Vue, Svelte, Preact or SolidJS, even mixed on one page.
Astro can do more than pages built in advance. By default everything is prepared at build time, but with an adapter for your server you can choose, per page, to render on request. Such a page can read and set cookies, and you can create endpoints that run as an API on the server. With server islands you load a piece of personal content separately, while the rest of the page is ready in advance. According to the documentation, those pieces load separately and in parallel.
Since 16 January 2026, the team behind Astro has worked at Cloudflare. According to the announcement, Astro stays open source under the MIT licence, its governance stays open and it remains meant for any host, not just Cloudflare.
What is Next.js?
Next.js is a framework for web applications on React. In the App Router, pages and layouts are Server Components by default: components rendered on the server and sent to the browser as output. According to the documentation, this helps to fetch data close to the source, keep secret keys out of the browser and send less JavaScript to the visitor.
Where interaction is needed, you use Client Components, with the line use client at the top of the file. You need them for anything to do with clicks, input and the browser. The documentation recommends doing this only for the components that are truly interactive, so the rest stays on the server.
That is less optional than it sounds. As soon as a file gets use client, according to the documentation, everything it imports goes to the browser too. The documentation's example: a header with a logo, a menu and a search box. Only the search box needs to run in the browser; put use client on the whole header and you send the logo and the menu as script as well. Anyone who wants to keep a Next.js site fast should watch where that boundary lies.
On the first visit, Next.js first shows the HTML as a preview of the page. Then JavaScript makes the Client Components interactive; this is called hydration. Until that is finished, something is on screen, but not everything responds. The more Client Components, the more work that is.
Next.js can also be built entirely in advance, with a static export: Next.js then creates one HTML file per page at build time, which can sit on any web server. Features that need a server do drop out, such as cookies, redirects, custom headers, Server Actions and the default image optimisation.
Where do they really differ?
| Astro | Next.js | |
|---|---|---|
| Default output | HTML pages built in advance | Server Components, rendered on the server |
| JavaScript for the visitor | None by default; only for islands | For Client Components and for running the app |
| Interaction | Per island, in the framework of your choice | Everywhere, with React |
| Needs a server | Only for pages you render on request | Yes, unless you make a static export |
| Built entirely in advance | By default | Possible, with a static export and fewer features |
| Strong at | Sites with lots of content and little interaction | Applications with logins and data per user |
The biggest difference lies in the starting point. With Astro you start from HTML and add interaction where it is needed. With Next.js you start from a React application and keep as much as possible on the server. Both can deliver a fast site; the difference is which way you have to push.
That starting point also decides where the work is. On an Astro site the work is mainly in content, layout and the few places with interaction. On a Next.js application it is mainly in what happens behind the login: roles, data, forms and the link to a database. Building a site that mainly informs with an application framework means paying for that second kind of work while not using it.
Why does the HTML matter for search engines and AI?
Google can process JavaScript, as long as it is not blocked. That is in Google's guide to the AI features. But not every crawler does. Vercel, the company behind Next.js, measured in late 2024 that the major AI crawlers, including those of OpenAI and Anthropic, did not execute JavaScript: they fetched the script files but did not run them. Vercel's own advice: put important content in the HTML the server sends.
That is a measurement from December 2024, and it may be different by now. But the lesson does not depend on one framework: text that only appears after a script runs is missed by some readers. Astro delivers that HTML by default. Next.js delivers it too, as long as you keep the content in Server Components and do not build everything in the browser.
Speed is linked to this. Less JavaScript means less work for the browser, and often a faster response to clicks. More on that in our article on Core Web Vitals.
When should you choose Astro?
- Your site mainly has to inform and be found: service pages, a knowledge base, town pages, a portfolio.
- You have many pages, possibly in several languages, and you want every page to be complete in the HTML.
- Interaction is local: a form, a calculator, a search box.
- People without programming skills edit the texts, through a content management system, as at TaalPro.
An Astro site can also have parts that differ on every visit, such as a form that checks something on the server. You set that per page. Only when most of the site becomes personal does Astro start working against you.
When should you choose Next.js?
- You are building an application: a customer portal, a dashboard, a platform with accounts.
- Data differs per user and changes often.
- There is a lot of interaction on every page, with forms that save data.
- Your team already works in React and will keep doing so.
Next.js can also make ordinary pages, such as a homepage or a pricing page; those are then rendered in advance or on the server. But you bring in the whole toolkit for applications, including for the parts that do not need it. For a site with only such pages, that is more than you need.
And Nuxt, SvelteKit or WordPress?
There is more than these two. Nuxt is to Vue what Next.js is to React. At Sittard Taxi, the homepage with the booking wizard is a Nuxt app, and the service and town pages are static pages of about 32 KB of HTML each. That way each part gets the tool that fits.
SvelteKit is a comparable framework built around Svelte. We have not built a client site with it, so we will not say more about it here.
WordPress is a good choice when a team already works with it, or when you need lots of extensions that already exist for it. EZ Factory runs on WordPress, with 611 addresses in three languages and a knowledge base of 163 Dutch articles. What suits you is covered in WordPress or custom.
Can you grow from a site into an application later?
Yes, and it does not have to be in one framework. You can build a site for the content, with a separate application alongside it for what happens behind the login. That way marketing and product each keep their own pace. At EZ Factory, the commercial face of the platform stands apart from the application itself, for exactly that reason.
It can also go the other way: at ArtsenPool, the public site of 15 pages and the three portals are both built in Next.js. There the site belongs to the platform: it explains how it works, for doctors and for hospitals. There is no fixed rule. Look at how much the two parts share: little, and two separate parts are easier to manage; a lot, and one project is more practical.
Which questions should you ask before choosing?
- What does the site have to do? Inform and sell, or process and keep records?
- How much differs per visitor? Does everyone see the same thing, or does each user have their own data?
- Who edits the texts, and how often?
- Who maintains the code in two years' time, and what is that team good at?
- Where does it have to run? On an ordinary web server, your own server or a platform?
- How long does it have to last? Every framework gets major updates; include them in the maintenance.
When this does not apply
If your current site works well and you can maintain it fine, a different framework is no reason to rebuild. A new site costs time and money, and the gain has to be bigger than those costs.
If your team only knows WordPress, or your webshop runs on a shop platform, the question of Astro or Next.js is not the first one. Start from what your team can maintain. And if you are building something with a lot of real-time collaboration, there are other choices than these two.
What we do not know: how Astro and Next.js compare on exactly the same site. We have not made a comparison in which the same page was built in both. The measurements on our case study pages are about different sites, with different content.
Frequently asked questions
Is Next.js bad for findability?
No. With Server Components, the content is simply in the HTML the server sends. The risk lies in content that is only built in the browser, and that can happen in any framework. Google can process JavaScript, but not every crawler does.
Can Astro handle logins and forms?
Yes, with an adapter for your server. You then render pages on request, per page, and such a page can read and set cookies. For a full application with many screens behind a login, an application framework is usually more practical.
Can you build Next.js as a static site?
Yes, with a static export. Next.js then creates one HTML file per page. Features that need a server, such as cookies, redirects and Server Actions, do not work then.
Is Astro still independent now that the team works at Cloudflare?
According to the announcement of 16 January 2026, Astro stays open source under the MIT licence, with open governance and support for any host. What that means in a few years, nobody knows for certain.
What does your own site run on?
On Astro, in three languages. For a site that mainly has to inform and be found, that suits us best. For applications we choose something else, such as Next.js for ArtsenPool.
Torn between the two? Describe your site or app in three sentences, and we will tell you which tool fits, even if it is your current one. You can read more about how we build under web development and Astro developer. You work directly with Nawid, with a fixed team of five specialists.
Also worth reading: Headless CMS: why we choose Directus.
Written with the help of AI, reviewed and edited by Nawid Rasa, who is responsible for the content. Sources are listed below the article. Spotted an error? Email hi@empireyo.com.
Torn between the two?
Describe your site or app in three sentences. We say honestly which tool fits, even if that means staying on your current stack.
Sources
Consulted on 5 November 2026.
- Astro Docs, Islands architecture
- Astro Docs, On-demand rendering
- Astro, The Astro Technology Company joins Cloudflare (16 January 2026)
- Next.js Docs, Server and Client Components (updated 5 October 2026)
- Next.js Docs, How to create a static export of your Next.js application (updated 9 August 2026)
- Vercel, The rise of the AI crawler (17 December 2024)
- Google Search Central, Google's guide to optimizing for generative AI features on Google Search (JavaScript)
- Empireyo, Basestep case study
- Empireyo, TaalPro case study
- Empireyo, ArtsenPool case study
- Empireyo, snelrepareren.nl case study
- Empireyo, Sittard Taxi case study
- Empireyo, EZ Factory case study