Skip to main content
PandaCodeGen
Back to Insights

Webflow pricing

Webflow True Cost: Build It From Your Invoice

Webflow has no single "real monthly cost." The defensible total is the combination of the current account, required features, connected services, payment costs, agency work and internal operating time for a defined period.

Every Webflow figure on this page was re-checked against Webflow's own pricing page and help center on August 2, 2026.

Hassan Jamal·Mar 18, 2026·7 min read

Three Webflow users on the March 2026 pricing change, in their own words, each with a link back to the original Reddit comment.

"Your number one gripe by a wide margin is how awful your pricing is. It is an absolute hellhole and the worst part of trying to sell a Webflow project. You have somehow created a way to make it so much worse.

u/wherethewifisweak (OP) · r/webflow · Mar 8, 2026 · 54 upvotes · Verify source

"I have been using Webflow for years and NEVER have been able to understand the pricing models nor fully communicate to my clients which plan they needed and why. It is so convoluted and counterintuitive but it seems the confusion is part of the business model here.

u/proteanradish · r/webflow · Mar 8, 2026 · 16 upvotes · Verify source

"Webflow: great product to build with, awful, confusing, overpriced account management.

u/originaladam · r/webflow · Mar 8, 2026 · 24 upvotes · Verify source

The short answer

  • Webflow's published floor on August 2, 2026: Basic $15/mo billed yearly with no CMS, Premium $25/mo billed yearly with CMS. Per site, USD, before tax.
  • Add a Workspace plan if you need code export or more than one seat: Core $19/mo billed yearly, Growth $49/mo billed yearly.
  • Add-ons are priced by usage, not bundled: Optimize from $299/mo, Analyze from $9/mo, Localize $9 or $29/mo.
  • Selling adds an Ecommerce plan: Standard $29/mo with a 2% transaction fee, Plus $74/mo and Advanced $212/mo at 0%, plus whatever Stripe or PayPal charge you.
  • Separate mandatory platform cost from optional apps, internal labor and one-time projects.
  • Model usage and fees from actual traffic, content, submissions, seats and commerce.
  • Compare alternatives over the same period and requirements; custom operation is not free.

Direct

Site, Workspace, add-ons and provider invoices.

Usage

Visits, bandwidth, CMS items, seats, forms and the store.

Operation

Design, content, engineering, support and incidents.

Period

One-time plus recurring cost over a fixed horizon.

What does Webflow cost when you add everything up?

Checked against Webflow's own pricing page on August 2, 2026: Site plans are Starter at $0, Basic at $15/mo billed yearly and Premium at $25/mo billed yearly, all quoted per site in USD before tax. Basic carries 300 static pages and 10 GB of monthly bandwidth but no CMS at all; Webflow states Basic is “specifically for sites that do not use any CMS or Ecommerce features”, so a single Collection puts the site on Premium. Platform plans are Team at $2,500/mo on an annual contract and Enterprise, for which Webflow publishes no figure. Team includes a site and Workspace; do not add another Site plan charge for its included site. Additional sites and extras require a quote from Webflow. We rechecked that bundle on September 18, 2026. For standalone Site plans, a paid Workspace plan may be a separate purchase, from $19/mo billed yearly for Core in the August snapshot. Those are the plan numbers; the rest of this page is what your invoice adds on top. Verify against the current pricing page rather than copying an old annual price table. If you are also pricing the other side of the decision, our Webflow migration cost breakdown and our Webflow migration service set out the same layers for a move away from the platform.

Cost layerEvidenceCalculation
Website planAccount plan page and invoiceCurrent recurring charge plus applicable overages
WorkspaceMembers, roles and required featuresCurrent charge for the needed collaboration model
Webflow add-onsLocalization, Analyze, Optimize or other enabled productsCurrent subscription and usage terms
Connected toolsInvoices for forms, search, membership, automation and analyticsRecurring fees plus usage and implementation
CommercePlan, processor and sales statementsSubscription, transaction, processing and app costs
PeopleTimesheets or a bounded allocationDesign, content, engineering, review and support hours

