What Webflow actually costs once the site is on it

Webflow's pricing is public and I am not going to reprint it here, because a price list in a blog post is wrong within a year and this site has opinions about stale numbers. What is worth writing down is the shape of the bill, which does not change: what you are actually paying for, and the three things that push it up without anyone deciding to.

Read this alongside Webflow's pricing page, not instead of it.

Two bills, not one

This is the part that catches people, because most platforms have one.

A site plan is charged per published site. It is what makes the domain work, and the tier determines the CMS limits: how many collections, how many items, how much traffic.

A workspace plan is charged per person who needs to get into the Designer. It has nothing to do with how many sites you have.

So a company with one site and five marketers is not paying for one thing five times. It is paying for one site plan and however many of those five genuinely need Designer access, which is usually fewer than five, because editing content does not require it.

What forces you up a tier

Three things, and none of them is a decision anyone consciously makes.

Collection and item counts. Every site plan caps both, and the caps are not raisable by asking. A resources library, a location directory or a product catalog grows quietly until it does not fit. What Webflow will not do has more on where those ceilings sit.

Form submissions. The entry tier limits them. A form that starts working is a good problem, but it is one that changes your plan.

Needing a CMS at all. The cheapest tier does not include one. A brochure site is fine on it right up to the day someone wants a blog, at which point the plan is no longer a choice.

What you budget against what you are billed

That third row matters more than the others and nobody counts it. A marketing site that talks to a CRM, an analytics tool, a scheduler and an email platform is paying four subscriptions that have nothing to do with Webflow. The integration pages say what each one is actually for; the invoices are separate.

The honest comparison with what you left

WordPress hosting is cheaper than a Webflow site plan. That comparison is real and it is also incomplete, because the WordPress number does not include the maintenance the platform requires and Webflow does not: updates, plugin conflicts, security patching, and the developer hours those consume.

The right way to compare is total annual cost including whoever keeps it running. On a marketing site with no in-house developer, Webflow usually wins that comparison. On a site with a developer already on staff, it frequently does not, which is one of the honest cases for staying on WordPress.

The number to work out before you commit

Not "which plan is cheapest". It is:

How many items will this site hold in two years, and how many people need to build pages in it?

Those two answers pick the tier and the seat count, which is the whole recurring bill. Everything else is a rounding error against the cost of the site being wrong.