Webflow Pricing Explained: The Real Cost of Running a Webflow Site

Ask five Webflow users what they pay per month and you will likely get five different, confidently wrong answers. Webflow's pricing model is not complicated once it clicks, but the way it is presented online, split across two separate pricing pages with overlapping names, trips up almost everyone during their first year of running a Webflow development project. This post exists to remove that confusion before it costs you money in the form of a surprise overage or a plan you did not need.

The two stacked layers, and why people miss the second one

Webflow pricing is built from two separate subscriptions that almost nobody realizes are separate until they get a bill that does not match what they expected.

The first layer is your workspace plan, sometimes called a seat plan. This is what you or your agency pays to use the Webflow Designer and Editor, the tool where sites get built. It covers how many people can work in the workspace and how many projects (draft sites, not yet published) you can have. Workspace plans range from a free Starter tier up through Core and Growth tiers priced per seat, roughly $19 to $49 per member per month depending on the tier and billing cadence.

The second layer is the site plan, and this is the one people forget exists until launch day. Every individual website you actually publish to a custom domain needs its own site plan attached to it, billed separately from the workspace. This is the layer that includes hosting, CMS capacity, form submissions, and bandwidth. A business with three published sites under one workspace pays for the workspace once and then pays for three separate site plans on top.

This two layer structure is the single most common source of "why is Webflow so expensive" complaints, and it is almost always because someone budgeted for the workspace plan and forgot the site plan exists, or vice versa.

CMS item limits

Webflow's CMS plans cap the number of items you can store in your collections (blog posts, product listings, team members, case studies, anything structured). The Basic CMS site plan allows 2,000 items, the CMS plan allows the same 2,000 item ceiling with more collections and higher submission limits, and the Business plan raises that to 10,000 items. Enterprise plans go higher but require a custom quote.

This matters more than it sounds. A blog publishing three posts a week for five years accumulates around 780 posts, well within limits. But a directory site, a large product catalog, or a site with multiple content types each drawing from the same pool (blog posts, author bios, categories, tags, testimonials all count as items) can approach 2,000 faster than expected. We have seen content-heavy sites hit their CMS ceiling within 18 months of launch.

Form submission limits

Each site plan tier includes a monthly form submission allowance: 500 on Basic, 1,000 on CMS, and 2,500 on Business plans, with overages typically billed per additional 500 submissions beyond the cap. For a contact form receiving a dozen submissions a week, this is a non-issue. For a lead generation site running paid traffic to a quiz, calculator, or multi-step form, submission volume can climb quickly and quietly exceed the plan's included allowance.

Ecommerce transaction fees

If you run Webflow Ecommerce, there is a third cost layer specific to that plan type: a transaction fee on top of your site plan and your payment processor's own fee (Stripe or PayPal, typically around 2.9 percent plus 30 cents per transaction). Webflow's own ecommerce transaction fee varies by plan tier and can be reduced or eliminated on higher tiers, but on entry-level ecommerce plans it typically runs around 2 percent per transaction in addition to processor fees.

For a store doing $20,000 a month in revenue, a 2 percent platform fee is $400 a month that a Shopify or WooCommerce store would not necessarily pay in the same form. This is one of the clearer signals that Webflow Ecommerce is built for smaller catalogs and moderate volume rather than a business planning to scale ecommerce revenue aggressively.

Localization add-ons

Webflow's native localization feature, which lets you build multilingual or multi-region versions of a site within one project, is a paid add-on layered on top of an Enterprise-tier site plan, and its cost scales with the number of locales you activate. For a business seriously targeting three or four language markets, this can add a meaningful line item that a WordPress site using a plugin like WPML would not carry as a platform fee, even though WPML has its own licensing cost.

Realistic annual totals for three scenarios

These figures combine workspace seat costs and site plan costs at typical, publicly listed rates, assuming annual billing (which is meaningfully cheaper than monthly across the board).

Scenario 1: Small marketing site. One workspace seat on a Core plan, one site on a CMS site plan, no ecommerce, minimal form volume. Workspace: roughly $228 a year. Site plan: roughly $276 to $324 a year. Total: approximately $500 to $600 a year, before any third party tools.

