Webflow Pricing 2026: Free Tier Limits, CMS Costs & When to Upgrade

Webflow pricing confuses most buyers because the plan structure splits across two separate billing axes — site plans and workspace plans — and the thresholds that force an upgrade are not always obvious until you hit them. This post maps out exactly what you get for free, where the real costs kick in, and when Webflow stops being cost-effective compared to a headless alternative.

How Webflow pricing is structured

Webflow bills on two dimensions simultaneously:

1. Workspace plans — cover how many editors and guests can collaborate inside the Designer and CMS panel. Free forever for one person; paid tiers unlock additional collaborators and roles.
2. Site plans — cover what a published site can do: custom domain, CMS item limits, form submissions, bandwidth, and e-commerce.

You pay both. A small marketing agency might have one workspace plan covering all their sites, plus individual site plans for every client property. That stacking is the first thing that surprises teams moving from WordPress or Squarespace, where there is one bill.

Free tier: what you actually get

Webflow's free tier is a staging environment, not a production option. Key limits as of September 2026:

• Custom domain: not included — your site sits on a .webflow.io subdomain
• CMS items: 50 across all collections
• Form submissions: 50 per month
• Bandwidth: 1 GB per month
• Editors: 0 (no client-facing CMS editor access without a paid site plan)

You can prototype and hand off a preview URL, but the moment a client needs their own domain, real form volume, or more than a handful of blog posts, the free tier is gone.

Site plan pricing (2026)

Month-to-month prices run roughly 30–35% higher. The CMS plan is the default recommendation for content-driven sites, but 2,000 items sounds generous until you model a real content library — 800 blog posts, 400 product pages, 200 team bios, and a few hundred case studies gets you there faster than expected.

Workspace plan pricing (2026)

The Core plan bills per-seat at $19/seat/month (annual). A three-person editorial team adds $57/month before any site plan costs. The Growth plan at $49/seat is aimed at teams that need advanced permissions and white-label client portals.

The real upgrade triggers

CMS item limit on the CMS plan (2,000 items). This is the most common reason teams escalate to Business. A multilingual site that uses one collection per language, or a site with a large product catalog, gets there quickly. There is no way to archive or soft-delete items to free up quota — items count whether they are published or draft.

Guest editor seats. The CMS plan allows 3 guest editors. A mid-size client with a marketing team of five needs the Business plan at $39/month just for seat headroom.

Bandwidth. 50 GB sounds reasonable, but image-heavy sites with meaningful traffic hit it. Webflow does not offer a CDN add-on — you either upgrade or implement a reverse proxy in front of the Webflow-hosted domain, which creates its own complexity.

Form submissions. 1,000/month on the CMS plan is enough for most marketing sites, but any site running paid campaigns with a lead-gen form will exceed this during a campaign sprint.

Logic and memberships. Webflow Logic (workflow automation) and Memberships are add-ons with their own per-action or per-member pricing. These are not included in any flat site plan.

Where Webflow pricing breaks down at scale

For a single marketing site with modest traffic and a small editorial team, Webflow's pricing is reasonable — $23–$39/month per site, plus workspace costs. The math gets uncomfortable in two scenarios:

Multiple client sites. An agency managing ten client sites pays ten separate site plan bills. At $23/month each, that is $230/month before any workspace costs. WordPress on shared hosting or a Sanity + Vercel stack looks significantly cheaper per-site at that volume.

High CMS volume with dynamic filtering. Webflow's CMS does not support server-side filtering or dynamic pagination beyond what its native collection lists allow. Sites that need faceted search, user-specific content, or CMS-driven data beyond the item limits must reach for Webflow's API and build custom front-ends — at which point you have most of the complexity of a headless setup but are still paying Webflow's hosting margins.

Webflow vs. headless: where the cost curve crosses

A comparable Sanity + Next.js + Vercel setup for a content-heavy marketing site runs roughly:

• Sanity Growth plan: $15/month (up to 3 non-admin users included, 100k API CDN requests/day)
• Vercel Pro: $20/month (covers one team, multiple projects)
• Total: ~$35/month

For a single site with one development team, Webflow Business ($39/site/month) and the headless stack are close. Add a second site and the headless stack's costs barely move while Webflow doubles. Add five sites and the gap is significant.

The crossover for most agency or multi-site setups sits around three to four active client sites — beyond that, a shared Sanity organization and Vercel team deliver more CMS flexibility and lower per-site cost.

What you do not get regardless of plan

• Git-based version control for code (Webflow's Designer outputs proprietary markup)
• Component-level code customization without JavaScript embeds
• Native support for ISR, SSR, or edge rendering
• Structured data / JSON-LD injection without custom code embeds
• TypeScript or any typed content layer

None of these are dealbreakers for a pure marketing site with a non-technical team. They matter the moment the site needs dynamic behavior, personalization, or a content model that outgrows Webflow's collection structure.