←  All terms
C
Webflow

CMS Collection

A CMS collection is a structured set of similar content whose fields provide the template for dynamic pages.

A CMS collection is a structured set of similar content whose fields provide the template for dynamic pages. In Webflow, the solution should align CMS structure, components, permissions, and ongoing editorial maintenance. The concept is closely related to Webflow CMS and Collection Page.

Read more

Webflow CMS

Collection Page

Content Modeling

Reference Field

FAQ

CMS Collection

Where do Webflow CMS collections reach their limits?
Collections are subject to plan-dependent limits, for example on items and fields, which should be checked before modeling. Highly relational data or delivery across many channels strains the model sooner. In that case it must be assessed whether a headless CMS fits better or whether some data should live elsewhere.
What mistakes are common when planning CMS collections?
Typical errors are overly generic collections that mix content types, and fields that describe layout rather than content, such as a color choice per paragraph. Missing naming conventions and unclear required fields also complicate maintenance. A model agreed with the editorial team before the build avoids most of these problems.
What distinguishes a CMS collection from a static page?
A static page keeps its content fixed inside the layout, while a collection separates content from template. Items supply field values that a shared template fills in. This pays off for recurring structures such as articles or job postings. For one-off pages like the imprint or homepage, a collection usually adds needless effort.
How are CMS collections connected to each other?
Through reference fields: an article points to an author or category in another collection, and multi-reference fields handle several links. This way data is maintained once and displayed in many places. Dependencies should be planned up front, because later restructuring affects existing items.
How many CMS collections does a typical website need?
The number follows from the content types, not from a rule of thumb. Blog posts, authors, categories, or case studies are typical candidates, each with its own fields and maintenance. A collection should hold only similar content. Too many collections complicate upkeep, while too few force unrelated content into one schema.