Webflow CMS in 2027: How It Works, Real Limits and What It Costs

Webflow CMS is the content database built into Webflow: you define Collections, add items, and one template generates a page for each item. It needs the Premium plan, $25 a month billed yearly, which holds 20,000 items. For most marketing sites that cap never matters. The 100-item list limit does.

We've built on Webflow since 2022, including a First December Films site with 12 CMS collections and 475 items, and we publish this blog through the Webflow CMS API. On 31 October 2026 we checked every limit below against Webflow's own pages, then read the sitemaps of 123 live Webflow sites to see which limits real teams hit.

Key takeaways

• Only 3 of the 123 Webflow sites we scanned list more than 20,000 URLs. The median site lists 533. The plan cap is rarely the problem.
• 85 of those 123 sites (69%) have a section with more than 100 URLs, which is more than one Collection list can show.
• 49 of the 62 blogs we read with over 100 posts run Finsweet's free list-loading code on top of Webflow's pagination.
• Team costs 100 times what Premium costs and starts at the same 20,000 items. You're buying governance, not capacity.
• Publishing has traps the docs mention only in passing: referenced items publish with yours, new URLs reach sitemap.xml only on a full site publish, and scheduling works once per item.
• The old Webflow Editor shut down on 5 October 2026. Any guide that still tells clients to log in on the live site is out of date.

What is Webflow CMS?

Webflow CMS is a structured database inside Webflow that stores repeatable content and connects it to page designs. Webflow's help centre describes four parts: Collections hold one type of content, fields set its structure, items are the entries, and Collection pages and Collection lists put those entries on the site.

So yes, Webflow is a CMS, but it's also the design tool and the host. WordPress gives you a database and leaves design and hosting to plugins and servers. Contentful and Sanity give you a database and an API and leave the front end to developers. Webflow sells all three layers as one subscription, which is why a marketer can add a case study and see it live without a developer.

One confusing detail catches new users. A thread on r/webflow starts with someone reading "0 CMS items" on the Basic plan and worrying they can't upload images. They can. "CMS" means reusable, structured entries, not files. Basic is fine for a site of hand-built pages, up to 300 of them.

How does the Webflow CMS work?

You create a Collection, define its fields, design one template, and every item you add gets its own page at a shared URL path. Change the template and every page follows. Update one field and each place that shows it updates too.

A blog is the standard example:

1. Create a Collection called Posts and add fields such as title, summary, author and body.
2. Design the Collection page template once.
3. Add items. Each one publishes at a URL like /blog/post-name.
4. Add a Collection list to your blog index, and it fills itself.

Webflow offers 16 field types, listed in its Collection fields guide. Reference and Multi-reference are the ones that matter most, because they link Collections together. A post points to one author (Reference) and several topics (Multi-reference). That's what lets an author page list that person's posts without anyone maintaining the list by hand.

The other thing worth learning early is conditional visibility: show or hide any element based on a field's value. It's how one template handles a post with a video and a post without one.

What changed in the Webflow CMS in 2026?

Webflow rebuilt the CMS architecture, merged its plans, replaced the Editor and added components to rich text, all between January and October 2026. Guides written before April describe a noticeably different product.

Sumit Tejani, a project manager at Concatstring, told Webflow the nesting change "has already changed how I think about structuring content" on portfolio projects. That matches what we'd expect. Before April, showing a case study with its related services and those services' own tags needed workarounds. Now it's a three-level nested list.

Not everyone waited patiently. In January a thread on r/webflow asked whether Webflow would ever ship the CMS features it had promised, and Allan Leinwand replied for Webflow that the new platform had reached Enterprise, with everyone else to follow. It reached every site on 9 April.

What are the Webflow CMS limits in 2027?

Webflow CMS limits come in three layers: what your plan stores, what one page can show, and what the API accepts. Most guides list the first layer and stop. These figures come from Webflow's pricing page and help centre, read on 31 October 2026.

Ecommerce plans differ: Standard carries 2,000 CMS items, and Plus and Advanced carry up to 10,000.

These next limits apply on every plan, and no upgrade lifts them, per Webflow's dynamic content limits:

The last row has a catch. Webflow's developer docs count every locale version, so one item created in three locales uses three of the 100.

