Webflow Pricing in 2026: The Site-Plan vs Workspace-Plan Split (and the Total Cost Most People Miss)

Quick answer: Webflow charges on two axes at once, and that is the whole source of the confusion. A Site plan hosts one website and unlocks your custom domain. A Workspace plan covers the team building it and is billed per seat. You usually need both, which means the number on the pricing card is rarely the number on your invoice. As of November 2026, paid Site plans start in the mid-teens per month billed yearly, Ecommerce starts higher and adds a transaction fee, and Workspace seats stack on top. Check Webflow's live pricing before you budget - they restructured the tiers in May 2026 and third-party numbers go stale fast.

Most "how much does Webflow cost" guides answer the wrong question. They quote one number for a tier and move on. Webflow does not work that way. You are paying for two different things on two different meters, and the pricing page presents them side by side without making the dependency obvious. If you are new to the platform, start with what Webflow is and then come back here, because the pricing only makes sense once you know what the two meters are actually metering.

Webflow has two price tags, not one

Here is the split that trips everyone up.

A Site plan is attached to a single published website. It is what lets you connect a custom domain, raise your CMS item and bandwidth limits, and remove the Webflow badge. One Site plan equals one live site. Three client sites equal three Site plans.

A Workspace plan is attached to your team, not your site. It governs how many people can build, how many unhosted projects you can keep in progress, and which features your designers get access to. It does not host anything and it does not give you a custom domain.

The practical consequence: a solo freelancer can often live on the free Starter Workspace and just pay for one Site plan per client project. A team of five building one product pays for one Site plan plus five Workspace seats. The two numbers are independent, and the bigger one is frequently the Workspace side, not the hosting side. Several pricing breakdowns describe this two-part billing as the single most misunderstood part of Webflow. It is the thing to internalize before you compare Webflow to anything else.

Site plans: what you pay to publish one website

Site plans are the hosting tier. As of November 2026, the non-commerce ladder runs roughly like this (Webflow consolidated some of these in a May 2026 pricing change, so names and limits may differ on the live page - verify before committing):

The real decision on this ladder is the CMS item limit. Sources disagree on the exact counts (CMS lands somewhere around 2,000 items, Business around 10,000), and Webflow sells add-on item capacity if you blow past the ceiling. If you are running a content operation that publishes daily, model your item count over two years, not two months - the jump between tiers is driven almost entirely by how much dynamic content you store. Billed monthly instead of yearly, every one of these tiers costs meaningfully more, often 20 to 33 percent more. The yearly commitment is the quiet default that makes the headline prices look reasonable.

Ecommerce plans: the transaction fee is the real variable

If you are selling, you are on a different Site-plan ladder - Standard, Plus, and Advanced - and the sticker price is not the number that matters. The transaction fee is.

As of November 2026, the Standard tier carries a Webflow transaction fee of around 2 percent on every sale. Plus and Advanced drop that fee to 0 percent but cost more up front. Stripe or PayPal processing fees (roughly 2.9 percent plus a fixed amount) apply on top of all of them - that is the payment processor, not Webflow, and no plan removes it.

The math that decides your tier is a break-even, not a feature list. At roughly 2 percent, the Standard fee quietly costs you more than the price gap to Plus once you are doing a few thousand dollars a month in sales. Several breakdowns put that crossover around the low-thousands-per-month range. Product count ceilings climb with the tiers too (Standard around 500 products, the higher tiers into the thousands), but for most stores the fee crossover hits before the product limit does. Run your own expected monthly revenue through the fee before you pick a plan - the "cheaper" Ecommerce tier is often the more expensive one.

Workspace plans: what you pay for the team

The Workspace ladder for teams and freelancers runs Starter (free), Core, and Growth, with Agency and Enterprise options above that. These are billed per seat, per month.

Starter is genuinely free and fine for one person evaluating the platform or building a single site. Core and Growth raise the number of unhosted staging projects, unlock code export and advanced collaboration, and add staging and publishing controls that matter once more than one person touches the site. As of May 2026, every Workspace plan also includes a monthly allotment of AI credits (different amounts per tier), with paid top-ups available if your team burns through them - a new meter worth watching, because it did not exist in earlier pricing.

The thing to notice: Workspace cost scales with headcount, not with traffic. A five-person team pays five times the per-seat rate before a single visitor loads the site. For an agency running many client projects, this is usually the dominant line on the bill.

The add-ons that turn into the real bill

The tier price is the floor. The add-ons are where the total actually lands:

Extra seats. Beyond your base seats, Webflow bills additional collaborators by type. As of November 2026 a full seat runs around $39/month, a limited seat around $15/month, and reviewer seats are free. On a growing team this line moves fast.

Localization. Multi-language sites are priced per locale as an add-on, not included in the base Site plan. Costs run per locale per month and climb with asset localization and localized URLs. If you serve three or more languages, price this separately.

CMS item and capacity add-ons. Hit your item ceiling and you buy more rather than being forced up a full tier. Useful, but it is another recurring line.

AI credit top-ups. The included Workspace credits are capped. Teams leaning on Webflow's AI features buy more monthly.

None of these are hidden in a sinister sense - they are just not on the headline card, and they are exactly the costs that make a Webflow quote come in higher than the tier page suggested. It is the same pattern we mapped for AI app builders in the hidden-costs breakdown: the base plan is honest, the total is assembled from parts.

The total most people miss

Put the two meters together with a concrete case. A three-person team building one content-driven marketing site, billed yearly:

• One CMS Site plan for the live site.
• Three Workspace seats for the team.
• Maybe a localization add-on if the site ships in two languages.

Published breakdowns put a setup like that comfortably into the $70 to $90+/month range once both meters are running, before any seat growth or add-ons. The Site plan alone would have suggested a third of that. That gap - between the hosting number people quote and the all-in number people pay - is the single most important thing to understand about Webflow pricing. If you want the full feature-by-feature verdict, the 2026 Webflow review covers where the platform earns its cost and where it does not, and the alternatives guide covers when to look elsewhere.

For a straightforward marketing or content site, that all-in total is reasonable for what you get: a genuinely strong visual builder, solid hosting, and a CMS that real teams run. Webflow is priced fairly for the job it does best.

Where Creatr Fits

Webflow's pricing makes sense for marketing sites, portfolios, blogs, and content-driven stores. The cost story changes the moment you need real application behavior - multi-role authentication, row-level data isolation so one tenant cannot read another's records, integrations that handle failure instead of assuming the happy path, data that stays correct under load. That is not a CMS problem, and no Site-plan tier solves it.

Creatr, also known as DeepBuild, is a managed AI product studio for exactly that layer. It builds, hosts, and runs a production-grade web app in about 24 hours, with humans in the loop on the "production 30 percent" - the auth, isolation, failure handling, and correctness that decide whether an app survives real users. You own the code outright. When the question stops being "which hosting tier" and becomes "will this actually work for a hundred users with different roles," that is the line where a managed build fits and a site builder does not.