# Webflow CMS Limits in 2026: Every Cap and What It Costs a Blog
Author: Sai Krishna
Author URL: https://superblog.ai/blog/author/sai-krishna/
Published: 2026-09-13
Meta Title: Webflow CMS Limits in 2026 | Superblog
Meta Description: Every Webflow CMS limit as of September 2026: items, Collections, lists per page, scheduling, Localize pricing, and what to do when a blog outgrows them.
Tags: blogging, SEO, cms
Tag URLs: blogging (https://superblog.ai/blog/tag/blogging/), SEO (https://superblog.ai/blog/tag/seo/), cms (https://superblog.ai/blog/tag/cms/)
URL: https://superblog.ai/blog/webflow-cms-limits-blog/

![Webflow CMS Limits 2026](https://prod.superblogcdn.com/site_cuid_ckox4in4f002nl8lhcib41g2u/images/webflow-cms-limits-2026-1789107855788-compressed.png)

Webflow CMS limits are set per Site plan, and they went up in May 2026. As of September 2026, the Premium plan carries 20,000 CMS items and 40 CMS Collections, the free Starter plan carries 50 items and 20 Collections, and Basic has no CMS at all. On top of that sit page-level caps that no plan lifts: 40 Collection lists per page and 100 items per list without pagination.

If you last read about Webflow's item cap being 2,000 or 10,000, that article is out of date. The numbers below come from Webflow's own pricing page and help center, checked on September 11, 2026.

## Webflow CMS limits by plan, September 2026

Prices are per site in USD. Yearly prices are the ones Webflow advertises by default.

LimitStarterBasicPremiumTeamPriceFree$15/mo yearly, $25/mo monthly$25/mo yearly, $39/mo monthly$2,500/mo, annual contract onlyCMS items (whole site)50No CMS20,00020,000, more for a separate feeCMS Collections20No CMS40100Static pages2300300500Bandwidth1 GB/mo10 GB/mo50 GB included, add-ons to 2.5 TBUp to 30 TB/moScheduled publishingNoNoYesYesPer-item and multi-item publishingNoNoYesYesRSS feeds from a CollectionNoNoYesYesCMS API rate60 requests/minNot applicable120 requests/min600 requests/minLocalizationNot availableAdd-onAdd-on2 locales included

Sources: [Webflow pricing](https://webflow.com/pricing) and [Updated pricing and simplified plans for May 2026](https://help.webflow.com/hc/en-us/articles/51059955082387-Updated-pricing-and-simplified-plans-for-May-2026), both checked September 11, 2026. Enterprise is quoted per deal and lists CMS items as custom.

A second set of limits applies to every plan, because they protect page performance rather than revenue. From [Dynamic content limits](https://help.webflow.com/hc/en-us/articles/33961370432275-Dynamic-content-limits), last updated April 9, 2026:

Page-level limitCapCollection lists per site page40Nested Collection lists per site page10Items shown per Collection list without pagination100Items shown per nested Collection list100

Field counts are published only for the Team plan, which lists 100 fields and 20 reference fields. Webflow does not publish a field count for Premium on its pricing page, so treat any third-party number for that as unverified.

## What the May 2026 overhaul changed

Webflow merged the old CMS and Business Site plans into one plan called Premium on May 13, 2026. Per Webflow's help center, an old CMS plan site went from 2,000 to 20,000 CMS items and from 20 to 40 Collections, and an old Business plan site went from 10,000 to 20,000 items. CMS item add-ons were retired because the new allowance covers what they used to unlock.

Two things moved the other way. Business plan bandwidth dropped from 100 GB to 50 GB, so sites that were comfortably inside the old allowance now buy bandwidth add-ons (the first +50 GB is $20 per month billed annually, $30 billed monthly). And Surge Protection still applies: two consecutive months over your bandwidth limit triggers an automatic plan upgrade.

So the honest 2026 summary is that the raw item cap stopped being the thing that breaks blogs. What breaks blogs now is everything around it.

## Which Webflow CMS limits actually bite a blog

**The item budget is shared, not per Collection.** 20,000 items is the total for the site. Posts, categories, tags, authors, case studies, job listings, changelog entries and testimonials all draw from the same pool. A blog on its own will not get near it. A blog on a site that also runs a large template-generated section can.

**100 items per Collection list is the first wall most teams hit.** Your `/blog` index cannot show more than 100 posts in one list unless you turn on pagination, and pagination changes the URL shape and how deep pages get crawled. Category pages, author pages and related-post sections all inherit the same ceiling.

**40 Collection lists per page sounds generous until you build a magazine layout.** A featured hero, a set of category rows, a trending strip, a newsletter block filtered by tag and a related section at the bottom add up faster than expected, and nested lists have their own cap of 10 per page.

**Scheduling is plan-gated and one-shot.** Webflow's own documentation is explicit: "Only Collection items that have never been published can be scheduled to publish at a future time. Scheduled publishing isn't available on Starter or Basic Site plans" ( [Scheduled publishing](https://help.webflow.com/hc/en-us/articles/33961272476563-Scheduled-publishing), updated December 2025). You can queue a first publish. You cannot schedule an updated version of a live post to go out on Tuesday morning, which is exactly what a content refresh program needs.

**Multiple authors are a build, not a field.** Webflow's [Collection fields](https://help.webflow.com/hc/en-us/articles/33961390084499-Collection-fields) list has no author type. To credit two people on a post you create an Authors Collection and add a multi-reference field to Posts, then design the byline, the author page and the author archive yourself. Every writer who needs to edit content in Webflow also needs a seat: as of September 2026 a full seat is $39 per month per seat billed yearly and a limited content seat is $15, on top of the Site plan.

**Localization is priced separately from the CMS.** Localize Essential starts at $9 per month and scales with the number of locales, up to 3 locales with 10,000 translated words per locale per month. Localize Advanced starts at $29 per month, up to 10 locales with 50,000 words per locale per month. The Team plan bundles 2 locales. A four-language blog is therefore a Site plan plus a Localize tier, decided by locale count rather than by how much you publish.

The full per-locale math is in [Webflow localization pricing](/blog/webflow-localization-pricing-blog/).

For the search-side consequences of running the blog inside the same project as the marketing site, we go deeper in [Webflow blog SEO](/webflow-blog-seo).

## Workarounds that keep the blog inside Webflow

Start here. Most of these are cheap, and if one of them clears your blocker you are done.

1. **Paginate or cap the list.** For the 100-item ceiling, enable pagination on the Collection list, or use Webflow's [limit and filter settings](https://help.webflow.com/hc/en-us/articles/33961368695827-Limit-Collection-lists) to show a fixed number and link to a fuller archive. Keep the paginated URLs crawlable and internally linked.
2. **Move the blog to [Superblog](https://superblog.ai) at /blog and leave the site alone.** One routing rule, the marketing site stays on Webflow, detail in the next section.
3. **Split one Collection into several.** Collections are the cheaper resource: 40 on Premium, 100 on Team. Archives by year, or separate Collections for editorial posts and product updates, spread the same content across more containers. The cost is duplicated templates and cross-Collection lists you cannot merge in one native list.
4. **Archive aggressively.** Unpublishing or deleting stale items frees item budget. Add a 301 redirect for every URL you remove, or you convert a CMS problem into a search problem.
5. **Move up a plan.** Starter to Premium takes you from 50 items to 20,000 and unlocks scheduling, per-item publishing, RSS and CMS item indexing control. If you are on Basic and want a blog at all, this is not optional, because Basic has no CMS.
6. **Talk to Webflow about Enterprise.** Item counts are listed as custom there. This is the route for a genuinely large library, and it is priced accordingly.
7. **Keep the master content outside Webflow and sync it in.** Teams use Airtable, Google Sheets or a database with a sync tool pushing into the CMS through Webflow's API. The rate limit is the thing to check before you commit: 120 requests per minute on Premium, 60 on Starter. It buys you bulk editing. It does not buy you more items, and it adds a second system to run.

None of these change the underlying shape: the blog lives inside a design tool, and every publishing capability you want has to be designed, bound and maintained by someone who knows the Designer.

## Take the blog out of the CMS and keep the Webflow site

There is a second answer to a CMS limit, and it is the one that suits a serious content program: stop asking the CMS to do it. Your marketing site stays on Webflow exactly as it is. One routing rule sends `yoursite.com/blog` to Superblog, and readers, links and crawlers see a single domain. Setup is covered step by step in the [Webflow blog guide](/blog/add-blog-to-webflow/) and on the [blog for Webflow](/use-cases/blog-for-webflow) page. A subdomain or a full custom domain works on every plan too, with free SSL.

What that hands you, against the specific limits above:

- **Post volume that stops being a design decision.** Pro covers up to 1,000 posts, Super is unlimited under fair use and Business allows 25,000. For scale: 23 blogs on Superblog hold 1,000 posts or more, and the platform serves over 150,000 posts in total.
- **Nothing to keep running.** There is no Designer to open, no template bindings to rewire, no plugin shelf and no security patching. What gets published is a set of pre-built static files sitting on a CDN, which leaves no database and no runtime for anyone to attack.
- **Real scheduling, including on updates.** Autosave is on from the first plan. Scheduled publishing and collaborative review start at Pro. Pro carries 5 seats, Super 10 and Business 25, split across Admin, Editor and Writer roles, and a post takes co-authors as a field rather than an Authors Collection you have to model and design.
- **SEO output you never bind by hand.** Each deploy rewrites the structured data: Article and WebPage markup in JSON-LD, with Organization, ImageObject and FAQ blocks beside it. Sitemaps, canonical tags and Open Graph data are written per post, IndexNow fires as a post goes live, and the llms.txt index rebuilds with a plain-markdown twin of every post. Multilingual output (hreflang plus one sitemap per language) unlocks on Super, and no per-locale fee is attached to it.
- **Page speed you inherit.** Uploaded images are converted to WebP for you, the global CDN does the delivery, and the Lighthouse performance score clears 90 on every page without a tuning pass.
- **Traffic numbers with no consent banner.** Pirsch is built in from Pro upward and sets no cookies, so there is nothing to ask permission for. Google Analytics can run alongside it on any plan.
- **Dashboard extras on Business.** The featured image and the Open Graph image can be generated by AI from the post itself, costing one credit apiece. Keyword research sits in the same tier: enter a term and read live DataForSEO figures on volume, competition and cost per click, 25 keywords to a search.
- **Your existing posts come across with their URLs.** The Webflow import is API-based: give Superblog an API token plus the site and Collection ID and it pulls posts, keeping the original slug and publish date. Bylines are the one thing to fix afterwards, because imported posts are attributed to the account that ran the import.
- **Pricing you can check in a minute.** Pro runs $49 a month, Super $99. Each one opens with a 7-day trial that asks for no card, and there is a 30-day money-back guarantee. Larger programs sit on Business or Enterprise. Full detail is on [pricing](/pricing).

Apply the same test in reverse before you move: if 20,000 items was your reason for leaving, note that Pro's 1,000-post cap is lower, and Super or Business is the tier that matches. A side-by-side of the two platforms for content work is on the [Webflow blog alternative](/webflow-alternative) page.

## Webflow CMS limits FAQ

### What is the Webflow CMS item limit in 2026?

20,000 CMS items per site on the Premium and Team plans, as of September 2026. The free Starter plan allows 50 items and the Basic plan has no CMS. The cap counts every item across every Collection on the site, not per Collection.

### How many CMS Collections can a Webflow site have?

40 on Premium, 100 on Team and 20 on Starter. Enterprise is custom. A typical blog uses four Collections for posts, categories, tags and authors, so the Collection cap is rarely what stops a blog.

### Can I show more than 100 blog posts on one Webflow page?

Not in a single Collection list without pagination. Webflow caps a Collection list at 100 items displayed, and nested Collection lists at 100 as well. Turn on pagination, or split the archive across several pages or Collections.

### Does Webflow allow scheduled blog posts?

Yes, on Premium and above. Two conditions apply: scheduling is unavailable on Starter and Basic, and only items that have never been published can be scheduled. An edit to a live post cannot be queued for a future date.

### How do I get past the Webflow CMS limits without leaving Webflow?

Paginate long lists first. If the blocker is publishing workflow rather than item count, move the blog to Superblog at `/blog` and leave the Webflow site untouched. Otherwise split content across more Collections, archive old items with redirects in place, upgrade the Site plan, or negotiate custom item counts on Enterprise.

## Where to go from here

If the cap you hit is an item count, upgrade the plan and get on with it. If what you actually hit is the ceiling on how a content team works inside a design tool, the blog is the piece to move, not the site. Start a [7-day trial](https://write.superblog.ai), import your Webflow Collection, and point `/blog` at it when the pages look right.


---
This blog is powered by Superblog. Visit https://superblog.ai to know more.
---

