Astro vs Next.js: which framework to use for a marketing site?
Astro is our default for most B2B marketing sites, and 72% of Astro sites pass Core Web Vitals on mobile, compared with 37% of Next.js sites. Pick Next.js when the site needs logins, heavy personalization, or shared code with your product. Either way, marketers edit in a headless CMS, and Webflow fits teams that want to build pages themselves.
Key takeaways
- Astro is our default for content-led B2B marketing sites because it ships HTML with little or no JavaScript.
- In October 2026, 72% of mobile Astro sites passed Core Web Vitals, compared with 37% of Next.js sites.
- Next.js wins when the site needs logins or heavy personalization, shares React code with your product, or will be owned by an in-house React team.
- Neither framework gives marketers an editor. The editing experience comes from the headless CMS you pair with it.
- If your marketers want to build pages visually, a visual platform like Webflow fits better than either Astro or Next.js.
For most B2B marketing sites, we default to Astro. We pick Next.js when the site starts behaving like an app, with logged-in areas, code shared with a Next.js product, or pages that change for every visitor.
That surprises some teams, since Next.js is the bigger name, but most comparisons come from framework, CMS, and hosting vendors and skip what marketing teams use once the site is live.
Our State of the CMS 2027 research shows how far ahead Next.js is with new companies. We looked at the 2026 batch of Y Combinator, the startup accelerator behind Airbnb and Stripe, and among the startups whose websites show no CMS, 52% are built on Next.js and only 8% on Astro.
Popularity doesn't tell you which one fits a marketing site, though, so we compare them on the five things your team lives with after launch, namely real-world speed, editing, hosting and running costs, SEO and AEO, and who maintains the site.
Astro vs Next.js at a glance
Astro is built for websites that are mostly content, and Next.js is built for applications that also need public pages. Here's how that difference shows up across the decisions that matter for a marketing site:
How Astro and Next.js render a page
Rendering decides how much code every visitor downloads, which is why it sits underneath almost every other difference in this comparison.
Astro renders pages to plain HTML and CSS and adds JavaScript only through islands, which the Astro islands docs describe as "an enhanced UI component on an otherwise static page of HTML."
On a pricing page, the plan cards and FAQ stay plain HTML, and the ROI calculator is the one island that loads JavaScript. Server islands extend this to personalization, so a static page can hold one block rendered per request, like a regional price. We cover the rest of the framework in what Astro is and how it works.
Every Next.js page is part of a React application, so even a prerendered page downloads React to become interactive. In return, Next.js is flexible on every request.
Next.js 16 introduced Cache Components, which the Next.js 16 release post says "complete the story of Partial Prerendering," so a page can send a static shell and stream in the parts that depend on the visitor. That makes regional pricing, gated content, and experiments on high-traffic landing pages easier to build in Next.js than to bolt onto a static site.
Astro vs Next.js performance in real-world data
Only 48% of mobile websites pass Core Web Vitals according to the 2025 Web Almanac, so a site that passes is already ahead of most of the web.
JavaScript is a big part of the reason, because the median mobile home page ships 632 KB of JavaScript, and the browser must download, parse, and run it all before the page fully responds. Cutting that weight by default is the heart of Astro's design.
The field data shows the effect. We pulled the HTTP Archive Core Web Vitals Technology Report for both frameworks, and in October 2026, 72% of 55,449 mobile Astro origins passed Core Web Vitals, compared with 37% of 424,877 Next.js origins. Astro sites passed about twice as often.
Two caveats keep the comparison fair:
- Next.js has a much bigger sample. It runs on nearly eight times as many sites in the dataset, and many of them are heavier, app-like products, so part of the gap reflects what people build with each framework.
- A Next.js site can still be fast. A well-built Next.js marketing site can pass Core Web Vitals comfortably when developers keep client-side JavaScript in check.
For a marketing lead, the practical difference is the default, since Astro gives you a fast site unless someone adds weight, while Next.js needs ongoing discipline from your developers to stay fast as the site grows.
Whichever framework you choose, third-party scripts can wipe out the advantage. Tag managers, chat widgets, and A/B testing tools load on every page, and they're the most common reason we see a Core Web Vitals assessment fail on sites that should be fast.
SEO and AEO with Astro and Next.js
Both frameworks can send complete HTML to search engines, so rankings depend far more on how the site is built than on which framework sits underneath.
The same HTTP Archive data mentioned before shows that both cover the basics, with a median Lighthouse SEO score of 100 for both frameworks on mobile. Lighthouse only checks on-page basics like metas and crawlable links, though, so those scores say nothing about where you'll rank.
Two things matter more than the framework you pick:
- Content in the server HTML: AI answer engines raise the stakes here. For our client ShyftOff, about 60% of qualified leads now come through AI search, so key copy, pricing, and FAQs should be in the HTML the server sends instead of loaded later by client-side code. Astro does this by default, and Next.js does it for Server Components, but a page built mostly from client components can push important content behind JavaScript.
- SEO fields in the CMS: Neither framework gives marketers the SEO settings panel they'd find in a website builder, so plan fields for meta titles, descriptions, and structured data into your CMS from the start.
Building for search and AI answers together is the day job of our SEO and AEO team.
What editing looks like for your marketing team
Most comparisons skip editing, yet it's the part your team will feel every day. Neither Astro nor Next.js has an editor. Marketers work in a headless CMS, no matter the framework you pick, and the CMS shapes their day far more than the framework does.
If the split between content and presentation is new to you, our guide to headless CMS vs traditional CMS explains how it works.
We pair both frameworks with Sanity, and the split of work looks the same on either one:
- Marketers: Publish blog posts, edit page copy and SEO fields, update the navigation, and build pages from existing blocks.
- Developers: Handle new page templates, new block types, and changes to the content model, which they set up once and then maintain.
The two frameworks do differ on live preview, which Sanity supports for both:
- Astro: Sanity's Astro visual editing guide says preview "requires server-side rendering because draft mode depends on per-request cookie checking," so a static Astro site needs a server-rendered preview route, and by default the preview refreshes by reloading the page.
- Next.js: The setup is more mature and includes Sanity's Live Content API, which Sanity notes has no direct equivalent in Astro.
If click-to-edit preview is high on your team's wish list, that tilts slightly toward Next.js.
Our Sanity development team builds and runs this setup on either framework.
Astro vs Next.js hosting and running costs
Both frameworks are free and open source. What you pay for is hosting, the CMS, the build, and the people who keep the site running.
Astro's static output runs on free or low-cost hosting tiers, while Next.js runs best on Vercel, where the free Hobby plan is for non-commercial use only. The table below sums up each cost layer, and our Astro hosting and CMS cost breakdown goes through every hosting and CMS option in detail.
You can run Next.js outside Vercel too. The Next.js deployment docs say it "can be deployed as a Node.js server, Docker container, static export, or adapted to run on different platforms." Some features take extra setup away from Vercel, so self-hosting tends to move the cost from your invoice to your developers' time.
Both frameworks now have a commercial owner, since the Astro team joined Cloudflare in January 2026 and Vercel stewards Next.js, but content in a headless CMS stays portable either way.
Our view is that hosting shouldn't decide this choice. A few hundred dollars a year either way is small compared with the build and ongoing maintenance, and that's where the two frameworks really differ.
Who maintains an Astro or Next.js site?
Each framework makes a different part of ownership easier:
- Hiring favors Next.js: In the Stack Overflow 2025 Developer Survey, 20.8% of respondents used Next.js and 4.5% used Astro, so React and Next.js developers are easier to find and easier to replace.
- Simplicity favors Astro: Astro components look like HTML and CSS with a small script block on top, so a developer who knows React picks Astro up in days, and a static content site has very little server code to patch.
Upgrades and security work also look different on each:
- Next.js: Server features mean security releases need a developer on call, and Next.js ships them regularly. Major upgrades take planning too, because Next.js 16 introduced a new, more explicit caching model that changes how pages are built.
- Astro: The framework moves quickly as well, with two major versions in 2026 (Astro 6 in March and Astro 7 in June), but for a static content site those upgrades are usually small.
Either way, a framework doesn't remove the need for an owner. Someone has to update dependencies, watch performance, and ship the pages marketing asks for, which is the work we describe in what WebOps is.
When to choose Astro for a marketing site
Astro is the right pick when most of these describe your site:
- The site is mostly content: Product pages, the blog, resources, docs, and landing pages make up nearly everything, and that's exactly what Astro is built to serve.
- Core Web Vitals matter to your traffic: If organic search and paid campaigns drive pipeline, a fast default protects both rankings and conversion rates.
- A small team or an agency will maintain it: Astro's smaller codebase and lighter server footprint keep upkeep manageable without a dedicated platform engineer.
- The marketing site shares no code with your product: If your app isn't on Next.js, or the two never need shared components, there's nothing to gain from matching stacks.
- You want the lowest hosting cost: Static output runs on free or near-free tiers on every major host.
That's why our default stack for content-led B2B sites is Astro with Sanity.
When Next.js is the better choice
Next.js earns its extra weight when the site behaves like an application. Pick it when one or more of these is true:
- The site has logged-in areas: A customer portal, account pages, or gated resources need sessions and server logic that Next.js handles natively.
- Your product already runs on Next.js: Sharing components, the design system, and authentication with the app saves real engineering time.
- Most pages change per visitor: Heavy personalization or experimentation across the site plays to Next.js's per-request rendering.
- Your in-house React team will own the site: A team that ships Next.js every day will maintain a Next.js marketing site faster than one in a new framework.
- Interactive tools make up most of the page: Configurators and calculators with saved state are applications, even when they live on a marketing page.
In those cases, the extra JavaScript buys you something real, and Next.js is the right tool.
Running Astro and Next.js side by side
Many SaaS companies don't have to choose. The marketing site runs on Astro at the root domain, and the product runs on Next.js at a subdomain like app.example.com.
If you want both under one domain, for instance, to keep the blog and docs under example.com for SEO, a reverse proxy can route each path to a different stack. We explain how in our guide to setting up a reverse proxy for multiple CMSs. The price is two codebases and two deploy pipelines to maintain.
When Webflow fits better than both
Astro and Next.js both need a developer for every new layout. That works well when marketers assemble pages from approved blocks, and much less well when they want to design and launch pages on their own.
If your team wants to build a new landing page on Tuesday and launch it on Wednesday without a developer, a visual platform like Webflow fits better than either framework. Webflow is our default recommendation for teams that want to own the site day to day, and our Webflow development team builds and runs those sites.
How we choose between Astro and Next.js
On a first call, we ask six questions before we recommend a stack:
- Does any part of the site need logins or user accounts?
- Does the site need to share components or code with a Next.js product?
- Who will maintain the site in two years, an in-house React team, an agency, or one developer?
- How much of each page changes per visitor?
- Will marketers build new layouts themselves, or assemble pages from approved blocks?
- How much do Core Web Vitals matter to your organic and paid traffic?
The answers usually point one way.
If you're weighing the two for a new site or a rebuild, talk to our team, and we'll work through these questions with your marketing and engineering leads.
Frequently asked questions about Astro vs Next.js
Is Next.js overkill for a marketing website?
For a content-only marketing site, often yes. Next.js ships a React runtime and server features that a content site rarely uses, and both add upkeep. It's the right fit when the marketing site shares code with a Next.js product or has logged-in areas.
Can Astro use React components?
Yes. Astro renders React, Vue, Svelte, Solid, and Preact components through official integrations, and outputs them as HTML by default. Adding a client directive like client:visible makes a component interactive, so teams moving from Next.js can reuse many of their existing components.
Do you have to host Astro on Cloudflare?
No. Cloudflare took over the Astro team in January 2026, but Astro stays MIT-licensed and deploys to Netlify, Vercel, AWS, or any static host. Static output needs no adapter at all, and server rendering uses the adapter for whichever host you choose.
Can you move from Next.js to Astro without losing rankings?
Yes, if URLs, metadata, and content stay the same or redirect one-to-one. Astro's documentation includes a dedicated guide for migrating from Next.js. The SEO risk sits in changed URLs, missing redirects, and dropped structured data, so map every URL before launch.
Is Astro good for sites with thousands of pages?
Yes. Astro builds large static sites quickly, and Astro 7 made builds 15% to 61% faster in Astro's own benchmarks. For very large or fast-changing catalogs, you can server-render some routes and cache them instead of rebuilding every page on each publish.


See your website the way a senior strategist does
Foresight scans your site across 10 strategy dimensions. You get a scored breakdown of every gap costing you leads.
Continue reading





Ready to escape your CMS nightmare?
100+ successful migrations. 0 ranking disasters at launch. One embedded team that's done this before.