The recurring line items teams miss

Seven lines, and not one of them appears on the Webflow invoice, which is exactly why a cost review built from that invoice alone comes out low. Each gets bought separately and remembered separately. Added up once, the total usually surprises whoever signed off the plan price.

  • Domain, email and DNS, which are separate from the website plan.
  • Additional Workspace access, roles or client collaboration.
  • Localization, analytics, experimentation and consent tooling.
  • Forms, file storage, sending email, search, memberships and automation.
  • Ecommerce apps, payment processing, transaction costs and customer support.
  • Agency retainers, freelance work or internal design and engineering time.
  • Accessibility work, security, testing, backups, someone on call, and anything compliance requires.

Forms are the clearest example of a figure the summaries get wrong. Webflow's form documentation states that the free Starter Site plan is capped at 50 submissions in total, that the cap does not reset, and that submissions are unlimited on every other Site plan. There is no per-block overage. The cost sits in storage instead: form file uploads are free to 10 GB, then $0.50 per GB per month, with a hard limit at 100 GB. Checked August 2, 2026. That does not make forms costless either: spam handling, routing, CRM integration, consent, retention and operations can still create work or vendor spend.

"Webflow has no single real monthly cost. It has a total that changes with the account, the features and what you connect to it.

What a Workspace and its seats actually cost

This is the half of the bill that sits behind a tab on Webflow's pricing page and gets left out of most cost comparisons, including the AI-generated ones. Read on August 2, 2026: every account includes a free Starter Workspace with one full seat and two staging sites. Core is $19/mo billed yearly and Growth is $49/mo billed yearly. On top of the plan, extra seats are charged per person: a Full seat, which designs sites or manages admin settings, is $39/mo billed yearly; a Limited seat, which edits content and builds pages from components, is $15/mo; reviewer and commenter seats are free. Webflow AI usage is metered separately, with 2,000 credits a month at $20/mo billed yearly.

One feature hides inside those plan tiers, and one widely repeated claim about them is wrong.Code export requires Core, so $19/mo is the floor for getting your own markup out. But 301 redirects are not a Growth feature, and we had that wrong here until we checked it. Webflow's own documentation is explicit: redirects need a paid Site plan, or a Workspace on a paid Workspace plan. If you are publishing the site at all you are already on a paid Site plan, so redirects come with it and there is no extra $49/mo to preserve search traffic when URLs change. Budget Growth for what it genuinely adds, site-level roles, publishing permissions and password protection, rather than for the ability to redirect.

The arithmetic that catches teams: a five-person marketing team on Growth is $49 plus four additional seats. Put them all on Full seats and that is $49 + $156 = $205 a month before a single Site plan is paid for. Put the three who only write copy on Limited seats and it is $49 + $39 + $45 = $133. Auditing who genuinely needs a Full seat is the fastest saving on this whole page, and it takes about ten minutes in the members list.

A seat change lands on August 4, 2026

Webflow's feature sunsets page, read on August 3, 2026, states that the legacy Editor and legacy Editor whitelabeling become unavailable starting August 4, 2026, and that existing legacy Editor users are automatically given access to a free client seat or a limited seat as part of the migration. Those two outcomes are not the same line on your bill: reviewer and commenter seats are free, while a Limited seat is $15/mo billed yearly. If clients or colleagues have been publishing through the legacy Editor, check which seat each of them was actually assigned before you finish this calculation.

How the bill changes as the site grows

Do not use one generic traffic threshold. Model the variables the current plan and connected vendors bill for: visits, bandwidth, CMS items, locales, seats, form storage, orders, messages or automation runs. Add a low, expected and high scenario and identify the point where a plan or architecture change is triggered.

Code export changes the exit calculation

