Webflow Pricing 2026: Free Tier Limits, CMS Costs & When to Upgrade
By Nayan Kyada · · 6 min read
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:
- Workspace plans — cover staging sites, collaboration features, and seats for the people working inside the Designer and CMS. Free for one full seat; paid tiers unlock more staging, roles, and permissions, and extra seats cost more.
- 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 Starter site plan is a staging environment, not a production option. Key limits per Webflow's pricing page as of October 2026:
- Custom domain: not included — your site sits on a
.webflow.iosubdomain - Static pages: 2
- CMS items: 50
- Form submissions: 50
- Bandwidth: 1 GB per month
- Seats: the free Starter Workspace includes one full seat
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)
Webflow restructured its site plans, so many comparisons still quote the older Basic/CMS/Business lineup. The current self-serve site plans, billed yearly, per site:
| Plan | Price/month (billed yearly) | CMS items | Bandwidth | Static pages | Forms |
|---|---|---|---|---|---|
| Starter | $0 | 50 | 1 GB | 2 | 50 |
| Basic | $15 | — (no CMS) | 10 GB | 300 | Unlimited |
| Premium | $25 | 20,000 | 50 GB, with paid add-ons up to 2.5 TB | 300 | Unlimited |
| Team (platform plan) | $2,500 (annual contract) | — | — | — | — |
| Enterprise | Custom | Custom | Custom | Custom | Custom |
Month-to-month billing costs noticeably more (Webflow advertises savings of up to 40% for yearly billing). Premium is the default recommendation for content-driven sites, and its 20,000-item cap is generous for most marketing sites — but a large multilingual library or product catalogue can still get there.
Workspace plan pricing (2026)
| Plan | Price/month (billed yearly) | Who it's for |
|---|---|---|
| Starter | $0 | 1 full seat, 2 staging sites |
| Core | $19 | 10 staging sites, custom code, code export |
| Growth | $49 | Unlimited staging sites, site-level roles, publishing permissions |
| Freelancer | $16 | Freelancers with a small client roster; 1 free client seat per site |
| Agency | $35 | Agencies; unlimited staging sites, 3 free client seats per site |
| Enterprise | Custom |
Each Workspace plan includes one full seat for the owner; additional seats are billed on top, so a multi-person team pays per seat in addition to the plan. Check Webflow's pricing page for current per-seat rates before you quote a client.
The real upgrade triggers
No CMS on Basic. Basic is static-only. The first blog post or CMS collection pushes you to Premium.
Seats. Workspace plans include one full seat; every additional designer or editor adds seat cost. The freelancer and agency plans include free client seats per site, which helps for client handoffs.
Bandwidth. Premium includes 50 GB. Image-heavy sites with meaningful traffic hit it, and more bandwidth is a paid add-on (for example, +50 GB is $20/month billed annually). Webflow says two consecutive months over the limit triggers an automatic plan upgrade.
CMS item limit. Premium caps out at 20,000 items. Beyond that you're talking to Webflow about the Team or Enterprise plans.
Add-ons. Features beyond the core site plan — such as Localization, Optimize, and Analyze — are add-ons with their own pricing. These are not included in a 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 — $25/month per site on Premium (billed yearly), 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 $25/month each, that is $250/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 often 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: $0 on Free (up to 20 seats, 1M API CDN requests/month), or $15 per seat/month on Growth
- Vercel Pro: $20/month per member (one team, multiple projects)
- Total: ~$20/month on Sanity Free, or ~$65/month with three Sanity Growth seats
For a single site with one development team, Webflow Premium ($25/site/month plus workspace seats) 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)
- Full control over rendering — Webflow now supports code components, but pages still render through Webflow's own pipeline
- Native support for ISR, SSR, or edge rendering on your Webflow-hosted site
- A typed content layer like Sanity TypeGen
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.