You also can't nest a Collection list inside a component, and a component holding a Collection list can't go in rich text.

Do locale copies count toward the 20,000?

Probably, though Webflow doesn't say so. We searched 534 Webflow help articles and found no statement either way, and the docs do say each locale keeps its own set of Collection items. Plan as if 5,000 items in four languages uses 20,000, and ask Webflow Support before you commit. You'll find more on the mechanics in our Webflow localization guide.

How big do real Webflow CMS sites get?

Most Webflow sites use a small fraction of the 20,000-item cap. We read the sitemaps of 123 live Webflow sites on 31 October 2026: the median listed 533 URLs, and only 3 listed more than 20,000.

Here's how we built that. We started with 136 sites identified as Webflow in two earlier Webyansh audits, dropped webflow.com, confirmed the Webflow signature on each homepage that day, and kept the 123 with a readable sitemap of at least five URLs. The sample leans B2B, and 39 of the sites come from Webflow's customer stories, so it skews larger than the average Webflow site. Those 39 have a median of 1,259 URLs; the other 84 have 480.

Sitemap URLs aren't CMS items, and that cuts both ways. They include static pages and locale copies, which overstates the count. They miss Collections with no public page, such as testimonials, which understates it. In our sample a median of 91% of URLs sat in folders with five or more pages, so template pages make up most of a typical sitemap.

The three biggest sites show how scale happens. Snappr lists 49,399 URLs, and 39,725 of them sit under locale folders. Nursa lists 46,301, with 20,597 in a single facilities folder. BioRender lists 28,503, with 13,180 in an icon folder. Those are programmatic directories and translation at scale, not blogs. If your plan looks like that, read the headless section before you build.

Which Webflow CMS limit do most sites actually hit?

The 100-item list cap is the limit most sites run into, and it's a display limit rather than a storage limit. In our scan, 85 of 123 sites (69%) had a section with more than 100 URLs, against 3 of 123 (2%) above 20,000.

Webflow's reason is page speed. A list renders into the page's HTML, so 500 cards mean 500 cards of markup on every visit. It offers two fixes: pagination, or the Skip trick, where you duplicate a list and start the copy at item 101.

Neither fix is enough for a searchable library, because a live on-page search only sees the items already in the page. A forum thread on the 100-item limit raised exactly this problem in 2019, and it's why a third-party layer has become normal. We read the blog index on 89 of these sites, 62 of which had more than 100 posts:

Those rows overlap, and the overlap is the lesson. All 49 Finsweet blogs also keep native pagination underneath. Finsweet's script fetches the next pages and appends them for visitors, while crawlers still get real page 2 links. That's the pattern we'd copy. It's free, and removing it later leaves a working paginated blog.

We hit the same wall on First December Films, where the catalogue outgrew a single list. The fix there was a catalogue search, and that's still our advice for any archive people search instead of browse. Once client-side filtering starts to feel slow, look at Algolia, which has a Search and Sync app documented in Webflow's help centre.

How much does Webflow CMS cost?

Webflow CMS starts at $25 a month billed yearly on Premium, or $39 billed monthly, per site. That's $300 or $468 a year, plus tax. The free Starter plan gives you 50 items on a webflow.io address for building and testing.

Team is the jump to look at carefully. At $30,000 a year it costs 100 times Premium's yearly price and includes the same 20,000 items. It earns its price through workflows, governance and support, so don't buy it for capacity. Extra items are available on Team for a separate fee that Webflow doesn't publish.

Three other costs sit outside the plan:

• Seats. Marketers need a limited seat at $15 a month yearly or $19 monthly, per the prices in our Webflow pricing guide. Agencies get free client seats instead: 3 per site on the Agency plan, 1 on Freelancer.
• Bandwidth. Premium includes 50 GB. Extra starts at $20 a month for 50 GB, billed yearly, up to 2.5 TB. Video-heavy pages use this up faster than founders expect.
• Localize. The Essential plan starts at $9 a month and adds cost with each locale, on top of whatever the item count does.

Former Business plans dropped from 100 GB to 50 GB in the merger. If your site passed 50 GB in the past two billing months, Webflow adds bandwidth add-ons at renewal, so read that notice closely.