Webflow's help center puts it directly: “Code export is only available on Workspace plans — that is, Site plans do not include the ability to export your site's code.” The cheapest paid Workspace plan that includes it is Core at $19/mo billed yearly, on top of whatever the Site plan costs. Exported HTML, CSS, JavaScript and assets do not include working CMS, ecommerce, User Accounts, localized content beyond the primary locale, code components, password protection, native form processing or site search. A future move therefore includes replacement and migration work, not merely hosting the ZIP. We look at those dependencies separately in our guide to the Webflow User Accounts timeline and in do you own your website.

Does Webflow have a PageSpeed ceiling you should budget for?

There is no fixed Webflow PageSpeed ceiling to enter as a line item in your cost model, because no such platform-wide number exists. Measure the live site by representative route, field Core Web Vitals where available and repeatable lab tests. If a performance problem consumes engineering time or affects a measured funnel, add the observed cost and uncertainty to the decision model without claiming the platform caused a ranking or revenue result.

Is Webflow actually free?

Free to build with, not free to launch. The Starter Site plan is $0 and it publishes to a webflow.io subdomain with two static pages, 1 GB of bandwidth, a limited CMS and a hard cap of 50 form submissions that never resets. The free Starter Workspace is genuinely useful for designing and staging, and it includes one full seat. What $0 does not buy is a custom domain, which is where a real site starts, so the honest floor for anything public is $15/mo on Basic, and $25/mo on Premium the moment you want a CMS. Read from Webflow's pricing page on August 2, 2026.

Is Webflow worth it in 2026?

For a marketing site that one or two people edit and nobody needs to export, yes, and the total above is a fair price for not employing a developer. It stops being worth it at three specific thresholds, all of which you can check today rather than guess at. The first is the seat count, because a Full Workspace seat is $39/mo per person and a Limited one is $15/mo, so that line grows with your team rather than with your traffic. The second is the add-on mix, because Optimize from $299/mo and Localize can each cost more than the site plan they sit on. The third is the moment somebody asks for the code, at which point a paid Workspace plan is the entry fee and what you get back still excludes the CMS, the store and anything behind a login.

Notice that none of those thresholds is about design or speed, which is where the argument usually gets had. Webflow is a good product and the reason teams leave it is almost never that it stopped working. It is that the bill grew along an axis nobody priced at the start. Run the ten-step audit below on your own account and you will know which of the three you are closest to, which is a more useful answer than anyone else's verdict.

How to price downtime risk without an outage count

Use Webflow's current status history and your monitoring to document incidents affecting the site. Price the business requirement through service levels, dependencies, recovery, incident response and any contractual remedy. A historical outage count does not establish the future cost of Webflow or the reliability of a custom alternative.

Audit your Webflow cost in ten steps

Ten steps, and the first three take about ten minutes because the information is already sitting in your account. The rest is the actual work: mapping each dependency to a business workflow, which is what tells you whether a line is removable or load-bearing. Keep the order, because step ten is only answerable once step eight is.

  1. Export the last twelve months of Webflow and connected-vendor invoices.
  2. Record the live Website and Workspace plan, renewal date and billing period.
  3. List every enabled Webflow add-on and responsible owner.
  4. List the outside tools doing your forms, search, memberships, automation, analytics and selling.
  5. Capture billed units and actual use for each service.
  6. Record internal and external hours for content, design, engineering and support.
  7. Map each dependency to a required business workflow.
  8. Document export, data, cancellation and replacement constraints.
  9. Build twelve, twenty-four and thirty-six month scenarios.
  10. Choose retain, right-size, consolidate, replace or investigate with an owner and date.

What to do once you have your total

Four routes, and three of them keep you on Webflow. That is the honest distribution: most cost reviews end in right-sizing a plan and removing tools nobody owns rather than in a migration. Pick the route your total actually supports, not the one you suspected before you started counting.

  • Retain Webflow when the managed editor and features justify the complete cost.
  • Right-size plans or remove tools after verifying dependencies and rollback.
  • Optimize the implementation when the platform fits but the site has correctable UX or performance problems.
  • Migrate when unmet requirements, portability, control or total cost justify the transition and ongoing responsibility.

