CMS Collection (Webflow): plainly explained.

In Webflow, a CMS Collection is a data structure that groups content of the same type: articles, team members, projects.

Website · Updated Aug 2, 2026

DEFINITION

In Webflow, a CMS Collection is a data structure that groups content of the same type: articles, team members, projects. Each Collection has defined fields, like a title or an image. Each entry is a Collection item. Think of it as a spreadsheet where every row becomes a page or a dynamic block.

CATEGORY

Website

RELATED

Content Management System, Webflow

Summarize this page with AI

01

What a CMS Collection actually is

A CMS Collection is the core building block of Webflow's content management system. It is a structured container that groups every item of one content type and gives each item the same set of fields. An Articles Collection declares that every article carries a title, a slug, an author, a publication date, a cover image and a rich text body. Fill those fields in and you have created a Collection item. The Collection itself is the model or blueprint, and the items are the concrete entries that follow it.

The cleanest mental model is a database table. The Collection is the table, each field is a column, and each item is a row. Webflow hides the database server behind a visual interface, but the logic is identical: define the shape of the data once, then pour as many rows into it as you need. Almost everything dynamic on a Webflow site (a blog, a team page, a product catalog, a job board, a case study library) sits on top of one or more Collections.

02

How a Collection works under the hood

When you create a Collection, Webflow stores your items as records and generates two things for you. First, it can build a dynamic list, called a Collection List, that pulls items into any page and repeats a design block for each one. Second, if you attach a Collection Page (also called a Collection Template Page), it produces one real, indexable URL per item, all built from a single layout. Add a new item in the Editor and a new page appears automatically, styled exactly like the others.

This is the mechanism that makes a Webflow site scale. You design the article layout once, bind each element to a field (this heading shows the Title field, this image shows the Cover field), and every future article inherits that design without any manual page building. The binding is the key idea: elements on the canvas are connected to fields, so the content and the presentation stay separate but render together at publish time.

03

Field types and references

A Collection is only as useful as the fields you give it. Webflow offers a fixed set of field types, and choosing the right one for each piece of data matters more than beginners expect.

  • Plain text for short strings like a title or a subtitle.
  • Rich text for long body content with headings, lists and images.
  • Image and Multi-image for a single visual or a gallery.
  • Link, Email, Phone for actionable values.
  • Number, Date, Switch, Color and Option for structured or filterable data.

Reference and Multi-reference fields

The most powerful fields connect Collections to each other. A Reference field links an item to exactly one item in another Collection, for example an article to a single author. A Multi-reference field links an item to several items, for example a project to several services or an article to several categories. These relationships are what let you build category pages, filtered lists and related content blocks without duplicating data. Model them well and the site behaves like a small relational database.

04

When to use a Collection, and when not to

Reach for a Collection whenever you have repeating content that shares a structure and will grow or change over time. Blogs, portfolios, team directories, event listings, product catalogs and glossaries are all textbook cases. The test is simple: if you can imagine a spreadsheet of these items with the same columns, it belongs in a Collection.

A Collection is the wrong tool for one-off pages. A homepage, an about page or a pricing page is unique, so it should be a static page, not a CMS template. Forcing singular content into a Collection adds complexity for no benefit. Webflow plans also cap the number of Collections and CMS items, so it is worth reserving them for content that genuinely repeats rather than modeling everything as data.

05

Common mistakes and pitfalls

The recurring mistake is under-modeling the Collection before designing. Teams create a title and a body, start styling, then discover they also need a category, an author and an excerpt, which forces rework. A second pitfall is stuffing free-form layout into a single rich text field instead of using dedicated fields, which makes content brittle and hard to reuse elsewhere. A third is ignoring the slug and SEO fields at creation time, leaving weak URLs and missing meta descriptions across hundreds of auto-generated pages. Finally, people forget that Multi-reference fields cannot drive every kind of dynamic filtering, so the content model has to match the way pages will actually query it.

06

CMS Collections at BeBranded

At BeBranded, modeling Collections is a design step in its own right, done before any visual work begins. We map every content type, decide which fields are required, and draw how Collections reference one another, because that structure quietly determines how easy the site is to maintain two years later. An Articles Collection connects to a single Collection Page that serves as the template, a Multi-reference to a Categories Collection powers filter pages, and clean slug and SEO fields are set from the start rather than patched afterwards. We also size the model against the client's Webflow plan and against the way content is queried, so lists stay fast and predictable. A well-modeled Collection gives the client full control of their content from the Editor with no risk of breaking the layout, which is exactly the balance a scalable site needs.

FAQ

Questions about CMS Collection (Webflow).

Another question?

Write to us
What is the difference between a Collection and a Collection item?
The Collection is the model, for example Articles, and it defines the fields every entry must have. An item is one concrete entry, for example a single published article. A Collection can hold as many items as your Webflow plan allows, and they all share the same structure and layout.
Does a CMS Collection generate pages automatically?
Yes, if you attach a Collection Page (Collection Template Page) to it. Each item then gets its own page at a unique URL, built from the same layout. If you only need to list items inside another page, you use a Collection List instead and no individual pages are created.
How many Collections and CMS items can I create in Webflow?
The limits depend on the site's Webflow plan, and each plan sets a ceiling on both the number of Collections and the number of CMS items. This is why we size the content model against the plan from the start. Going over the limit means upgrading the plan or restructuring the content.
What is the difference between a Reference and a Multi-reference field?
A Reference field links an item to exactly one item in another Collection, such as an article to a single author. A Multi-reference field links an item to several items, such as a project to several services. Multi-reference fields are what make category pages and filtered lists possible without duplicating content.
Can I import content into a Collection instead of typing it by hand?
Yes. Webflow supports CSV import to create many items at once, and its API lets you push items programmatically from an external source like Airtable or a spreadsheet. For large catalogs we usually automate this rather than entering items manually, which saves time and reduces errors.
Should every page of my site be a CMS Collection?
No. Collections are for repeating content that shares a structure, like blog posts or projects. Unique pages such as the homepage, an about page or a pricing page should stay static, because forcing them into a Collection adds complexity with no benefit and consumes CMS item limits you may need elsewhere.

Related

Related terms, and where to go next.

BeBranded
Webflow

Webflow CMS: mastering collections in 2026

Webflow CMS: collections, fields, templates, conditional visibility, next-gen CMS 2026, and best practices for a CMS your team will actually use.

Read the article
The best CMS for website creation in 2026: a complete guide
No-Code

The best CMS for website creation in 2026: a complete guide

Compare the best CMS platforms in 2026 (Webflow, WordPress, headless and more) by features, pricing and use case to pick the right one.

Read the article
Webflow pricing 2026: plans, costs & what you'll really pay
Webflow

Webflow pricing 2026: every plan, what it costs and the real budget for a site

Every Webflow plan and add-on, checked on webflow.com/pricing on 14 November 2026, with yearly and monthly prices, plus what a Webflow site really costs once design, build and upkeep are counted.

Read the article

Let’s talk

Tell us what you want to build.

Thirty minutes with the people who will work on your project. You leave with a clear view of the scope, the timeline and the next steps.

What happens next

  1. 1A 30-minute callWe listen to your goals, your constraints and your context.
  2. 2A clear scopeWe map what is worth doing first, and what it takes.
  3. 3A costed proposalYou decide, with no commitment and no sales pitch.