Webflow's CMS Collections have hard item limits by plan. Here's what breaks when you approach them, and what to do next.
Key takeaways
- Webflow's CMS plan caps a site at 2,000 items total across every Collection; the Business plan raises that to 10,000.
- The item ceiling applies to the whole site combined, not per Collection – database-shaped content (catalogs, directories, job boards) hits it fastest.
- Migrating CMS Collections is a bigger job than a static export: field types and reference fields have to map onto the new CMS's structure.
Every Webflow CMS Collection has a hard ceiling, and it is set by your plan, not by how much content you actually need. Nobody reads that line closely until they are three blog categories and a product catalog away from hitting it.
The actual numbers
Webflow's CMS plan caps a site at 2,000 CMS items total, across every Collection combined – not per Collection. The Business plan raises that to 10,000 items. Once you are at the ceiling, Webflow will not let you publish a new item until you delete one, upgrade, or split content elsewhere.
Who actually hits it
It is rarely blogs. A handful of years of posts is a few hundred items at most. The sites that hit the wall are the ones using Collections as a database: a product catalog, a job board, a directory of locations or team members, a glossary – anything that grows on its own, page after page, without an editor manually pruning it.
What "hitting the limit" looks like day to day
- New items silently fail to publish. The CMS editor lets you draft them; going live is where it stops you.
- Upgrading is the default fix Webflow offers – the Business plan, at a meaningfully higher monthly cost, to buy five times the ceiling.
- Deleting old items just delays the problem if the Collection is still growing, which most database-shaped content is by definition.
The other way out
A CMS with no per-item ceiling tied to a pricing tier is the direct fix, and it is also the point where migrating Collections – not just static pages – starts to make sense. That is a materially bigger job than a static export: field types, reference fields and multi-reference relationships all have to map onto the new CMS's structure. Our Astro + CMS – Collections package ($1,390) is built specifically for that: the Basic package covers a site with no CMS or a token amount of it; Collections is for the ones actually running into a wall.
See how the Collections package handles this, or tell us how many items you're managing and we'll tell you what it actually takes.