Webflow's CMS limit and how to design around it
The 10,000-item collection cap stops more Webflow projects than any other constraint. A short playbook for designing around it.
Webflow's CMS is excellent right up until you hit the per-collection item cap. After that the project either gets re-architected or gets moved.
What hits the limit first
Multi-language sites with one collection per language times every content type. Blog archives that grew faster than expected. Product catalogues from teams that thought "one collection, one product type" was a clean structure.
How to design around it
Split early. If the brief includes "thousands of items," design two collections from day one - recent vs archive, by year, by category. The split has a cost (cross-collection links, sitemap aggregation) but a small one compared to a migration.
Use external storage for non-display content. If 80% of your fields are metadata used by APIs, consider keeping that in a real database and only mirroring display copy in Webflow.
Be honest about scale. If the long-term answer is "tens of thousands of items," Webflow may not be the right tool. We've seen migrations from Webflow to a coupled CMS go fine. We've seen the inverse fail every time.