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 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. Our full breakdown of Webflow's 2026 pricing covers every layer if you are budgeting.

Who actually hits 20,000 items

If a person writes your content, you will probably never get close. A blog publishing weekly for a decade is around 500 posts. Add case studies, team members, and testimonials and a typical B2B marketing site lives comfortably under 2,000 items. For that profile, the old advice still holds: item limits are not your problem, and anyone telling you to leave Webflow over them has not checked the current numbers.

The picture changes completely when a system writes your content instead of a person.

We currently run a client site sitting at roughly 15,600 items across 24 collections. That is 78% of the Premium ceiling with about 4,400 items of headroom left. The revealing part is the distribution. Five collections account for close to 90% of the total, and every one of them is fed by an automated pipeline rather than typed by hand. Meanwhile the human-authored collections on the same site are tiny: three news posts, nine testimonials, nineteen FAQs.

That is the pattern worth understanding. Item count stops correlating with editorial effort the moment a pipeline is involved. A site can publish three news articles a year and still be at 78% capacity.

The profiles that get there

Sites that reach the ceiling almost always share one of these traits.

An external system syncs into Webflow. Airtable, Google Sheets, a database, or an internal tool pushing rows through a sync service. Every row is an item, and volume is governed by the source system rather than by anyone's publishing schedule.

Programmatic or templated pages. Location pages, route pages, comparison pages, pricing tables generated from data. This is a legitimate and effective SEO strategy, and it consumes items at a rate no editorial calendar can match.

Multi-dimensional relationships. Where entities cross-reference each other, the item count multiplies. Categories times regions times time periods times variants produces thousands of records from a handful of underlying concepts.

Migrated legacy content. Bringing years of tabular data across from another platform arrives as thousands of items on day one.

The Collection ceiling

Premium gives you 40 Collections and every taxonomy consumes one. Blog posts, categories, authors, tags, case studies, industries, services, team members, testimonials, job listings, locations, FAQs. A well-modelled B2B site can approach 40 without anything unusual going on.

Which constraint binds first depends entirely on your content shape. Editorial sites tend to run out of Collections while barely touching the item allowance. Data-driven sites do the reverse: the client site above uses 24 of 40 Collections while sitting at 78% of items. Check both before assuming which one is your problem.

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.

For a synced site this is worse than it sounds, because the sync fails silently from the perspective of whoever is watching the source system. Rows get added in Airtable, nothing appears on the site, and nobody notices for a while.

The limit that usually arrives first

Worth saying plainly: on data-heavy sites, bandwidth tends to bite before CMS items do. The same pipeline that fills your CMS also generates pages, and those pages get crawled and served.

The client site above hit its bandwidth ceiling well before its item ceiling, and Webflow's in-product remedy was a sales call rather than another add-on tier. If you are modelling capacity, model both, and see our pricing breakdown for how the bandwidth ladder actually behaves in practice.

Your options

Flatten taxonomies. Highest-leverage fix if Collections are the constraint. Any category or tag that does not need its own landing page can be an Option field instead of a reference to a Collection. This often reclaims a third of your Collection budget in an afternoon.

Prune generated data. If a pipeline is filling the CMS, some of what it generates is probably stale. Historical records, expired availability, superseded reports. Adding a retention rule at the source is usually easier than restructuring the site.

Question whether every row needs to be an item. Data that is only ever displayed inside another page, never needing its own URL, does not necessarily need to live in the CMS. Some of it can be rendered from an API call or a static data file at build time.

Move the heavy collections off-platform. If a handful of collections carry most of the volume, they can live in a headless CMS and be rendered separately while Webflow continues running the marketing site. This is the middle path, and it is often the right one: you keep the visual editing your marketing team likes and move only the machine-generated data. Our comparison of Sanity and Webflow covers what that split looks like.

Upgrade. Premium to Team takes you from 40 to 100 Collections, but the item ceiling stays at 20,000. If items are your constraint, $2,500/mo does not solve it. That is worth saying plainly, because it is counterintuitive and it is the point at which a lot of teams discover the upgrade path runs out.

When migration is genuinely the answer

We are a Webflow Partner and most of the time our advice is to stay. The maintenance you avoid is worth more than the licence you pay.

The exception is a site where the item count is driven by a pipeline and still growing. In that situation you are not choosing between platforms on preference, you are watching a hard ceiling approach on a predictable curve. Upgrading does not raise the item cap, so the options narrow to pruning, restructuring, or moving the data layer somewhere without a ceiling.

A headless CMS has no equivalent limit. That is the honest reason a data-heavy site outgrows Webflow, and it has nothing to do with Webflow being bad at what it does.

How to work out where you stand

Count your items and your Collections separately, then work out your growth rate for each. If a pipeline is feeding the CMS, project from the source system's growth rather than your publishing schedule.

If you are under 5,000 items with a stable content operation, stop thinking about this. If you are past 15,000 with an active sync, start planning now, because restructuring under deadline is considerably more expensive than doing it deliberately.