Yes. Webflow has a built-in CMS made of collections, fields and items. A collection works like a database table, for example blog posts or team members, and your design templates pull content from it. There's also a CMS API for creating, updating and publishing content from code, so you're not limited to typing everything in by hand.
Three building blocks: collections, fields, items
If you've only used page builders before, the Webflow CMS can feel abstract. It comes down to three parts.
- Collections are containers for one type of content, much like a database table. You might have one for blog posts, one for team members and one for testimonials.
- Fields define what each piece of content holds, such as text, rich text, images, dates, numbers and references to other collections.
- Items are the individual entries, so each blog post or each team member is one item.
The payoff is in the design side. Webflow's CMS page describes reusable content templates: you design the layout once, and any new content follows it. You can also build page layouts that pull in CMS content while you design, so you're working with real text and images rather than placeholder copy.
The field types available
| Field type | Typical use |
|---|---|
| Plain Text, Rich Text | Titles, summaries and full article bodies |
| Image, Multi-Image | Featured images and galleries |
| Link, Email, Phone | Contact details and outbound links |
| Number, Date/Time | Sort orders, event dates and publish dates |
| Switch, Option, Color | Toggles, categories and brand colours |
| Reference, Multi-Reference | Linking one collection to another, such as an author to their posts |
Reference fields are where the CMS earns its keep. Link a post to an author item once and the author's name, photo and bio can appear on every post without retyping.
Drafts, live content and archiving
The CMS keeps staged and live content separate. Staged content is a draft you can preview but visitors can't see, and live content is published. Each item carries isDraft and lastPublished properties that set its status, and you can archive items with the isArchived flag instead of deleting them.
Working with the CMS from code
The CMS API lets you create, manage and publish content programmatically. It supports bulk updates and multi-locale content, which is useful if you're moving a few hundred posts from another platform or running a site in more than one language.
The Data API has rate limits that depend on your site plan:
| Item | Limit | Applies to |
|---|---|---|
| Data API requests per minute | 60 | Starter and Basic site plans |
| Data API requests per minute | 120 | CMS, eCommerce and Business site plans |
| Data API requests per minute | Custom | Enterprise |
| Site publish through the API | 1 successful publish per minute | Data API |
Go over the limit and you'll get an HTTP 429 response. If you're importing a big batch, pace the script to stay under your plan's number rather than retrying in a tight loop.
Scripted updates that never go live
Webflow Developer Documentation flags the part that trips people up. CMS API limits scale with the site plan, 60 against 120 requests a minute, and staged API changes don't go live until they're published. So a script can update a hundred items perfectly and the live site shows none of it, because nobody ran the publish step. Add publishing to the end of every script, and remember it's limited to one successful publish per minute.
How WordPress and Shopify handle structured content
WordPress has a REST API that lets applications send and receive data from your site as JSON objects. My comparison of Webflow and WordPress goes through the wider trade-offs.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Shopify product pages can hold custom fields through metafields, which covers some of the same ground for shops.
My verdict on the Webflow CMS
Yes, it has a full CMS, and the collections and reference fields make it a good fit for blogs, team pages, case studies and portfolios. Plan your collections and fields before you design, so templates have the right content to pull from. If you'll update content by script, build in the publish step and watch the per-minute limit for your plan. For ideas on putting the site to work, my Webflow marketing plan is a good next read.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Does Webflow have a built-in CMS?
Yes, based on collections, fields and items.
What is a collection?
A database-like container that defines a content type and its fields, such as blog posts.
Can I edit the CMS through code?
Yes. The CMS API can create, update and publish collection items.
Does the CMS support drafts?
Yes. Items can be staged as drafts or live, and they can be archived.
Is there an API limit?
Yes. It depends on the site plan, and you'll get a 429 when it's exceeded.
