Count your CMS items, your Collections, and your static pages, then compare them against what your plan includes. Most sites hit a Collection or item ceiling long before they hit a bandwidth ceiling. And in 2026 the numbers changed, because Webflow restructured its Site plans.
This question comes up constantly in handover calls. A marketing team wants to know whether the plan they are inheriting will hold for two more years of content, and nobody can find a straight answer because the plan lineup was rewritten this year.
So here is a plain read of what Webflow now includes, what changed, when it changes for your site, and which limits actually bite in practice. Every number below comes from Webflow's own announcement and help documentation.
Webflow merged two plans into one. Its 2026 pricing announcement introduced a new Premium Site plan by combining the old CMS and Business plans, raised the included CMS limits, and removed the CMS item add-ons that used to be necessary. It also added a new Team plan and AI credits across every Workspace.
The stated reasoning was simplification. Instead of choosing between CMS and Business and then bolting on add-ons, most content-driven sites now land on one plan. In our experience that was a real source of confusion for clients, so consolidating it is a genuine improvement.
Prices moved in both directions. Webflow says some customers see an increase, some a decrease, and some no change, and it published a pricing change calculator so owners can check their own case. That is the right way to handle a repricing, and we would rather clients check the calculator than take our word for it.
Premium is now the default for content-driven business sites. Webflow states that all customers on the Premium plan get 20,000 CMS items and 40 CMS Collections included. It is priced at $25 per month on a yearly plan or $39 per month billed monthly.
Those CMS numbers are generous for almost any business site. A blog publishing weekly for ten years produces roughly five hundred posts. Twenty thousand items is a different scale entirely, which is the point of removing the add-ons.
The 40 Collections figure is the one worth thinking about, because Collections are consumed by structure rather than volume. A site with posts, authors, categories, case studies, industries, team members, testimonials, job listings, locations, and integrations is already at ten. Complex content models add up faster than people expect, and this is where planning matters. Our notes on Webflow CMS best practices cover how to model content without spending Collections on things that should have been fields.
Webflow also lists what existing customers gain. Former CMS plan customers get double their static page count, higher Webflow Cloud limits, and access to features including form file upload, well-known files, and faster search indexing.
Yes, and Webflow names them directly, which we appreciate. For customers moving from the old Business plan, most limits stay the same or improve, but included bandwidth drops from 100GB to 50GB and Webflow Cloud limits decrease. Bandwidth add-ons remain available for sites that need more.
Being straight about this matters more than spinning it. If you run a media-heavy site that was comfortably inside 100GB, halving the included allowance is a real change you should model before renewal rather than discover on an invoice.
The Basic plan also moved. Webflow says the yearly price rises to $15 per month and the monthly price to $25 per month, while the static page limit doubles from 150 to 300. So Basic costs more and holds more, which suits brochure sites with many static pages and no CMS needs.
For anyone using Webflow Cloud for app-style work, read the limit changes carefully rather than assuming parity. We wrote up what that product does and where it fits in our overview of Webflow Cloud.
It depends on where your site lives, and the dates are specific. Webflow says that for existing sites in Freelancer or Agency Workspaces, or sites on legacy pricing, changes take effect on the next renewal or billable change on or after November 16, 2026. For all other existing sites, that date is June 29, 2026.
New Site plan purchases were on the new pricing immediately from the announcement. So a site you buy a plan for today is already on the new lineup, while a site you have been running for three years may not change until its renewal date passes one of those thresholds.
There is a lever worth knowing about. Webflow says site owners can switch to yearly billing before the change takes effect to lock in their current Site plan for another year. If you are on monthly billing and the calculator shows a price increase, that is a straightforward way to buy time.
In our work it is almost always Collections or static pages, not CMS items or bandwidth. Content teams model too many Collections early, or a marketing site accumulates dozens of campaign landing pages. Item counts and bandwidth rarely become the binding constraint on a normal business site.
The Collection ceiling hurts because it is structural. Running out of items means pruning content, which is annoying. Running out of Collections means changing your content model, which can mean rebuilding templates and re-importing data.
Our practical rule is to model Collections for things that need their own page or their own reusable list, and use fields or option sets for everything else. A "service type" with five values is an option field, not a Collection. That single discipline keeps most sites well clear of the ceiling for years.
The free Starter plan is a separate story. Webflow's documentation puts it at 50 CMS items and 2 static pages, which is fine for a prototype and not viable for a real site. It also cannot do redirects, which matters if you are migrating.
For companies that have outgrown self-serve but are not ready for Enterprise. Webflow describes it as an all-in-one annual plan including a site with 100 CMS Collections, 10 seats, and Localization, plus workflow features that were previously unavailable on self-serve plans.
The feature list is the interesting part. Webflow names its new AEO agents, publishing workflows, page branching, single-page publishing, and a site activity log, along with security features including custom SSL certificates and security headers. Page branching and single-page publishing in particular solve a real problem for teams where several people edit at once.
There is also a detail that matters specifically for studios like ours. Webflow says the Team plan includes content management API rate limits five times higher than self-serve plans, which makes large migrations move significantly faster. If you are importing thousands of items, that is a meaningful difference in a project timeline. We flagged the same constraint when writing about migrating from Squarespace to Webflow, where content volume drives the schedule.
Webflow moved its AI features to a credit-based system and included a pool of credits in every Workspace plan. Those credits reset monthly on self-serve plans and annually on Team and Enterprise plans, and your consumption is visible in a new AI usage dashboard inside the Workspace.
The timing is worth noting. Webflow said credit limits would not be enforced until June 29, 2026, giving customers a window to see their own usage patterns first, with add-on credits available from that date. Publishing the meter before enforcing it is a reasonable way to introduce usage pricing.
Our view on AI credits is the same as our view on any metered resource. Watch the dashboard for a month before you assume anything about your consumption, because teams are consistently wrong about how much they use a new feature in either direction.
Model two years of content growth, not today's content. Count the Collections your content model genuinely needs, estimate items at your real publishing rate, check bandwidth against your media weight, and then pick the plan that clears all four with headroom.
We do this during scoping rather than at launch, because the content model decision is upstream of the plan decision. Choosing a plan first and then squeezing the content model to fit it is how sites end up with awkward structures that cost more to maintain than the plan difference ever saved.
Then write the answer down and hand it over. Part of a clean handoff is telling the client which plan they are on, which limits apply, and what to watch. We have delivered over 150 projects, and the ones that stay healthy are the ones where the client understands their own setup rather than calling someone every time a warning appears.
Three things, in order. Find your renewal date and work out which of the two effective dates applies to your site. Run your details through Webflow's pricing change calculator to see whether your price moves up or down. Then, if it moves up and you are billed monthly, decide whether to switch to yearly billing before the change lands.
After that, audit your content model against the new limits while you are already thinking about it. Count Collections and static pages, and check whether your media library is pushing bandwidth toward the new lower Premium allowance if you are coming from the old Business plan.
If you would rather have someone else read the fine print and tell you what it means for your specific setup, we are happy to do that. Send us your site and your current plan and we will map it against the new lineup. Let's talk, over at phoenix.studio.
Tell us where you want to go. We'll tell you how we'd get you there.