Webflow vs Astro: which is better for a marketing site in 2026?

This is a decision people make once and live with for five years. Pick the wrong one and you find out the expensive way: in a rebuild, in a migration that loses its forms, or in a monthly bill that grew with your traffic.

Short answer

Choose Webflow if a non-developer will design and rebuild pages themselves and a monthly platform fee per site is fine. Choose Astro if you want the code and content in accounts you own, almost no JavaScript in the browser, and you have a developer to make layout changes.

Comparisons Published
Book a strategy callAll insights

We built on Webflow for years. Since September 2026 we have taken five live sites off Webflow, including this one, and we are porting an 87-page Webflow site to Astro for a client right now. So this is not a comparison from the docs. It is what each one did to real sites, with the numbers, and the part where Webflow is the better answer.

01

What Webflow and Astro actually are.

They are not the same kind of thing, and most of the confusion starts there. Webflow is a hosted product: a visual designer, a CMS, hosting and forms, all behind one login and one bill. You draw the page, Webflow writes the HTML, and Webflow serves it.

Astro is a framework. It is free, MIT licensed code that turns your pages into finished HTML files when the site builds, which is what a static site generator does. It has no editor, no hosting and no CMS of its own. You pick those. We use Vercel to host and Sanity as the headless CMS.

So the real question is not which tool is better. It is whether you want one product that does everything, or three accounts that each do one thing and belong to you.

02

How we compared them.

Everything here was checked on 5 November 2026. Prices come from the vendors' own pricing pages, read that day and quoted word for word in our research file. Webflow sets its prices with a script, so we read the values the page itself holds rather than a screenshot.

The performance numbers come from one script run against six live homepages that day. It lists every script file a page loads, downloads each one and adds up the bytes. Two are Webflow sites, four are Astro sites we built. Hosting is priced on Vercel because that is where we host; we did not price other hosts. Sizes are uncompressed, as downloaded, so they are bigger than what crosses the wire.

The migration numbers come from our own launch records: the status file each repository keeps, written during the work rather than after it.

Two things this is not. It is not a survey: two Webflow sites is a sample, and I say below what it cannot tell you. And it does not compare build prices, because we do not publish one for either.

03

Webflow and Astro side by side.

Checked on 5 November 2026 against webflow.com/pricing, vercel.com/pricing, sanity.io/pricing and Astro's license file. The Astro column assumes the stack we build on: Astro, Vercel and Sanity.
WebflowAstro, Vercel and Sanity
What it isOne hosted product: designer, CMS, hosting, formsA free framework, plus a host and a CMS you choose
LicenseProprietaryAstro is MIT licensed
Cheapest site with a CMSPremium, $25 a month billed yearly or $39 monthly, with 50 GB bandwidthVercel Pro at $20 a month and Sanity Free at $0
Cheapest site with no CMSBasic, $15 a month billed yearly or $25 monthlyVercel Pro at $20 a month
Free tierStarter: 2 static pages on a webflow.io domainAstro and Sanity Free are $0; Vercel Hobby is for non-commercial use only
CMS limits on the entry plan20,000 items and 40 collections on the CMS plan10k documents on Sanity Free, 25k on Growth
Traffic pricingBandwidth is part of the plan, a slider from 50 GB to 2.5 TB$20 of included usage credit on Vercel Pro, then pay as you go
Who changes a layoutAnyone with a designer seat, visuallyA developer, in code
Who edits copyEditors in WebflowEditors in Sanity: up to 20 seats free
Platform JavaScript on the homepage1,587 KB and 2,020 KB on the two we measured0 KB on the four we measured
If you leaveStatic pages export; CMS content goes collection by collection; forms stop workingYou already hold the repository, the dataset and the host
04

What each one makes the browser download.

This is where the two differ most, and it is the part nobody puts in a comparison because it means measuring something.

A Webflow site loads jQuery and a set of Webflow script chunks on every page, because that is how Webflow runs its interactions: the scroll reveals, the menus, the sliders. Both Webflow sites we measured loaded the same jQuery 3.5.1 file, 87 KB, from the same CloudFront address. On top of it, the chunks.

Platform script only. Our own site.js on 5fourdigital.com is 34 KB and is the only script file it loads.

On BlackIllustrations, my own product site and still on Webflow, the platform runtime came to 1,587 KB. On the client site we are porting it was 2,020 KB across four files, one of them 1,583 KB by itself. This site, on Astro, has one script file in its HTML: our own, at 34 KB. The other three Astro sites we checked load nothing of ours at all.

Uncompressed is not what crosses the wire, and a cached file is not downloaded twice. What does not compress away is the parsing. A phone still has to read and run every one of those kilobytes before the page can respond to a tap, and that is the cost the visitor feels.