Who can edit the Webflow CMS now that the Editor is gone?

Anyone with a Webflow account and a seat on the site. The legacy Editor closed for good on 5 October 2026, and the old ?edit shortcut stopped working. The replacement shortcut is ?update, which opens the page in Webflow for a signed-in editor.

Of the 7 articles we read from the top results for this query, 3 still describe the Editor as a current feature. If your client handover doc does too, update it.

The trade is fair, in our view. Content editors gain on-canvas editing, asset management and alt text control, none of which the Editor offered. They lose white-labelling, since Editor branding went with it. Agencies that promised clients a branded back end will have to explain that.

Zaire Fletcher, a senior digital producer at Greenhouse, told Webflow that "everyone is an owner on the marketing site", which is the outcome to aim for. It's a customer story, so treat it as the best case. It still only works if the Collections are built for editors, which is what field groups, help text and required fields are for.

How does publishing work in the Webflow CMS?

Every item is a draft until you publish it, and you can publish it now, queue it for the next site publish, or schedule it. Once an item is live, later edits stay in draft until you publish again, so a live page never changes by accident.

We publish this blog through the same system, so these are the behaviours we've learned to plan around. The first three are in Webflow's item guide, and most guides skip them:

1. Publishing an item also publishes what it references. If a post points to an author with unpublished edits, those edits go live too. Check referenced items first.
2. Scheduling works once. Webflow's scheduled publishing applies only to items that have never been published, and it isn't on Starter or Basic. A refresh of a live post can't be scheduled, and the CMS API can't set a schedule either. We built our own small scheduler for refreshes for this reason.
3. Delete isn't immediate. Items you bulk delete stay live until the next full site publish. Use Unpublish when you need something gone now.
4. New URLs wait for a full site publish. Webflow's sitemap updates when you publish your site. In our experience, a new post published on its own goes live at once but stays out of sitemap.xml until a full site publish. On 23 August 2026 two of ours stayed out that way, and neither appeared until we ran one. An existing URL's lastmod did update after a single-item publish on 15 October.
5. Caches lag. After one refresh on 15 October the plain URL served the old page for about nine minutes, though a cache-busted fetch showed the new one sooner. Check the plain URL before you tell anyone it's live.

A full site publish also pushes any unpublished Designer work, so agree who's allowed to run one. On 30 October we checked what was queued before we ran ours, and that's a habit worth copying.

Is Webflow CMS good for SEO and AI search?

Yes, with two jobs left to you: schema and internal linking. Webflow outputs CMS content as HTML, gives every Collection page its own title, meta description and Open Graph fields, and lets you bind them to fields. Set those patterns once and every item inherits them.

Speed is a real strength at the platform level. In HTTP Archive's Technology Report for September 2026, 71.3% of Webflow origins passed Core Web Vitals on mobile, against 60.0% for HubSpot CMS Hub and 48.3% for WordPress. Geography changes the numbers more than the platform does:

If your buyers are in India, a list of 100 image cards on a mid-range phone will cost you more than any CMS choice.

For AI search, the useful property is that CMS text sits in the raw HTML. In our scan of 190 B2B SaaS homepages, 2% of Webflow pages kept over a fifth of their text out of that HTML, against 15% of Next.js pages. AI crawlers that don't run JavaScript still see your Collection pages. We cover the rest in our guide to Webflow for SEO, GEO and AEO.

Three things we'd set up on day one:

• Schema through custom code. Add JSON-LD to the Collection page head and bind it to fields. One trap: Webflow HTML-escapes ampersands and straight apostrophes from CMS fields inside custom code, so they reach your schema as HTML entities. We use the word "and" and curly apostrophes in those fields to avoid it.
• Reference-driven links. Related posts, author pages and topic hubs built from Reference fields keep internal linking current without manual edits.
• Tables through embeds. Rich text has no native table. Our posts use code embeds, and a post in r/webflow warns that the Designer normalises rich text HTML when it opens the item, so test yours before you import a thousand of them.

Can Webflow be a headless CMS?

Yes, for read-heavy use. Webflow's REST Data API creates, updates and publishes items, and its Content Delivery API serves published items from a CDN at api-cdn.webflow.com. There's no GraphQL endpoint, whatever older guides say.

