Webflow CMS Limits Explained: Item Caps, Collections, and What Happens When You Hit Them

The limits, as of July 2026

Webflow's CMS allowances changed substantially in the May 2026 pricing update, and most articles about this are out of date. The current published figures:

Starter (free): 50 CMS items.

Basic ($15/mo): no CMS at all. This trips people up. Basic gives you 300 static pages and a custom domain, but if you want a blog you need Premium.

Premium ($25/mo): 20,000 CMS items and 40 Collections.

Team ($2,500/mo): 20,000 CMS items and 100 Collections.

Enterprise: negotiated.

Verify against Webflow's own plan comparison before acting on any of this, since these numbers moved once already this year.

The honest headline: this is rarely the problem it used to be

If you have read older posts about Webflow CMS limits, they were probably written when the CMS plan capped you at 2,000 items and Business at 10,000. Those tiers no longer exist. Premium now includes 20,000 items, and Webflow removed CMS item add-ons entirely because the included allowance made them redundant.

For the overwhelming majority of marketing sites, 20,000 items is not a ceiling you will ever touch. A blog publishing weekly for ten years is roughly 500 posts.

So if someone tells you to migrate off Webflow because of CMS item limits, ask them when they last checked the numbers.

The constraint that actually bites: Collections

The item count is generous. The Collection count is not.

Premium gives you 40 Collections. That sounds like plenty until you model a real site. Blog posts, post categories, authors, tags, case studies, case study categories, industries, services, team members, testimonials, client logos, job listings, departments, locations, FAQs, resource types, integrations, changelog entries. A well-modelled B2B SaaS site can approach 40 Collections without anything unusual going on.

Every taxonomy is a Collection. That is where the budget goes.

What happens when you hit a limit

You cannot create new items or Collections. The site stays up and publishing continues to work, but content operations stop until you upgrade, delete, or restructure.

It surfaces at the worst possible moment, which is usually mid-campaign when someone is trying to ship.

Your options

Flatten taxonomies. The highest-leverage fix. Any category or tag that does not need its own landing page can be an Option field rather than a reference to a Collection. This often reclaims a third of your Collection budget in an afternoon.

Merge overlapping Collections. Separate "Industries" and "Verticals" Collections holding the same concepts is common and wasteful.

Audit for abandoned Collections. Most sites carry Collections built for a campaign that ended two years ago.

Move one heavy Collection off-platform. If a large resource library or product catalogue is the problem, it can live in a headless CMS and be rendered separately while Webflow runs the rest of the site.

Upgrade. Premium to Team takes you from 40 to 100 Collections. At $2,500/mo that is a large cheque to solve a modelling problem, and worth exhausting the options above first.

Related constraints worth knowing

There are limits on reference and multi-reference fields per Collection, on nesting depth, and on static pages per site (300 on Basic and above). Webflow's CMS also cannot express repeating structures inside a single item, which is the constraint that most often pushes genuinely complex content models toward a headless CMS. That is a modelling limitation rather than a quota, and no plan upgrade fixes it.

How to decide

Count your actual Collections, not your items. If you are near 40 on Premium, spend an hour on taxonomy before you spend anything on a plan.

If you are hitting structural limits rather than numeric ones, meaning your content genuinely cannot be modelled in Webflow's CMS, that is a different conversation and one where a headless CMS earns its keep.

Our breakdown of Webflow's 2026 pricing covers where the cost cliffs sit if an upgrade is on the table.