Here is the fair part. Google's analytics script ran from 374 KB to 528 KB per file on every site that used it, Astro or Webflow. On our three client Astro sites it is the only script on the page. If you are choosing Astro to get a lean page and then add five marketing tags, you will not get a lean page. The platform is one decision. What you put on it is another.

If the page weight matters to you because of search, the piece on Core Web Vitals explains which of these numbers Google actually reads.

05

What each one costs to run every month.

Webflow prices per site, and its Premium plan is marked new on the page. As of 5 November: Basic is $15 a month billed yearly, $25 monthly, for up to 300 static pages and no CMS. Premium is $25 a month billed yearly, $39 monthly, and adds the CMS with 50 GB of bandwidth. More bandwidth moves a slider that adds to the price, up to 2.5 TB.

The next tier up is Team at $2,500 a month on an annual contract. That is the first plan on the page that lists Webflow Localize and publishing workflows. A marketing site that grows into either of those needs makes a large jump.

Separately, Webflow bills the workspace you build in. Core is $19 a month billed yearly, $28 monthly, and it is the tier where "Code export" first appears. A workspace includes one full seat, for the owner.

The Astro side is three bills. Astro is $0. Vercel Pro is $20 a month with $20 of included usage, and you need Pro for a business: the Hobby plan is, in Vercel's words, "for personal, non-commercial use." Sanity Free is $0 with up to 20 user seats and 10k documents. Growth is $15 per seat a month.

Monthly platform cost for one marketing site with a CMS, from each vendor's pricing page on 5 November 2026. Build and upkeep are not included on either side.
ItemWebflowAstro stack
Site plan with a CMS$25 billed yearly, $39 monthlyAstro: $0
HostingIncluded, 50 GB bandwidthVercel Pro: $20
CMSIncluded, 20,000 itemsSanity Free: $0, 10k documents
Workspace with code exportCore: $19 billed yearly, $28 monthlyNot a thing: the code is yours
When traffic growsMove the bandwidth sliderUsage past the $20 credit

At the entry level they come out close, and I would not choose either one on price. The difference is the shape of the bill as you grow. Webflow's rises in steps, and in Webflow's words, "Two consecutive months over the limit triggers an automatic plan upgrade." Vercel's rises with use, and Sanity's with the number of people editing.

06

Who edits the site, and what they can break.

This is Webflow's real advantage, and it is a big one. A marketer with a designer seat can open Webflow, duplicate a page, move a section and publish it, with nobody else in the loop. No ticket. No developer. For a team that changes its landing pages every week, that is worth a lot.

It is also the risk. The same seat that can move a section can break the mobile layout of every page that uses that class, and Webflow will publish it. Nothing checks the page before it goes live except the person clicking publish.

On Astro the split is cleaner and stricter. Editors change copy, images, case studies and posts in Sanity, and the site rebuilds itself. On this site, publishing a case study in Sanity triggers a fresh build through a webhook. Layout lives in code, so a layout change goes through a developer and a review.

Which one is right depends on who you have. If your marketer is also your designer, Webflow fits how you already work. If you have a developer, or an agency on retainer, the stricter split means the site you approved is the site that stays live.

07

What you own if you leave.

Read Webflow's own pricing page on this, because it is direct about it. Code export is for "HTML and CSS files", and "Dynamic content (CMS items/pages) can't be exported." Its FAQ adds that CMS content "must be exported on a collection-by-collection basis and forms will stop working." And: "If you export your code, it can't be reimported."

Webflow's side is its own wording. Ours is the No-Hostage Rule, which is in every contract.

None of that is hidden, and none of it is unusual for a hosted builder. It does mean a Webflow site is a Webflow site. You can take a snapshot out. You cannot take the working site out.

On an Astro build the question mostly goes away, because there is nothing to export. Under our No-Hostage Rule the repository sits in your GitHub, the content in your Sanity account and the hosting in your Vercel account, and we work as an admin on all three. If we part ways, you keep a complete working site.

08

What moving a site off Webflow actually takes.

People assume the export does most of the work. On the 87-page client site, it was where the work started.

The first thing I learned is that on Webflow the markup is the design. I first rebuilt the pages in clean, hand-written HTML over Webflow's own stylesheet. It built, it rendered, and it looked nothing like the live site. Our check compares every page to the original on visible text and on class names, and it scored 33% on text and 3.7% on classes, because the 209 classes the real homepage hangs off were not there. So we port the real markup now, and all 85 live pages pass that check.

The second is that Webflow does a lot at runtime, and an export does not carry the runtime. That site has 525 Lottie animation elements, driven by a player Webflow loads. Without it, every one was an empty box. The arrowheads on 424 buttons and menu rows disappeared, leaving a bare dash, and 64 pages lost the soft panel behind their hero.