Each of those routes has its own article. Read what leaving Webflow involves before committing to a transition, compare the two operating models in Webflow versus a custom website, and look at the projects we have delivered to see what a scoped build actually contains.

Compare a custom alternative honestly

PandaCodeGen's migration planning tiers start at $1,500 Starter, $3,500 Growth and $5,000 to $10,000 Scale. A custom target can still require hosting, CMS, forms, email, databases, monitoring, security updates and engineering. Compare both options on the same requirements, usage and operating period. There is no universal savings percentage or payback. The full tier detail sits on our pricing page, the build variables are unpacked in what a website costs and what drives migration cost, and application-level work is described under custom engineering.

The evidence standard we hold ourselves to

You will not find an unnamed client bill or a ranking anecdote used as proof on this page. When we publish a result, it comes with the relationship it came from, the date, how it was measured and what the measurement does not tell you. Projects connected to our own founders are labeled as founder-affiliated rather than presented as independent client proof. Apply the same test to any figure you are shown while comparing platforms: if the source, date and method are missing, it is not a number you can plan a budget around.

Frequently asked questions

Frequently Asked Questions

Is Webflow worth it in 2026?

For a marketing site that one or two people edit and nobody needs to export, yes. It stops being worth it at three thresholds you can check today. Seat count, because a Workspace seat is charged per editing person and grows with your team rather than your traffic. Add-on mix, because Optimize from $299/mo and Localize can each cost more than the site plan they sit on. And the moment somebody asks for the code, because a paid Workspace plan is the entry fee and what you get back still excludes the CMS, the store and anything behind a login. None of those thresholds is about design or speed, which is where the argument usually gets had.

How much does Webflow actually cost per year?

Webflow's published Site plan prices on August 2, 2026 are $15/mo billed yearly for Basic, which has no CMS, and $25/mo billed yearly for Premium, which does, so $180 or $300 a year per site before anything else. Add a Workspace plan if you need code export or extra seats: Core is $19/mo billed yearly, Growth $49/mo. Add-ons are separate and usage-priced: Optimize from $299/mo, Analyze from $9/mo, Localize $9 or $29/mo. Selling needs an Ecommerce plan: Standard $29/mo with a 2% transaction fee, Plus $74/mo and Advanced $212/mo at 0%, all billed yearly, with Stripe or PayPal charging their own processing fees on top. All prices are USD, per site, before tax. Your own yearly total is those figures plus connected vendors, agency work and internal time, which Webflow does not publish and you take from twelve months of invoices.

Is Webflow good for SEO?

Webflow provides relevant site and page controls, while results depend on the rendered implementation, content, links, crawlability, metadata, structured data and experience. No platform guarantees rankings. Audit the actual site rather than inferring an outcome from the platform name.

Can I migrate from Webflow to Next.js without losing SEO?

Your Webflow slugs are already yours, so the addresses often carry over with light mapping. Budget the risk where it actually sits: the CMS, site search, localization and anything gated do not export, so those pages are rebuilt and can lose content or structured data in the rebuild. Verify the rendered output rather than assuming a clean copy.

What are the limitations of Webflow?

Current code export excludes working CMS, ecommerce, User Accounts, localized content beyond the primary locale, code components, password protection, forms and site search. Feature and plan limits also vary. Decide whether those boundaries matter to the specific requirements.

When should I leave Webflow for custom code?

Consider migration when verified experience, data, integration, portability, release or total-cost requirements justify the transition and ongoing engineering responsibility. Optimize or right-size Webflow when the platform still fits. There is no universal traffic or payback threshold.

Primary sources

Get a like-for-like migration plan

We will reconcile the current Webflow system and compare it with a scoped custom operating model. The result is a decision document, not an automatic recommendation to migrate.