Webflow's May 2026 plan changes: CMS and Business are gone
Webflow merged the CMS and Business plans into one Premium plan on 13 May 2026, raised the included CMS limits, and deleted the item add-ons. Here is what changed, when it reaches your site, and the two limits that went down rather than up.
On 13 May 2026 Webflow stopped selling the CMS plan and the Business plan. They were merged into a single plan called Premium, at $25 a month billed yearly or $39 billed monthly. Almost every comparison, pricing guide and agency article on the web still describes the two plans as current, and until today three posts on this site did too.
So this is the change, taken from Webflow's own announcement and help centre, with the dates that decide when it reaches a given site. It matters beyond the price, because the included limits moved in both directions and the CMS item add-ons were deleted outright.
What replaced what
| Plan | Before | After |
|---|---|---|
| Name | CMS and Business, sold separately | One plan called Premium |
| Price | CMS $23, Business $39 yearly | $25 yearly, $39 monthly |
| CMS items | 2,000 on CMS, 10,000 on Business | 20,000 included |
| CMS Collections | 20 on CMS, 40 on Business | 40 included |
| CMS item add-ons | 5,000 and 10,000, paid monthly | Removed |
| Static pages, Basic | 150 | 300 |
| Bandwidth, former Business | 100GB | 50GB, add-ons available |
| Ecommerce plans | Unchanged | Unchanged |
When it reaches your site
The rollout is in three waves, and the third one is the reason agencies need to read this. New Site plan purchases moved on 13 May 2026. Existing sites move on their next renewal or billable change on or after 29 June 2026. Sites held in a Freelancer or Agency Workspace, or on pricing from 2022 or earlier, move on or after 16 November 2026, which Webflow says is deliberate so that agencies have time for the conversation with their clients.
There is one lever left before each of those dates. Webflow states that switching from monthly to yearly billing before the change takes effect for your account locks in the current plan for another year. If you manage client sites, that decision has a deadline attached to it and the deadline is not the same for every site you manage.
The part that is a downgrade
Most of this is more for the same money. For a site that was on the CMS plan it is a large increase: ten times the CMS items, double the Collections, double the static pages, and higher Webflow Cloud limits, with form file upload, well-known files and faster search indexing added. For a site that was on Business, two things go the other way.
- Bandwidth falls from 100GB to 50GB. Webflow says that where a site has exceeded 50GB in the past two billing months it will add bandwidth add-ons to cover the usage, which is a price increase arriving as an add-on rather than as a plan change.
- Webflow Cloud limits fall. Web app requests go from 10M to 2M a month and CPU from 120 to 30, alongside reductions across SQLite, the key-value store and object storage. On a former CMS-plan site the same limits rise, from 1M to 2M requests and 15 to 30 CPU.
Both of those land automatically at renewal. Neither is visible on the pricing page, because the pricing page describes the plan you would buy today rather than the plan you are being moved off. That is worth checking on any media-heavy site before the renewal date rather than after it, and it sits alongside the other things that quietly drive a Webflow budget, which we set out in what actually drives the cost of a Webflow build.
The new Team plan, and what moved behind it
Webflow also introduced a Team plan at $2,500 a month on an annual contract. It carries a site with 100 CMS Collections, 10 seats and Localize, and it unlocks capabilities that were not previously available on self-serve at all: AEO agents, publishing workflows, page branching, single-page publishing and a site activity log.
The AEO agents entry on that list is the one to notice. When we wrote about what Webflow's AEO agents actually do, the question was whether the feature was worth using. The answer now carries a number in front of it, because reaching it from self-serve means a $2,500 a month annual commitment rather than a plan upgrade. That changes who the feature is for.
What this does to everything written before May
Our own Webflow limits reference argued that platform limits are commercial decisions that change whenever pricing changes, and that an article carries whatever was true on the day it was written with nothing to signal when that stopped. Four months later that post was itself describing add-ons that no longer exist. Both the CMS comparison and the listings comparison quoted Business plan ceilings in tables dated 4 September, three months after the plan stopped being sold.
All three now carry a dated correction rather than a quiet edit, because a reader who quoted the old figure deserves to see that it moved and when. The practical lesson is the one the original post already gave and we did not apply to ourselves: read the vendor's current page, write the figure into the brief with the date attached, and check it again before the next build starts.