What broke when the Webflow runtime was removed from one 87-page site, from the port's launch record. Every item was caught before launch.
What Webflow did at runtimeWhat we saw without itScale
Ran Lottie animations from its playerEmpty boxes where the animations were525 elements
Drew button arrowheads with a LottieA bare dash on every button and menu row424 instances
Drew the panel behind each page heroPages with no hero background64 pages
Kept real CSS in inline style blocksHidden elements showing, the nav stuck in desktop layoutAbout 14KB
Cut card excerpts with a scriptCard text running to full lengthAbout 100 characters
Served assets under hashed filenamesOne photo shown twice, another lost77 files overwritten

None of that was hard to fix once we saw it. All of it passed a text check, and a screenshot comparison against the live site is what found it. The lesson I took: budget for the runtime, not just the pages.

The assets are the other half. Webflow serves images from its own CDN, and those links die when the site does. On this site we mirrored 591 Webflow images to our own host and converted them to WebP, which took them from 190MB to 59MB. On the client port we pulled all 285 assets local before anything else.

09

Search, AI crawlers and the HTML they read.

Both platforms serve finished HTML, so a crawler reads the page on either one without running any script. That is the part that matters most for search, and Webflow does it well. Do not let anyone tell you Webflow sites cannot rank.

What differs is how much of the rest you control. On an Astro build every file at the root is yours: robots.txt, llms.txt, the sitemap, the structured data, the redirect table, all in the repository and all checked by the build. At launch, all 385 redirects on this site reached their page in one hop, and the build fails if one stops doing so.

The bigger gap is usually not the platform. The client's Webflow site had no meta description on 86 of its 87 pages. Webflow has a field for it. Nobody filled it in. A platform gives you the field, and a process is what fills it.

If being quoted by ChatGPT and Claude is the goal, the platform decision is smaller than the content one. How to get your site cited by AI assistants is the list we work from, and every item on it is possible on Webflow.

10

Where Webflow is the better choice.

I want to be plain about this, because we build on Astro and it would be easy not to be.

  • A marketer who designs. If the person who owns the site wants to build new pages visually, without waiting on anyone, Webflow is better at that than anything we would hand them. Sanity edits content. It does not let you design a new layout.
  • No developer, ever. An Astro site needs someone who can work in code for every layout change. If you will never have that person, Webflow is the honest choice.
  • A small, simple site. At $15 a month billed yearly for up to 300 static pages, with hosting and forms included and one bill, Basic is hard to argue with for a site that rarely changes.
  • Hiring. In my experience Webflow designers are easy to find. An Astro developer who also understands marketing sites is harder.

If two of those describe you, stay on Webflow. Spend the money on content.

11

How to choose, by situation.

  • You are a startup with one marketer and no developer. Webflow. Revisit it when you hire engineering.
  • You have a developer or an agency on retainer. Astro. The stricter split protects the site, and the page stays light.
  • You publish a lot. Check the CMS limits against your plans for the next three years, on both sides, before you choose.
  • Your site has to stay up and stay yours. Regulated firms, anyone who has been locked out of a site before: Astro on accounts in your name.
  • You are on Webflow and it works. Do not move for speed alone. Measure your own runtime first with the method above. Move when ownership, cost at scale or the edit process is the actual problem.
12

What we could not check.

Two Webflow sites is a small sample, and both lean on Webflow's interactions. A lean Webflow build with no animations would ship less script than either. I do not have one to measure, so I am not going to guess the number.

We also have no field data comparing a Webflow site with its own Astro port, because the port is not live yet. When it is, we will add the before and after here, on the same pages, from real visitors. That is the comparison worth having.

And none of the prices above include building the site. Those depend on the site, and we do not publish ours yet.

Prices change. Every figure in this piece was read on 5 November 2026. If you are reading this much later, check the pricing pages before you trust the tables.

John D Saunders, Founder / Creative Director at 5Four Digital
Written by
John D. Saunders
Founder / Creative Director, 5Four Digital

Designer, developer and educator in Miami. I run strategy and creative direction at 5Four Digital, a web design and development agency that leans on AI. I have spoken at AIGA, Adobe MAX and Webflow Conf, and I put the whole process on YouTube.

More about John

Common questions, answered.

On the sites we measured on 5 November 2026, yes, by a wide margin in script: two Webflow homepages loaded 1,587 KB and 2,020 KB of platform JavaScript uncompressed, and our Astro homepages loaded none. Analytics scripts weigh the same on both, so a heavily tagged Astro site loses most of that advantage.

Ready to stop paying the Ticket Tax?

Book a 30-minute call. We'll look at what you have, tell you which system to start with, and give you a clear price range before you leave the call.

Book a strategy callSee the Approval Loop