Webflow CMS collections: the one question
Will anyone who is not a developer ever need to add one of these? If yes, it is a collection. Properties, case studies, team members, job posts, plans, locations, articles, all collections, even when there are only three of them today.
If no, it is a page. Home, about, contact, pricing: they exist once, they change rarely, and wrapping them in a content structure buys nothing. This one question is also the clearest signal that a website builder has been outgrown, because a builder answers it for you by having no answer.
The expensive mistake is “we will only ever have three”. Three becomes eleven, by which point the layout has been copy-pasted eleven times and every change is eleven changes made by hand, of which one will be missed. It is also the choice that moves a quote further than page count does, which is a post of its own.
The opposite mistake is real too. A collection holding one item is a static page with extra steps and a worse editing experience, you have added a layer of abstraction and gained nothing to abstract over.
What a collection costs up front
You have to decide the fields before the content exists. That is uncomfortable, and it is the entire point: a collection forces the conversation about what every item must have, while it is still cheap to answer. The cheapest place to have it is in the design file, while the repeating card is still a drawing.
The fields people wish they had added: a short summary separate from the long body, an explicit ordering number, a featured flag, and an SEO title separate from the display title. That last one matters more than it sounds: the headline that works on the page is rarely the one that works in a search result.
A badly shaped collection is genuinely worse than static pages, because the shape becomes load-bearing for every item added afterwards. Spend the hour on the fields.
Where it pays
The Goat Residential rents student housing, which means the property list changes constantly and is the reason anyone visits. It is a collection, and the client updates it without us, the difference between owning a website and renting access to one.
The second language rides the same structure rather than a duplicated page tree. That is the compounding benefit: every improvement to the item layout lands everywhere at once, in both languages, instead of being applied by hand and drifting.
The test of a good collection is simple. The client adds an item, and nothing about the site looks like something was added.
Questions we get asked
When should I use a Webflow collection instead of a static page?
Whenever anyone who is not a developer will ever need to add another one. Properties, case studies, team members, job posts, plans, locations and articles are all collections, even when there are only three of them today. Home, about and contact are pages.
How many items can a Webflow CMS collection hold?
The plan sets the ceiling, and the practical limit arrives earlier than the published one. Filtering and sorting stay comfortable in the low thousands; past that the constraint stops being the CMS and becomes the architecture, which is a different decision entirely.
Can I change collection fields after the content is in?
You can add fields freely. Changing a field's type or removing one is where it hurts, because the shape is load-bearing for every item already published and for every reference pointing at it. Spend the hour on the fields before the first item exists.