Scenario 2: Content-heavy site with a large CMS. Two workspace seats (a marketer and a designer) on Core, one site on a Business site plan to cover the higher CMS item ceiling and submission volume. Workspace: roughly $456 a year for two seats. Site plan: roughly $700 to $900 a year. Total: approximately $1,200 to $1,400 a year, and this is before Finsweet or Jetboost add-ons discussed below.

Scenario 3: Ecommerce site with moderate volume. One or two workspace seats plus an Ecommerce site plan, which starts higher than the standard CMS tiers, roughly $1,000 to $1,600 a year for the plan alone, plus the 2 percent transaction fee layered on top of processor fees. At $15,000 a month in sales, transaction fees alone add roughly $3,600 a year. Total: approximately $4,600 to $6,000 a year once transaction volume is factored in, before third party apps.

Third party tools people end up adding

Webflow's native functionality covers a lot, but most real client sites eventually add at least one of the following, and these costs are almost never included in anyone's original budget.

• Finsweet. Free and paid attribute-based tools for advanced CMS filtering, sorting, and pagination. Many core attributes are free; premium tools like the CMS Filter or the paid client-first framework support run $0 to a few hundred dollars depending on usage.
• Jetboost. Real-time search, filtering, and wishlist functionality that Webflow does not offer natively. Plans generally run $19 to $69 a month depending on site traffic and feature tier.
• Memberstack. User authentication and gated content, since Webflow has no native membership system. Pricing generally starts around $29 a month and scales with member count and feature needs.
• Make (formerly Integromat). Workflow automation connecting Webflow forms or CMS to other tools like CRMs or email platforms. Free tier exists, but active automation usage typically lands in the $9 to $29 a month range and climbs with volume.

A site using two or three of these tools can easily add $600 to $1,800 a year on top of the base Webflow subscription costs, and this is the layer that catches budget-conscious clients off guard because none of it appears on Webflow's own pricing page.

Where the surprise overages actually come from

In our experience running dozens of Webflow builds, overages trace back to three predictable causes.

1. Underestimating CMS growth. A site launches with 300 items and a Basic or CMS plan, then the marketing team gets serious about content and blows past 2,000 items within two years without anyone checking the dashboard.
2. Traffic-driven form volume spikes. A successful ad campaign or a viral moment sends form submissions well past the monthly allowance in a single month, triggering overage charges nobody budgeted for.
3. Adding a published staging or client preview site without realizing it needs its own site plan. Because only the workspace is shared, every additional live domain, including a client's staging environment, needs its own paid site plan.

How to avoid pricing surprises

Before committing to a plan, forecast your CMS item count two to three years out, not just at launch, and choose the tier with room to grow rather than the cheapest one that barely fits today. Check your expected form volume against realistic marketing plans, not current traffic. If ecommerce transaction fees will meaningfully eat into margin at your target revenue, model that cost explicitly against a Shopify alternative before committing. And budget for at least one third party tool from day one, because most content-rich or interactive sites need at least one.

If you want an accurate, itemized quote for your specific site rather than working from general ranges, our Webflow development team can map out the exact plan tier and third party tools your project needs before you commit to anything. You can see the plan tiers and tool stacks we have used on real projects in our case studies.

FAQ

Do I need a workspace plan and a site plan, or just one?

You need both. The workspace plan covers who can build the site, and the site plan covers hosting, CMS capacity, and bandwidth for each published domain. Skipping the site plan means your site cannot go live on a custom domain.

What happens if I exceed my CMS item limit?

Webflow will prompt you to upgrade to a higher site plan tier before you can publish new items beyond your cap. It is not an automatic overage charge, but it does force an upgrade decision, often at short notice.

Is Webflow cheaper than Shopify for ecommerce?

It depends on transaction volume. At lower monthly sales, Webflow's flat plan cost can be competitive, but its per-transaction fee on entry tiers means the gap narrows or reverses as sales volume grows, which is worth modeling against ecommerce development alternatives before committing.

Can I avoid the third party tool costs entirely?

For a simple brochure site, yes. Once you need advanced filtering, gated content, or workflow automation, a third party tool is usually faster and cheaper than a custom-coded workaround, so most growing sites end up adding at least one.

If you want a clear, itemized breakdown of what your specific Webflow site would actually cost per year, book a free 1-hour strategy call through our contact page and we will run the numbers with you.