# What Is the Webflow CMS, and Do You Need It?

Canonical: https://figment.so/blog/webflow-cms

The Webflow CMS is a built-in content database: you define a Collection's fields once and Webflow builds a page per item. You need it only if content repeats, and the full CMS needs the Premium Site plan.

**The Webflow CMS is a built-in content database: you create a Collection (like "blog posts"), define its fields (title, image, body), and Webflow generates a page for every item you add, using a template you design once.** You need it if you have repeating content, such as blog posts, team members, products or case studies, that would otherwise mean rebuilding the same layout by hand for every entry. If your site is a handful of one-off static pages, you probably do not. The full CMS comes with the Premium Site plan.

## What is the Webflow CMS?

It is a structured database for your content. Webflow's help center frames it around static and dynamic content: "Static content is managed manually and only changes when you edit it... Dynamic content references one source of truth (i.e., the CMS) and automatically updates if the source changes" ([Webflow, "Intro to the Webflow CMS"](https://help.webflow.com/hc/en-us/articles/33961307099027-Intro-to-the-Webflow-CMS)). The same guide says: "The CMS is a structured database that lets you store and manage content. You start by creating a CMS Collection, which serves as a database for a specific topic or type of content. Within the Collection, you create individual entries (e.g., one blog post) called Collection items."

The workflow, per that guide: create a Collection and set its fields (title, body, image), design the Collection page template once, then add a Collection item for each real entry. Each item gets its own page built from the template.

## What are Collections, fields and items?

They are the three building blocks of the CMS:

- **Collection:** the container for one type of content, such as blog posts, team members, testimonials or recipes.
- **Field:** one piece of structured data inside every item, like a name, photo or price. Webflow's Collection fields article lists the types: "Plain text," "Rich text," "Image," "Multi-image," "Video," "Link," "Email," "Phone," "Number," "Date/Time," "Switch," "Color," "Option," "File," "Reference," and "Multi-reference" ([Webflow, "Collection fields"](https://help.webflow.com/hc/en-us/articles/33961390084499-Use-Collection-fields-to-build-custom-Collections)). Reference and multi-reference fields link items in one Collection to items in another (or the same) Collection.
- **Item:** one entry in a Collection, such as a single blog post or team member.

You can edit fields, group them under names, or delete them at any time. Deleting a field that is connected to something on your site (an element, an SEO setting, custom code) means disconnecting it everywhere first. Webflow warns that this "may affect your design and code embeds" and recommends a site backup before you start.

## What is a Collection page?

A Collection page is the single template that every item in a Collection shares. Webflow's help center: "When you create a Collection, Webflow automatically creates a blank Collection page — a dynamic template that powers individual pages for each Collection item" ([Webflow, "Structure and style Collection pages"](https://help.webflow.com/hc/en-us/articles/33961277976467-Structure-and-style-Collection-pages)). Edit the template once and every item's page updates.

You can nest a Collection's item pages under a parent folder to control the URL path (for example, `website.com/content/blog/example-post`). You can also toggle whether a Collection's item pages publish at all, which is useful if you do not want a Collection indexed yet.

## What is a Collection list?

A Collection list pulls dynamic content onto pages other than an item's own Collection page, such as a blog index on your homepage, a "related posts" block or a grid of team members. Webflow's help center: "Collection lists let you add and design dynamic content from a CMS or Ecommerce Collection to any page on your site" ([Webflow, "Collection list"](https://help.webflow.com/hc/en-us/articles/33961294051347-Collection-list)).

A list can be **Dynamic** (shows every item automatically, with optional filters, sorting and pagination) or **Curated** (you hand-pick items and their order). Elements inside a Collection list stay static until you connect them to a Collection field. Then every item in the list pulls its own value for that field.

## Which Webflow plans include the CMS?

Premium includes the full CMS; Basic has none; Starter has a limited version. As of this check, Webflow's pricing page lists "Limited Webflow CMS" on the free **Starter** plan, positions **Basic** explicitly "For simple sites that don't need a CMS" without listing CMS access, and includes the full "Webflow CMS" on **Premium** alongside code components, site search and scaling bandwidth ([Webflow, Pricing](https://webflow.com/pricing)). The gate has moved between plans before, so check it against your own site.

Webflow's own pages have given different CMS item counts for the same plan. Check the current limit on [Webflow's pricing page](https://webflow.com/pricing) for your plan before you commit content to it.

## Can I import and export CMS content in bulk?

Yes, in both directions, through CSV. Webflow's help center: "When you create Collections in the Webflow CMS, you can add Collection items manually or import them in bulk with a comma separated values (CSV) file... You can also export the content of any CMS Collection as a CSV file. This is useful for backing up your Collection items, importing them into another Webflow site, or moving them to another platform" ([Webflow, "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)). Before you try it:

- CSV files are capped at 4 MB per upload.
- "The number of Collection items you can import depends on your site plan type." The same plan-based cap applies to imports as to items you create by hand.
- An import can create new items or, matched by an Item ID column, update existing ones. That is useful for bulk-editing published content.
- Exported image and file fields come out as URLs pointing back to Webflow's own hosting, not as attached files: "Image and file field URLs point back to the site you exported the Collection from. If you delete that site, those assets and links break." Download the actual files separately if you are migrating away.

## Is there a CMS API for developers?

Yes. Webflow's Data API exposes Collections, fields and items as separate endpoint groups. Per Webflow's developer documentation, the Collections endpoints can "retrieve all collections for a site," "retrieve the schema and details for a specific collection," "create a new collection," and "remove a collection and all of its items." The Fields endpoints can create, modify or remove a field. The Items endpoints can list, retrieve, create, modify, delete, publish or unpublish items, including creating items "across multiple locales" ([Webflow Developer Documentation, "CMS"](https://developers.webflow.com/data/reference/cms)). Webflow's own MCP server and third-party integrations use the same API layer. Our [guide to AI editing a Webflow site](/blog/use-ai-with-your-webflow-site) covers what that looks like in practice.

## What does the CMS not include?

It is content storage and templating, not a way to take your site elsewhere. A code export contains Collection page templates, not the live database behind them. CMS content has to be exported separately, per Collection, as CSV, and forms and site search stop working on an exported site. Our [Webflow code export guide](/blog/webflow-code-export) covers what comes out and what you have to rebuild. If you are weighing the CMS against a plugin-driven alternative, [Webflow vs WordPress](/blog/webflow-vs-wordpress) covers that trade-off.

## How do I decide whether I need the CMS?

Work through this checklist:

- [ ] Does your content repeat in a predictable structure (same fields, different values)? That is a Collection candidate.
- [ ] Which fields does each item need: text, image, a reference to another Collection?
- [ ] Do you need the content in more than one place (its own page, plus a list elsewhere)? That takes both a Collection page and a Collection list.
- [ ] Does your current or planned site plan include the CMS? Check [Webflow's pricing page](https://webflow.com/pricing) directly.
- [ ] If you are importing content, does your CSV header row match your Collection's field names, or will you need to map columns by hand?
- [ ] If you might leave Webflow someday, have you budgeted time to export every Collection as CSV and download linked images separately? Code export alone will not carry your content.

If your content repeats, use the CMS. If every page is one-off, you can skip it.
