--- title: "Astro vs Webflow (2026): Cost, Speed and Lock-in — Dardo" description: "Astro vs Webflow for a B2B marketing site: who edits, what a 60-page site costs a year, Core Web Vitals data, export limits and when to pick each." url: "https://dardo.studio/en/blog/astro-vs-webflow/" language: "en" translations: {"es":"https://dardo.studio/es/blog/astro-vs-webflow/","pt":"https://dardo.studio/pt/blog/astro-vs-webflow/"} updated: "2026-10-22T19:49:00.490Z" --- [Blog](https://dardo.studio/en/blog/) # Astro vs Webflow: editing, yearly cost, speed and lock-in for a marketing site in 2026 Webflow suits marketing teams that build pages visually; Astro suits developer-run sites. Yearly costs, September 2026 speed data and what moving takes. By [Nicolás Cerón](https://www.linkedin.com/in/nicoceron/) · October 22, 2026 ![Two railway tracks diverge across a misty plain at blue hour toward distant lit towns, with one crimson signal lamp glowing at the switch](https://dardo.studio/_astro/01M5JG22FETX5D2BRZAM0ZHN6Q_ZlJ1FI.webp) ## Key takeaways - In September 2026, 71.3% of Webflow sites and 71.1% of Astro sites passed Core Web Vitals on mobile, while the median Astro home page weighed 1.36 MB against 3.48 MB on Webflow. - Our 60-page B2B example with 3,000 CMS items costs USD 1,368 a year on Webflow Premium with three paid seats and USD 0 to 600 on Astro with Cloudflare and Sanity, before developer time. - On Webflow, marketers on USD 15 Limited seats build pages from components; on Astro, editors fill CMS fields and new layouts are code. - Webflow's code export, from a USD 19 Core Workspace, leaves out the CMS, forms, site search and localized pages, so moving to Astro is part export and part rebuild. ## The short answer Choose Webflow when a marketing team builds and changes pages visually every week, the content spans several related collections, and you want hosting, forms, a CMS and a visual editor in one bill. Choose Astro when developers make most changes, the site has to sit next to your product or your own backend, or you want the code and the content in accounts you control. Speed doesn't settle it. In September 2026, 71.3% of Webflow sites and 71.1% of Astro sites passed Core Web Vitals on mobile, even though the median Astro home page weighed about 40% as much. Cost settles it only partly: Astro's running bill is lower, while its build and every later layout change cost developer time. We build and maintain sites on both, through [Webflow development](https://dardo.studio/en/services/webflow-development/) and [Astro development](https://dardo.studio/en/services/astro-development/). Prices below are in US dollars, before tax, as of October 2026. ## How the work splits between marketing and developers On Webflow, a Full seat, at USD 39 a month billed yearly, designs full sites and manages settings. A Limited seat, at USD 15, edits content or builds pages from components. One Full seat comes with the Workspace, and reviewers who only comment are free. Since Webflow fully retired its legacy Editor on 5 October 2026, everyone who edits a site needs a seat: users of the old Editor were moved to free seats, and anyone added now pays. That model has one big strength. A designer builds a component library once, such as a hero, a pricing table and a logo strip, and marketers on Limited seats assemble landing pages from it and publish without filing a ticket. On Astro, the line between design and content sits elsewhere. Components are code, and the content model in the CMS decides what editors can do: fill fields, reorder blocks, preview drafts and publish, after which the site rebuilds. A developer adds new components, changes the navigation and keeps the framework current. Astro moves quickly, with Astro 6 in March 2026 and Astro 7 in June, and gives security fixes only to the previous major version, so upgrades need an owner. Content can also live as Markdown files in Git, which suits documentation and changelogs that developers write. A useful test: look at who changed the site's layout in the last six months. If it was mostly marketers in the Designer, Astro would slow them down. If it was mostly developers working around Webflow with custom code embeds, Webflow is slowing them down. Astro development Want Dardo to do this for you? Tell us what you need. Nico replies personally within one business day. [Get a proposal](https://dardo.studio/en/contact/?service=astro-development) · [See the service](https://dardo.studio/en/services/astro-development/) ## What a 60-page B2B site costs a year on each The example: a B2B company's 60-page marketing site with a resource library of posts, case studies, downloads and authors, four collections and about 3,000 CMS items, in English, with 80 GB of traffic a month. A designer owns the Workspace and builds components, a second designer lays out campaign pages, and two marketers publish. Platform fees only, billed yearly; the domain, taxes and the build are left out. | Line | Webflow | Astro on Cloudflare with Sanity | | ----------------------------- | ------------------------- | ----------------------------------------------- | | Site plan or hosting | Premium, USD 25 a month | Cloudflare Workers, USD 0 to 5 | | Traffic above 50 GB | 100 GB tier, USD 20 | No bandwidth charge | | Designer who owns the account | Full seat, included | Sanity seat, USD 0 to 15 | | Second designer | Full seat, USD 39 | No platform seat; new layouts go to a developer | | Two marketers | Two Limited seats, USD 30 | Two Sanity seats, USD 0 to 30 | | Per month | USD 114 | USD 0 to 50 | | Per year | USD 1,368 | USD 0 to 600 | What we assumed. Premium, because Webflow's Basic plan has no CMS; Premium includes 40 collections and 20,000 items, far more than this site uses. The 100 GB bandwidth tier, because 80 GB is over Premium's included 50 GB. Billed monthly, the same Webflow lines cost USD 39, 30, 45 and 38, or USD 1,824 a year. Code export needs a paid Workspace plan on top, from Core at USD 19 a month billed yearly. On Astro, Cloudflare doesn't charge for requests to static assets or for bandwidth, and Workers Paid at USD 5 a month covers a form handler past the free 100,000 requests a day. Sanity's Free plan covers up to 20 users and 10,000 documents but only Administrator and Viewer roles, so the upper figure puts three people on Growth at USD 15 a seat. Site search, included in Premium, becomes a static index such as Pagefind. Developer time is the line that moves. On Webflow, the second designer's Full seat covers campaign layouts. On Astro, that work goes to a developer, and so do upgrades. If nobody on your team writes code, budget for someone who does: with our website maintenance plans, from USD 79 a month, the Astro site would cost about USD 950 to 1,550 a year, close to Webflow's bill. Our guide to [Webflow pricing in 2026](https://dardo.studio/en/blog/webflow-pricing-2026/) covers the May 2026 plan changes, and the [Webflow renewal calculator](https://dardo.studio/en/tools/webflow-pricing-calculator/) prices your own site against Framer and a coded site. ## Speed: the same pass rate at 40% of the weight The HTTP Archive's technology report, which measures every site it detects on each platform, put Astro and Webflow level on mobile Core Web Vitals in September 2026. The pages behind those numbers are very different. | September 2026, mobile | Astro | Webflow | | ----------------------------------- | ------- | ------- | | Sites measured | 47,277 | 59,483 | | Passing all three Core Web Vitals | 71.1% | 71.3% | | Good loading (LCP) | 81.1% | 78.6% | | Good responsiveness (INP) | 85.0% | 88.0% | | Good layout stability (CLS) | 93.6% | 93.6% | | Median page weight | 1.36 MB | 3.48 MB | | Median JavaScript | 409 KB | 926 KB | | Median images | 355 KB | 812 KB | | Median Lighthouse performance score | 70 | 62.5 | | Passing on desktop | 84.6% | 82.6% | Why the pass rates are level. Core Web Vitals is a threshold, not a race: a site passes when its real Chrome visits are good on loading, responsiveness and layout stability at the 75th percentile of page loads, and passing by a wide margin earns nothing extra. Webflow's hosting and CDN give most of its sites a reasonable start. And the two platforms miss in different places. Webflow sites are the less likely of the two to load their main content quickly, 78.6% against 81.1%, and the more likely to respond quickly to a tap, 88.0% against 85.0%. A single pass rate folds those into a tie. Where the extra weight comes from. When we inspected seven Webflow home pages in October 2026, all seven loaded jQuery and served their images and social share image from Webflow's servers. That is a baseline every Webflow page carries before your own content. Astro starts from HTML and sends JavaScript only for the components marked as interactive islands. In the United States, where devices and networks are faster, both pass more often: 84.2% of Astro sites and 80.2% of Webflow sites. A caveat that applies to every figure here: the report measures the sites detected on each platform, and its page weight and Lighthouse figures come from their home pages. Webflow's and Astro's audiences differ, so the data describes typical sites, not what a careful build achieves on either. Our [website platform speed report](https://dardo.studio/en/tools/website-platform-speed-report/) shows the same data by country. ## Content: Webflow's CMS or a headless CMS This is Webflow's strongest ground. Premium includes 40 collections and 20,000 items, publishes and schedules items one by one, generates RSS feeds and opens a content API at 120 requests a minute. For a resource library inside a marketing site, that's enough for most teams, and editors work in the same tool as the designers. A headless CMS behind Astro wins in three cases. The same content feeds more than the website, such as a help center, an app or partner pages. You want a strict schema: Astro's content collections check every entry against one, and an entry that breaks it stops the build instead of reaching a visitor. Or you publish in several languages: Webflow's Localize costs USD 9 a locale for up to three, or USD 29 for up to ten with translated URLs, while Sanity includes unlimited locales on its Free plan and Astro's i18n routing gives each language its own URLs. Our comparison of [headless and traditional CMSs](https://dardo.studio/en/blog/headless-cms-vs-traditional-cms/) covers the trade-offs. ## SEO and AI-search controls Both can rank; content and links decide that. Webflow puts the common controls in settings, where a marketer can change them. Astro puts them in code, where nothing has a limit and nothing exists until someone builds it. | Control | Webflow | Astro | | -------------------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | Titles, descriptions, Open Graph | Per page and per CMS template | From your templates and CMS fields | | Sitemap | Generated automatically | Built by the @astrojs/sitemap integration | | robots.txt | Rules you add in Site settings, SEO, Indexing | A file or endpoint you write | | llms.txt | Uploaded in Site settings, SEO; UTF-8, under 100 KB | A file you add, or generate from content at build | | Structured data | Schema markup support on site plans, plus custom code | JSON-LD generated in templates from CMS data | | Redirects | 301s on paid site plans, with CSV import and export | Host rules, such as Cloudflare's \_redirects file, with up to 2,000 static and 100 dynamic rules | | URL format | No trailing slash | Set with Astro's trailingSlash and build.format options | | Languages | Localize adds a sitemap with hreflang; translated URLs need Advanced | i18n routing, one URL per language, hreflang from your templates | For AI search, the work is the same on both: pages that state facts plainly, structured data that matches them, and the crawlers you want allowed in robots.txt. Webflow's own help article describes llms.txt as an experimental convention whose effect on AI-driven search is unclear, so treat it as a small extra rather than a strategy. Our [Webflow SEO guide](https://dardo.studio/en/blog/webflow-seo/) covers the settings, and our free [AI visibility checker](https://dardo.studio/en/tools/ai-visibility-checker/) reads any site's robots.txt, llms.txt and structured data. ## Interactions and design freedom Webflow's Interactions editor gives designers a timeline built on GSAP, and Webflow made GSAP free for commercial use in April 2025. React code components, imported through DevLink, need Premium. Five of the seven Webflow home pages we inspected used Interactions, one of them on 109 elements. Astro offers the same GSAP library, plus CSS animation, WebGL and view transitions between pages, with Astro's client router switching animations off for visitors who ask for reduced motion. What it lacks is the timeline editor: each interaction is code a developer writes and tests. The design freedom is equal or greater; the designer's independence is smaller. Interactions don't travel. They ship only as Webflow's own JavaScript, so a move to Astro recreates each one or drops it, which is a good moment to cut motion that no longer earns its place. ## What you can take with you Webflow is easier to leave than Framer, but only partway. On a paid Workspace plan, from Core at USD 19 a month billed yearly, you can export HTML, CSS, JavaScript and images and host them anywhere. The export leaves out CMS content, code components, localized content, password protection, site search and form handling, and Collection lists show their empty state. Collections export separately as CSV, one at a time and one locale at a time, with references flattened to text and images linked to Webflow's hosting, links that break if the site is deleted. The Data API is cleaner: at Premium's 120 requests a minute, 20,000 items take about 200 requests. An Astro site is code in your repository on an open-source framework. Astro's deploy guides cover hosts such as Cloudflare, Netlify, Vercel, GitHub Pages, AWS and Render, and its official adapters for Cloudflare, Netlify, Node and Vercel handle pages rendered on request. The lock-in moves to the CMS, so choose one with a full export or one you can self-host, such as Payload. ## Which to choose ### Webflow fits when - Marketers build and change pages visually every week, from components a designer maintains. - Content spans several related collections, within 40 collections and 20,000 items. - You need more than ten editors, each paid by role, which rules out Framer's standard plans. - You'd rather pay one bill for hosting, forms, CMS and editing than run them yourself. ### Astro fits when - Developers make most changes and want pull requests, tests and code review. - The marketing site shares components, data or releases with your product. - Content feeds more than one channel, or you publish in several languages. - You want the lowest running cost and the lightest pages, and can fund the developer time. ### Neither fits when - A designer or a small team owns the site and the story leans on motion. Framer is the closer fit; our [Webflow alternatives](https://dardo.studio/en/blog/webflow-alternatives/) guide prices it next to five other options. - The project is mostly a signed-in product with dashboards and accounts. Next.js fits that better, as [Astro vs Next.js](https://dardo.studio/en/blog/astro-vs-nextjs/) explains. - Marketing runs inside HubSpot's CRM every day. HubSpot Content Hub is worth pricing before either. ## Moving from Webflow to Astro The move is part export, part rebuild. In order: inventory every URL, including Collection pages, and export the 301s already set in Webflow; export each Collection per locale, or read it through the Data API; download every asset from Webflow's CDN, Open Graph images included; rebuild the templates as Astro components; recreate the interactions worth keeping; replace forms, search and password protection; and build each language with Astro's i18n routing. Two details matter more than they look. Webflow serves pages without a trailing slash, so set Astro's trailingSlash and build.format to match, or every page needs a redirect you didn't plan. And a static Astro build without an adapter turns configured redirects into meta-refresh pages, so put the 301s in your host's rules. Our free [redirect map generator](https://dardo.studio/en/tools/redirect-map-generator/) matches old and new sitemaps and writes those rules for Cloudflare, Netlify and other hosts. Our [Webflow to Astro guide](https://dardo.studio/en/blog/webflow-to-astro/) covers each step, and our [Webflow to Astro migration](https://dardo.studio/en/services/webflow-to-astro/) service runs it, with a staging crawl against every old URL and Search Console comparisons 30 and 60 days after launch. Going the other way is easier on content: Webflow's CMS imports CSV and its redirect settings import a CSV of 301s, while every page is rebuilt in the Designer. If you're weighing a move, [send us the site](https://dardo.studio/en/contact/?service=webflow-to-astro) and we'll tell you whether leaving Webflow pays before we quote it. ## Common questions **Is Astro faster than Webflow?** The median Astro page is lighter: 1.36 MB on mobile in September 2026 against 3.48 MB on Webflow, with 409 KB of JavaScript against 926 KB. Pass rates were level, though: 71.1% of Astro sites and 71.3% of Webflow sites passed Core Web Vitals on mobile. Both figures describe typical sites. When a Webflow site fails, the causes are usually images, fonts and third-party scripts, which can be fixed without leaving Webflow. **Is Astro cheaper than Webflow?** To run, yes. Our 60-page example costs USD 1,368 a year on Webflow Premium with bandwidth and three paid seats, and USD 0 to 600 on Astro with Cloudflare and Sanity, as of October 2026. Astro costs more to build and to change, because new layouts and upgrades need a developer. If you pay for upkeep from USD 79 a month on our maintenance plans, the two land close together. **Do I need a paid Webflow seat for every editor?** Yes, for anyone added now. Webflow fully retired its legacy Editor on 5 October 2026, so everyone who edits needs a seat in the site's Workspace: USD 15 a month billed yearly for a Limited seat that edits content or builds pages from components, or USD 39 for a Full seat. Existing Editor users were moved to free seats, and reviewers who only comment are free. **Can I export my Webflow site and host it on Astro?** Partly. Paid Workspace plans, from Core at USD 19 a month billed yearly, export HTML, CSS, JavaScript and images, but not CMS content, forms, site search, password protection or localized pages. Use that export as a reference, pull the CMS out as CSV or through the Data API, rebuild the templates as Astro components and redirect every URL that changes. **Which is better for SEO, Webflow or Astro?** Neither ranks a site by itself. Webflow puts the common controls in settings: 301 redirects, robots.txt rules, an llms.txt upload, schema markup support and localized sitemaps. Astro gives full control of every tag, file and redirect, but each one exists only once a developer builds it. If your team needs to change redirects or metadata without a developer, Webflow's settings are an advantage. **Can marketers still build landing pages on Astro?** Within limits. With a block-based content model in a headless CMS, a marketer assembles a page from sections a developer built, fills the fields and publishes, which covers most campaign pages. A new section design, a new interaction or a navigation change is code. If your team builds new layouts every week, Webflow's Designer and Limited seats suit it better. ## Sources & further reading Sources behind this page, with further detail from the original publishers. - [HTTP Archive: Technology report (Core Web Vitals, page weight and Lighthouse by platform)](https://httparchive.org/reports/techreport/tech) · httparchive.org - [Webflow: Pricing](https://webflow.com/pricing) · webflow.com - [Webflow Help: Legacy Editor deprecation FAQ](https://help.webflow.com/hc/en-us/articles/48412420902675-Legacy-Editor-deprecation-FAQ) · help.webflow.com - [Webflow Help: How do I export my Webflow site code?](https://help.webflow.com/hc/en-us/articles/33961386739347-How-do-I-export-my-Webflow-site-code) · help.webflow.com - [Webflow Help: How do I import content into the Webflow CMS?](https://help.webflow.com/hc/en-us/articles/33961290794771-How-do-I-import-content-into-the-Webflow-CMS) · help.webflow.com - [Webflow Help: Import/export 301 redirects](https://help.webflow.com/hc/en-us/articles/33961211526291-Import-export-301-redirects) · help.webflow.com - [Webflow Help: Set robots.txt rules](https://help.webflow.com/hc/en-us/articles/41954080897683-Set-robots-txt-rules) · help.webflow.com - [Webflow Help: Upload an llms.txt file to your site](https://help.webflow.com/hc/en-us/articles/43240104183315-Upload-an-llms-txt-file-to-your-site) · help.webflow.com - [Webflow Developers: Rate limits](https://developers.webflow.com/data/reference/rate-limits) · developers.webflow.com - [Webflow: Webflow makes GSAP 100% free](https://webflow.com/blog/gsap-becomes-free) · webflow.com - [Astro Docs: Islands architecture](https://docs.astro.build/en/concepts/islands/) · docs.astro.build - [Astro Docs: Content collections](https://docs.astro.build/en/guides/content-collections/) · docs.astro.build - [Astro Docs: Use a CMS with Astro](https://docs.astro.build/en/guides/cms/) · docs.astro.build - [Astro Docs: Deploy your Astro site](https://docs.astro.build/en/guides/deploy/) · docs.astro.build - [Astro Docs: Internationalization (i18n) routing](https://docs.astro.build/en/guides/internationalization/) · docs.astro.build - [Astro Docs: Configuration reference (trailingSlash, build.format, redirects)](https://docs.astro.build/en/reference/configuration-reference/) · docs.astro.build - [Astro Docs: @astrojs/sitemap](https://docs.astro.build/en/guides/integrations-guide/sitemap/) · docs.astro.build - [Astro Docs: View transitions](https://docs.astro.build/en/guides/view-transitions/) · docs.astro.build - [Astro Docs: Upgrade Astro (support for previous versions)](https://docs.astro.build/en/upgrade-astro/) · docs.astro.build - [Astro: Astro 7.0](https://astro.build/blog/astro-7/) · astro.build - [Cloudflare Docs: Workers pricing](https://developers.cloudflare.com/workers/platform/pricing/) · developers.cloudflare.com - [Cloudflare Docs: Redirects for static assets](https://developers.cloudflare.com/workers/static-assets/redirects/) · developers.cloudflare.com - [Sanity: Pricing](https://www.sanity.io/pricing) · sanity.io [Nicolás Cerón](https://www.linkedin.com/in/nicoceron/) Nicolás Cerón is the founder of Dardo, a brand, web design and development studio in Bogotá, Colombia. ## Related articles - [**How much does a website migration cost in 2026? Published prices by platform, site size and migration type**What website migrations cost in 2026 from providers that publish prices, by type and site size, plus what drives a quote and what a botched move risks.](https://dardo.studio/en/blog/website-migration-cost/) - [**Webflow vs Framer: which to choose for a marketing site in 2026, with real costs**Webflow vs Framer in 2026: who should pick which, what a 20-page site with a 300-post blog in two languages costs on each, and when to pick neither.](https://dardo.studio/en/blog/webflow-vs-framer/) - [**Webflow alternatives in 2026: what each one costs to run, and what it takes to move off Webflow**Framer, WordPress, a coded site, Wix Studio, Squarespace or HubSpot: what each costs to run a 20-page site with a blog, and what leaving Webflow takes.](https://dardo.studio/en/blog/webflow-alternatives/) - [**Webflow pricing 2026: what changes at renewal, what you'll pay and when to leave**Webflow merged its CMS and Business plans into Premium. What your site pays at renewal, with the math, and when staying beats moving to Framer or Astro.](https://dardo.studio/en/blog/webflow-pricing-2026/) ## Keep exploring. - [Service · **Astro development: fast content sites and migrations**](https://dardo.studio/en/services/astro-development/) - [Your project · **Start a conversation**](https://dardo.studio/en/contact/)