Webflow CMS limits: how many items and pages can your website handle?

In most B2B situations a Webflow site can handle plenty of content, but there are hard limits. Webflow counts with a total number of CMS items per site, a maximum number of CMS Collections and several display limits. For an average company site or blog you will never reach those limits, but with a large knowledge base, an extensive product catalog or multilingual content you can run into them. In this article you will see per plan how much your site can handle, when the Webflow CMS limits really start to pinch and what your options are if you grow past them.

What exactly are Webflow’s CMS limits?

Webflow imposes three types of limits: the total number of CMS items across your entire site, the number of CMS Collections and several limits on how you display content on a page. A Collection is a content type, for example “Blog articles” or “Job openings”. An item is an individual row in such a Collection, so a single article or a single job opening.

Those limits depend on your site plan. It is important to understand that the total number of items counts across your entire site, not per Collection. If your ceiling is 2,000 items and you spread them across blog, cases and team members together, they all count toward it. In addition, independently of your plan, a display limit applies: a standard Collection list typically shows a maximum of 100 items without pagination, and the number of lists and nested lists per page is limited. That mainly affects how you build large overviews, not how much you can store in total.

How many CMS items can you fit per Webflow plan?

It depends strongly on your plan, and since the pricing revision of May 2026 it also differs per site whether you are already on the new structure or still on the old one. Webflow has merged the separate CMS and Business plans into a Premium plan.

In the new structure it looks roughly like this:

• Starter (free): meant for building and testing, with a very limited number of CMS items. Not intended for a live, content-heavy site.
• Basic: a paid entry plan for static sites, typically without CMS functionality. If you intend dynamic content, this will not be enough.
• Premium: the workhorse for most marketing sites, with typically 20,000 CMS items and 40 Collections included, for about 25 dollars per month with annual billing. Webflow bills in dollars.
• Team and Enterprise: for larger organizations. The Team plan offers among other things more Collections (in the order of 100), and Enterprise works with custom limits that lie far above the self-service plans.

If your site is still on an older plan, the earlier limits apply until you renew: the old CMS plan sat around 2,000 items and 20 Collections, the old Business plan around 10,000 items and 40 Collections. According to Webflow, existing sites only move to the new limits at their next renewal or billing. So treat these numbers as a guideline and always check your own plan in your Webflow dashboard and on Webflow’s current pricing page, because plans and limits change.

When do you run into the limit in practice?

For most B2B sites the CMS limit is not a problem; you often only get close with very specific content models. A typical company site with a few hundred blog articles, a handful of cases, job openings and team members stays well below even the older CMS plan.

The limit comes into view in situations like these:

• A large knowledge base or support center with thousands of articles that you keep expanding structurally.
• An extensive product or service catalog where each product, each variant or each location is its own item.
• Multilingual content, because each language version of an item often counts separately. Three languages can roughly triple your item count.
• Many cross-referencing content types, such as authors, categories, tags and related items, which together drive up the number of Collections.

Besides the storage ceiling, you sometimes notice the display limit sooner. If you want to show hundreds of items in a single overview, you have to work with pagination or smart filtering instead of dumping everything into one list. That is more a design choice than a blocker, but it does determine how you set up your website architecture.

Why does this matter for your site’s growth?

Because the right choice depends on where you want to be in two to three years, not on where you are today. A content-heavy growth strategy, for example a serious SEO or content hub approach, can go from dozens to thousands of items in a few years. You then want to know in advance whether your plan can handle that and what an upgrade costs.

At the same time, it is fair to say: for very many B2B companies this is a theoretical problem. If your goal is to generate more and better leads with your website, the gain rarely lies in the number of CMS items, but in sharp content, clear navigation and strong conversion points. We prefer to steer clients toward leads and revenue rather than toward stuffing a database. If you do run into limits, that is a good moment to check whether your content is still logically structured, or whether you have simply grown and need a heavier plan.

What are your options if you hit the Webflow CMS limit?

You have roughly three routes, and which one fits depends on your team, budget and growth plan. There is no universally right choice.

Upgrading to a higher plan. The simplest step. If you are on an older or lighter plan, an upgrade to Premium typically lifts you to 20,000 items and 40 Collections. For most content-heavy marketing sites that is plenty, and you change nothing about your setup.

Restructuring content. Sometimes you are not stuck on the ceiling, but on a messy content model. By cleaning up language versions, old items or duplicate content types, or by merging things, you often gain more room than you think. This is also the moment to review your information structure.

Moving to another or headless CMS. If you really need tens of thousands of items, complex content relationships or an editorial team with specific requirements, a headless CMS or another platform can be more logical. You then decouple the content from the presentation. That gives more scalability, but also costs more development and maintenance. It is a serious decision, not a quick fix, and a switch must be planned carefully so you do not lose your rankings during the migration.

We are platform-independent and build in Webflow, WordPress and custom or headless. Which route is best depends on your situation: how much content you really manage, who works with it, your budget and your growth ambition. Webflow is strong in design, speed of building and visual management, but the CMS limits make it less suitable if you structurally work with tens of thousands of items. What you can update yourself in such a CMS and when you had better call the agency, you can read in editing your website yourself in the CMS. Another platform scales further, but requires more technical work. The right answer differs case by case.

The short summary

Webflow imposes limits on the total number of CMS items, the number of Collections and the display per page. The renewed Premium plan typically offers 20,000 items and 40 Collections, while older plans sit lower until you renew. Most B2B sites never reach those limits; you notice them mainly with large knowledge bases, extensive catalogs or multilingual content. If your content hits the limit, you choose between upgrading, restructuring or another CMS, depending on your growth plan. Want to know which platform fits your content and goals? Take a look at our approach to website development or first read the broader guide on having a B2B website built.

Schedule your free intake