The numbers set the boundary. Each read returns up to 100 items, so reading 20,000 items takes 200 requests, under two minutes at Premium's 120 a minute. Cached reads effectively have no rate limit, but they stay stale for up to 300 seconds, or 120 on Enterprise. That's fine for a blog or a help centre. It won't suit stock levels or anything that changes by the minute. Any app that needs a logged-in user or a query across Collections needs a real database.

The bigger debate in 2026 is whether a CMS still belongs in the stack at all. Lee Robinson moved cursor.com from a CMS to code and Markdown in three days for $260 in tokens, arguing that "the cost of an abstraction has never been higher". Adam Azzam of Prefect did something similar and said the CMS "worked fine on its own" until agents needed to reach the content. Knut Melvær of Sanity disagreed: the fix for an agent that can't reach your CMS is to give it access.

We side with Melvær for marketing teams, and we have a stake, since we build on Webflow. Moving content into a repository works when your whole team commits code. It fails when your content lead doesn't. Webflow's MCP server now lets Claude, ChatGPT or Gemini read and write Collection items within your roles, which removes most of the reason to leave. Our forecast, and it's only ours, is that bulk CMS work moves to agents during 2027 while editors keep the visual layer. For detail on what those tools can and can't do, read our Webflow AI review.

How does Webflow CMS compare with WordPress, HubSpot, Contentful and Sanity?

Of the platforms below, Webflow is the cheapest way to get design, content and hosting in one product at 20,000 entries. The others win on specific jobs. Prices below were read on 31 October 2026, in USD unless marked, and rupee conversions use 95.29 to the dollar (30 October 2026).

Prices vary by region, as HubSpot's rupee rates show, so check your own market before budgeting. Contentful's figures come from an archived copy of its page.

Our read: choose WordPress for its plugin ecosystem or if you must own the server, and HubSpot if the CRM runs your marketing. Choose Contentful or Sanity if several products share one content source and you have developers. Choose Webflow if marketers own the site. We compared the first of those in depth in Webflow vs WordPress, and if you're moving, our WordPress to Webflow migration page covers the process.

How should you structure a Webflow CMS?

Model the content types your site repeats, keep each Collection to one job, and link them with references. Webflow's limits reward many small Collections over one large one, and our client builds reflect that: First December Films runs 12 Collections, Viraalay 17. In our scan the median site showed 9 template folders.

A B2B SaaS site usually needs something close to this:

Four rules save rebuilds:

• Use an Option field for a short fixed list, and a Collection for anything needing its own page. Moving later means remapping every item.
• Plan references early. You get 10 per Collection on Premium, and nesting needs a Multi-reference field.
• Don't force a landing page into one Collection. Rakib Hossain asked Webflow's community in September how to fit 200 fields into a 60-field limit. Dylan Fletcher's answer is the right one: a Sections Collection with an Option field for the section type, linked by Multi-reference and shown through conditional visibility.
• Import in batches. CSV uploads stop at 4 MB, file fields don't import, and images brought in by CSV get no responsive variants. For a big migration, use the API and upload images directly. Our Airtable to Webflow guide shows that route.

When should you not use Webflow CMS?

Skip Webflow CMS if your content is really an application. It's a publishing database, and it's the wrong home for anything that behaves like product data.

Skip it if:

• You'll pass 20,000 items soon and can't justify an Enterprise contract. We've hit plan limits on client sites, and renegotiating mid-project is painful.
• Your catalogue needs faceted search across thousands of entries from day one.
• Pages depend on logged-in users or live data. Webflow Cloud can host that app beside the site, but the CMS won't do the job.
• You'll publish in many languages at volume, and Webflow's answer on how locales count stays unclear for your plan.
• You need to leave cleanly. CMS content doesn't export with site code, and CSV exports point images back at the old site, so deleting it breaks them. You can leave, but it's a rebuild.
• Your team already works in Git and prefers it.

For everything else, which is most B2B SaaS marketing sites, it's the option we'd pick. If you're weighing a rebuild, run your current site through our free AI Design Scorer first, since a weak page design costs more than any CMS limit.