Webflow CMS guide: Collections, fields and plan limits

The Webflow CMS is the content management system built into Webflow. It keeps content that shares a structure (blog posts, case studies, team members, job openings, glossary terms) in a database, and it generates a page for each record from a template you design once. There is no plugin to install and no server to run: the CMS lives in the same product as the visual designer and the hosting.

This guide is for marketing and web teams who want to set up the Webflow CMS properly on a B2B site. For a broader introduction to the platform, read What is Webflow?; for plans and costs, see our Webflow pricing guide. Here we stay with the CMS itself: the building blocks, the field types, the limits and a setup order that works.

The four building blocks

Webflow's help centre describes the CMS in four parts:

You design the Collection page template once. Every item in the Collection uses it, and when you change the template, every page updates with it. Collection lists work anywhere, static pages included, and can be filtered, sorted and shown conditionally based on field values.

Collection pages are published under a folder, and the Collection URL setting names that folder. With a Collection URL of post, a post lives at yourdomain.com/post/post-name. If you rename the folder after launch, Webflow tells you to add 301 redirects, and one rule covers the whole folder: old path /old-folder/(.*), new path /new-folder/%1.

Field types: building the content model

Every Collection has a required Name field and a required Slug field. On top of those, Webflow offers:

• Text: plain text and rich text. Long-form content goes into rich text, which takes headings, paragraphs and media.
• Media: image, multi-image, video link (YouTube, Vimeo and similar) and file.
• Links and contact: link, email and phone.
• Data: number, date/time, switch (yes/no), colour and option (a predefined list).
• Relationships: reference (one item from another Collection) and multi-reference (several items).

Large schemas can be organised into named field groups, which makes life easier for whoever edits the content. Webflow's developer docs say a Collection schema can have up to 60 fields, while the comparison table for the Team platform plan lists 100 fields and 20 reference fields. The point is that fields are not unlimited, and the ceiling depends on the plan.

References: connecting content the right way

Reference fields turn the CMS from a content store into a real data model. A common pattern: the Blog posts Collection points to Authors with a reference field and to Categories or Tags with a multi-reference field. Change an author's job title once and it updates on every post that shows the author.

The limit matters here. According to Webflow's help centre, Enterprise plans can add up to 20 reference fields per Collection; other plans up to 10, depending on the site plan. On a B2B site a post might want to link to an author, a reviewer, a category, a service, an industry and a related case study. Listing those relationships up front keeps you from hitting the cap halfway through the build.

Plan limits (as of October 2026)

Which CMS features each plan includes is set out in the comparison table on Webflow's pricing page:

The practical reading: any B2B site with a blog, a case study archive or a resource library needs Premium or above. Basic is for sites without a CMS. Premium also unlocks the editorial features: publishing and unpublishing single items, scheduled publishing, RSS feeds and using CMS data inside custom code embeds. For prices and plan choice, see the scenarios in our Webflow pricing guide.

Per-page display limits

Your plan decides how many items you can store. Per-page limits decide how many you can show at once. Webflow's "Dynamic content limits" article sets them out:

• A page can hold up to 40 Collection lists, nested lists included.
• A page can have up to 10 nested Collection lists, up to three levels deep.
• A Collection list shows up to 100 items by default. To show more, use pagination (up to 100 items per page) or duplicate the list and use the Skip setting.
• Collection lists cannot be nested inside components.

Webflow says these limits exist to keep pages fast. If the design calls for a 300-term glossary on a single page, plan for pagination or letter-by-letter pages from the start.

A setup order that works

On our own Webflow projects we set up the CMS in this order:

