Webflow hosting cost: two plans, not one
**Site plans** are per website. They cover hosting, the CDN, SSL, backups, form submissions and the custom domain. This is the number people mean when they ask what Webflow costs, and for a business site it is genuinely all-in — there is no separate host, no separate SSL, no backup service.
**Workspace plans** are per person editing in the Designer. A solo studio needs one seat; a team where three people build needs three. This is the line that gets missed in comparisons, and it is the one that scales with headcount rather than with traffic.
The distinction matters because they answer different questions. A business with one site and one editor pays for one of each. An agency with twenty client sites pays twenty site plans and a handful of seats.
What the site plan actually includes
Global CDN delivery, SSL, and versioned backups you can restore from a list. On WordPress each of those is a decision, a vendor and a renewal; here they are not line items because they are not optional.
Form handling with submissions stored and emailed, up to a monthly cap that most business sites never approach.
And the thing that does not appear on the page: no updates. There is no core to patch, no plugin to break a layout on a Tuesday. That absence is most of what the plan is buying — the arithmetic is in what upkeep actually costs.
The two that surprise people after launch
**Localization.** Running the site in a second language is an add-on priced per locale, not a feature of the plan. It is good, and budgeting for it in month four rather than month one is a common and avoidable annoyance — two languages covers what it involves.
**CMS item limits.** Every site plan has a ceiling on CMS items, and a catalogue or a large archive can meet it. Most business sites never come close; a site generating thousands of pages from data needs the number checked before the build rather than after. See what Webflow cannot do.
Neither is hidden — both are on the pricing page. They surprise people because nobody reads a pricing page for the thing they have not yet decided to need.
Who should not be paying for this
A site with genuinely enormous content volume, an application with user accounts and business logic, or a store whose operations are the product. In each case the money is better spent elsewhere and we would say so — Webflow or Shopify is that conversation for commerce.
Also: anyone paying for a Workspace seat who never opens the Designer. Editors work in the Editor, which is not a seat, and teams routinely over-buy here because the distinction is not obvious.
For everyone else the comparison is not per-month against per-month. It is one predictable renewal against an assembled stack with several, and the assembled stack has an unbilled maintenance line running underneath it.
Questions we get asked
What does Webflow hosting include?
Global CDN delivery, SSL, versioned backups, form handling and a custom domain, on a per-site plan. There is no separate host, SSL vendor or backup service, and no software for you to update — that absence is most of what the plan buys.
Why are there two different Webflow prices?
Site plans are per website and cover hosting; Workspace plans are per person building in the Designer. Comparisons usually quote only the first. A business with one site and one editor pays one of each; an agency pays many site plans and a few seats.
What costs extra on Webflow after launch?
Localization is priced per locale as an add-on rather than included, and CMS item limits can be reached by large catalogues or archives. Neither is hidden, but both tend to arrive as surprises because they are decided after the build rather than before.