The Webflow Business plan no longer exists. On 13 May 2026 Webflow merged its CMS and Business Site plans into a single Premium plan at $25 a month billed yearly, and added a Team plan at $2,500 a month between self-serve and Enterprise. Sites still on Business inside Freelancer or Agency Workspaces move to Premium at their first renewal on or after 16 November 2026, so for most agency-managed sites the comparison people search for, Enterprise vs Business, is now Enterprise vs Premium, with Team in the middle.
This page compares the three on cost, control, scale and support, using Webflow's pricing page as read on 13 November 2026, an archived copy of the same page from 1 May 2026, Webflow's own announcements, and Vendr's contract data for the one number Webflow does not publish. We build marketing sites in Webflow, so the bias is stated.
What replaced the Business plan
Webflow's announcement says the CMS and Business plans were combined "into one" to simplify the lineup, that CMS item add-ons are gone, and that existing customers move automatically when the change reaches their site. Sites in ordinary Workspaces switched at renewal on or after 29 June 2026; sites in Freelancer or Agency Workspaces, or on legacy pricing, switch on or after 16 November 2026. Switching to yearly billing before that date locks the old plan in for one more year.
| Limit | Business (archived 1 May 2026) | Premium (read 13 November 2026) |
|---|---|---|
| Price, billed yearly | $39 a month | $25 a month ($39 billed monthly) |
| CMS items | 10,000, add-ons to 20,000 | 20,000 included |
| CMS Collections | 40 | 40 |
| Static pages | 300 | 300 |
| Included bandwidth | 100 GB | 50 GB, add-ons to 2.5 TB |
| CMS API rate limit | 120 requests a minute | 120 requests a minute |
| Webflow Cloud requests | 10 million a month | 2 million a month |
| Webflow Cloud CPU | 120 minutes | 30 minutes |
| Hosting uptime | Standard agreement | Standard agreement |
Source: Webflow pricing page, archived 1 May 2026 and read 13 November 2026
For a former Business site that used more than 50 GB, the first bandwidth add-on is +50 GB at $20 a month billed yearly. Digidop, a Webflow agency, worked out that restoring 100 GB brings Premium to about $45 a month annualised, close to the old Business price. BRIX Templates reached the same conclusion: sites that were on Business for CMS items mostly pay less, and sites that were on Business for bandwidth need to check their usage before assuming a saving.
The practical point is that Premium is not a cut-down Business. It is Business with more CMS room, less included bandwidth and a lower list price. Nothing Business had in governance, security or support was taken away, because Business never had those things. They were always Enterprise features.
Premium, Team and Enterprise side by side
Webflow now splits its plans into Site plans (Basic and Premium, bought per site, alongside a Workspace plan for seats) and Platform plans (Team and Enterprise, which bundle the site, the Workspace, seats and some add-ons).
| Area | Premium | Team | Enterprise |
|---|---|---|---|
| Price | $25 a month billed yearly, plus Workspace and seats | $2,500 a month, annual contract | Custom |
| CMS items | 20,000 | 20,000 | Custom, over one million per site possible |
| CMS Collections | 40 | 100 | 100 |
| Fields per Collection | Not stated on pricing page | 100, including 20 reference fields | 100, including 20 reference fields |
| Static pages | 300 | 500 | Custom |
| CMS API rate limit | 120 requests a minute | 600 requests a minute | Custom |
| Seats | Bought separately | 5 full, 5 limited, up to 100 free | Custom |
| Publishing workflows and page branching | No | Yes | Yes |
| Custom roles, granular access, design approvals | No | No | Yes |
| Single sign-on, JIT provisioning, SCIM | No | No | Yes |
| Contract | Terms of Service | Terms of Service | Master service agreement |
Source: Webflow pricing page, read 13 November 2026; Webflow, Next-gen CMS for Enterprise, January 2026
Two details are easy to miss. Team keeps Premium's 20,000-item ceiling, so a site that has outgrown the item count has only one plan to go to. And the jump to one million items is an Enterprise feature by contract: Webflow's January 2026 announcement says total CMS storage "varies by Enterprise plan agreement", so the number in your order form is the one that counts.
The next-gen CMS architecture itself is no longer Enterprise-only. CMSWire reported in April 2026 that Webflow had moved every customer site onto it, with up to 40 Collection lists per page, 10 nested lists and 100 items per nested list. Those layout limits now apply on Premium too. Our Webflow CMS Limits in 2026 post covers the item and reference caps in more depth.
What each one costs
Premium has a list price. Team has a list price. Enterprise does not, and the gap between them is not a straight line.
A self-serve stack. A marketing team that wants roughly what Team bundles, on self-serve plans, would buy Premium at $25, a Growth Workspace at $49 for site-level roles and publishing permissions, four extra full seats at $39 each, five limited seats at $15 each and two Localize Advanced locales at $29 each. All prices are monthly, billed yearly, from Webflow's pricing page.
| Item | Self-serve | Team |
|---|---|---|
| Site plan | $25 (Premium) | Included |
| Workspace | $49 (Growth) | Included |
| Full seats | $156 (4 added to the owner's) | 5 included |
| Limited seats | $75 (5) | 5 included |
| Localisation, 2 locales | $58 (Localize Advanced) | Included |
| Monthly total | $363 | $2,500 |
| Yearly total | $4,356 | $30,000 |
Source: Webflow pricing page, read 13 November 2026; Octo calculation
The roughly $25,600 a year difference does not buy more content room. It buys publishing workflows, branch staging, page branching, single-page publishing, the site activity log and its API, a CMS API five times faster, 100 Collections, custom SSL certificates and security headers, and priority support with a 12-hour response target on major incidents. If none of those is on your list of problems, Team is the wrong plan.
Enterprise. Webflow lists Enterprise as "Custom". The closest public number is Vendr's, a software procurement marketplace: its Webflow page shows a median contract value of $37,800 a year across 135 purchases, with a range of $10,000 to $81,540 and buyers saving 14% on average through negotiation. Treat that as a proxy. Vendr's dataset covers Webflow purchases of every kind through its platform, not Enterprise contracts alone, and large multi-site Enterprise agreements sit well above it. What the number does tell you is that Enterprise conversations start in the same range as Team's $30,000, not at ten times it.
Control: where Enterprise is a different product
Most teams do not move to Enterprise for capacity. They move because security, legal or a second marketing team asks for something no self-serve plan offers.
Identity. Single sign-on, just-in-time provisioning and SCIM are Enterprise only. If your IT policy says every SaaS tool must sit behind the company identity provider, that line alone decides the plan.
Permissions. Premium with a Growth or Agency Workspace gives site-level roles and a per-person publishing toggle. Team adds publishing workflows and page branching. Enterprise adds custom roles, access limited down to individual pages and CMS Collections, and design approvals that require named reviewers before anything goes live. A regional team that should only edit its own locale, or a legal reviewer who must sign off a pricing page, needs Enterprise.
Audit. Team has a site activity log with an API. Enterprise adds an audit logs API for account activity, which is what a compliance team usually asks for.
Paperwork. Enterprise comes with a master service agreement, help with security questionnaires and, according to Webflow's Enterprise page, access to its Whistic security profile. Team and Premium run on the standard Terms of Service. For a procurement team, the MSA is often the deciding document.
Reliability and support
| Measure | Team | Enterprise |
|---|---|---|
| Designer and platform uptime | 99.90% | 99.90% |
| Hosting uptime for published sites | 99.00% | 99.99% |
| Response time, major incident | 12 hours | 1 hour |
| Response time, minor incident | 24 hours | 4 hours |
| Customer success manager, solutions architect, phone support | No | With Premium SLA |
Source: Webflow pricing page, Platform plans comparison, read 13 November 2026
Premium sites get a "standard agreement" on uptime, as Business did, and help centre and support portal access. The difference between 99.00% and 99.99% hosting uptime is the difference between about 87 hours and about 53 minutes of permitted downtime a year. For a site that books demos, that line matters more than any CMS limit.
When each one wins
- Premium wins for one marketing site, under 20,000 CMS items and 40 Collections, a handful of editors and no single sign-on requirement. That describes most B2B sites. Across the 20+ Webflow sites we have built in the last twelve months, our largest CMS holds just over 1,200 items, well inside the limit.
- Team wins when several people publish every week and mistakes have started to reach production: you want staged changes reviewed, pages branched and a log of who changed what, and a migration or CRM sync is hitting the 120 requests-a-minute API limit.
- Enterprise wins when IT requires single sign-on, legal requires an MSA, the site needs more than 20,000 items or 100 Collections, regional teams need page-level permissions, or downtime costs enough to justify a 99.99% hosting commitment.
Moving between plans: what it costs
Premium to Team or Enterprise is a contract change, not a rebuild. The site, its Collections and its URLs stay as they are. The cost is the price difference plus procurement time, and the work is configuration: setting up roles, workflows, single sign-on and staging. We would budget a few days of setup and a review of who can publish, rather than a project.
Restructuring the CMS is where the real cost sits. A site that was split across Collections to stay under 10,000 items on Business can be consolidated once larger Collections are available. Webflow's January 2026 announcement describes Wiley doing exactly that, putting complex product data into a single Collection. That is a content-modelling job with redirects and template changes, so plan it as a small migration with a redirect map, not a plan switch.
Enterprise back to Premium is the move to check before signing. You would lose single sign-on, custom roles, the audit API and the uptime SLA, and any site above 20,000 items or 40 Collections would have to be cut down to fit. Read the Enterprise term and renewal clauses with that exit in mind.
What this means for your plan decision: four questions
- Does IT or legal require single sign-on, SCIM or an MSA? If yes, Enterprise. No other plan offers them.
- Will the site pass 20,000 CMS items or 100 Collections in the next two years? If yes, Enterprise. Team does not raise the item cap.
- Is the problem process rather than capacity? If several publishers need review steps, branching and an activity log, Team. If one or two people publish, Premium with a Growth Workspace covers it.
- What does an hour of downtime cost? If the answer is a number your finance team would notice, the 99.99% Enterprise SLA is worth pricing.
No to all four means Premium, which is where most former Business sites should land. Our marketing websites page explains how we build and hand over Webflow sites for teams on any of these plans.