1. Content inventory. List every repeating content type: posts, case studies, services, industries, authors, FAQs. One-off pages such as About or Contact can stay static.
2. Content model. Write down each Collection's fields, which are required and which Collections they link to. Check the reference cap here.
3. URL decisions. Name each Collection's folder together with your SEO plan. Changing it after launch means redirects.
4. Template design. Design the Collection page template with realistic content lengths, and use conditional visibility for fields that may be empty.
5. SEO fields. Bind the SEO title, meta description and Open Graph fields to CMS fields in the template. Our Webflow SEO settings guide covers the details.
6. Import. Bring existing content in by CSV, then spot-check links and images.
7. Editor training. Give each editor only the role they need.

The point of this order is to avoid the most expensive mistake: changing the content model after hundreds of items are already in.

CSV import and the API

Webflow imports Collection items in bulk from a CSV file. Its own documentation lists what to watch for:

• The file can be up to 4 MB.
• Image fields take a direct image URL; images imported this way do not get responsive variants (srcset).
• In an option field, every distinct value becomes an option, up to 100.
• Reference and multi-reference values are converted to slugs and matched; for items with a custom slug, use the slug itself.
• File fields cannot be filled by CSV; upload files by hand afterwards.
• Webflow offers a pre-import backup, which you can restore from Site settings > Backups.

For large or constantly changing content there is Webflow's Data API, which can create, update and delete Collections and items. List requests return up to 100 items at a time, and CMS changes reach the live site when you publish.

For the parts that need code and that the CMS cannot cover (a price calculator, a customer portal, advanced search or personalized content) there is Webflow Cloud: the app runs on the same domain as the Webflow site, under a set path, and can use Webflow CMS data, so the marketing team keeps working in Webflow. We build these parts as Webflow Cloud apps.

Editors and roles

The real payoff of the CMS is that marketing can publish without waiting for a developer, and Webflow's seat model reflects that. A Full seat is for design and admin work; a Limited seat is for editing content and building pages from components; a free seat is for reviewing and commenting. As of October 2026, billed yearly, a Full seat costs $39 a month and a Limited seat $15.

Keeping roles narrow lowers both cost and risk. The person writing blog posts does not need access to the template's design.

Limits worth knowing

• Leaving the platform: code export gives you HTML and CSS, not CMS items or Collection pages. Content leaves Collection by Collection as CSV.
• File privacy: files uploaded to CMS fields are public to anyone with the link. Do not keep confidential documents in the CMS.
• Schema: the schema markup field in page settings does not support reference, multi-reference or multi-image fields.

None of this makes the Webflow CMS weak. These are simply facts to design around when you build the content model.

Bottom line

When a Webflow CMS project struggles, the cause is usually an unplanned content model, not the platform. Plan Collections, fields, references and URLs in writing before any content goes in, and your team will work comfortably for years. If you want help designing the CMS architecture, see our Webflow development and CMS service, or our Webflow agency page for everything we do on Webflow.

Sources

• Webflow Help Center, Intro to the Webflow CMS: https://help.webflow.com/hc/en-us/articles/33961307099027-Intro-to-the-Webflow-CMS (accessed October 2026)
• Webflow Help Center, Collection fields: https://help.webflow.com/hc/en-us/articles/33961390084499-Collection-fields (accessed October 2026)
• Webflow Help Center, Reference Collection field: https://help.webflow.com/hc/en-us/articles/33961317363091-Reference-Collection-field (accessed October 2026)
• Webflow Help Center, Manage CMS Collections: https://help.webflow.com/hc/en-us/articles/33961244391059-Manage-CMS-Collections (accessed October 2026)
• Webflow Help Center, Dynamic content limits: https://help.webflow.com/hc/en-us/articles/33961370432275-Dynamic-content-limits (accessed October 2026)
• Webflow Help Center, How do I import content into the Webflow CMS?: https://help.webflow.com/hc/en-us/articles/33961290794771-How-do-I-import-content-into-the-Webflow-CMS (accessed October 2026)
• Webflow Developers, Managing CMS Collections and Items: https://developers.webflow.com/data/docs/working-with-the-cms/manage-collections-and-items (accessed October 2026)
• Webflow, Plans & pricing: https://webflow.com/pricing (accessed October 2026)