Webflow CMS Items Limit in 2026: How to Overcome It

Webflow CMS limits the number of items, collections, and fields you can use depending on your plan: 2,000 items on the CMS plan, up to 20,000 on Business, and custom limits on Enterprise. If you've hit — or are approaching — one of these limits, here's everything you need to know and the best ways to work around them.

Webflow CMS Limits by Plan

SEO-friendly Solutions

If your content needs to be public and easily indexed by search engines, but you have reached or are close to the 20,000-item limit in Webflow CMS, you have two main options:

1. Webflow CMS Automation (or Enterprise Plan)

The simplest workaround that keeps you inside Webflow is to continue using Webflow CMS and create an automation to remove items from the CMS that are no longer needed and store them in an external database (for example, if an item doesn't need to be public after X days). Alternatively, you can upgrade to the Webflow Enterprise plan (which can cost from $15k to $60k per year). This limitation exists because SEO-friendly content must be generated on the backend, and within Webflow, this is only possible using their built-in CMS.

2. Reverse Proxy

A reverse proxy allows you to host your content on an external platform—such as a Next.js application—while making it appear seamlessly under your main Webflow domain. For instance, you could serve yoursite.com/blog from a completely separate server without your visitors ever noticing the transition.

Since the content lives outside of Webflow's infrastructure, this effectively removes the CMS item limit while keeping everything fully SEO-friendly.

The Content Editing Experience One of the main concerns when moving away from Webflow CMS is losing its intuitive editor. Fortunately, by using an external framework, you can easily connect a Headless CMS (like Payload, Sanity, or Contentful). This allows your content team to continue managing articles through a dedicated, user-friendly interface that is just as good—if not better—than Webflow's, while the frontend remains fully integrated under your Webflow domain.

There are two main ways to set this up:

The Classic Reverse Proxy

Historically, setting up a reverse proxy was a technically complex process — requiring external server configuration, DNS management, and ongoing maintenance.

The main trade-off: being hosted outside of Webflow meant losing access to the Webflow Designer. Your external platform wouldn't share Webflow's built-in UI components and templates, so you needed to rebuild your frontend separately.

Native Reverse Proxy (Webflow Cloud)

To solve these issues, Webflow introduced a native reverse proxy solution through Webflow Cloud. This allows you to host apps built with traditional code (like Next.js) directly inside Webflow's hosting infrastructure.

With this approach, you simply specify which route your custom app should be served from (for example, /blog), and Webflow handles the proxying natively.

Even better, it solves the UI trade-off. By using Webflow DevLink, you can visually design components inside Webflow (like your Navbar and Footer) and import them directly into your Next.js project as React components. This gives you the best of both worlds: infinite scalability for your CMS content through code, while keeping your visual components perfectly in sync with the Webflow Designer.

Non SEO-friendly: The WWX Stack

If your content doesn't need to be indexed — for example, everything inside a restricted or members-only area — and you want to stay on Webflow, you can pair it with Wized (client-side logic) and Xano (backend and database), commonly known as the WWX stack.

Wized lets you fetch data from Xano and inject it into your Webflow components, bypassing the CMS entirely. Since the content is loaded client-side via JavaScript, it won't be immediately available to search engine crawlers¹ — but that's fine for dashboards, member portals, and internal tools.

This approach works well for many projects, but has some trade-offs: testing is limited to manual checks, the architecture is tightly coupled to Webflow's rendering layer, and scaling a complex app can become harder to manage over time.

Going Custom: Code-Based Architecture

For projects that need a more robust and scalable foundation — whether SEO is required or not — a code-based approach removes platform constraints entirely. Using a framework like Next.js paired with a backend like Supabase (or any modern stack), you get:

• Unlimited data — no item caps, no collection limits
• SEO-friendly by default — unlike the WWX stack, Next.js supports static generation (SSG) and server-side rendering (SSR), so your content is fully rendered and indexable by search engines
• Automated testing — unit tests, integration tests, and CI/CD pipelines to catch bugs before they reach production
• Full architectural control — API routes, caching strategies, and real-time features
• Team scalability — version control, code review, and established development workflows that grow with your team

This path requires development expertise, but the result is a product that scales predictably without platform constraints. If your project is growing beyond what visual builders can handle — frequent updates, complex user flows, or multiple integrations — this is the approach that pays off long-term.

Frequently Asked Questions

What is the Webflow CMS item limit?

The Webflow CMS item limit depends on your plan: 2,000 items on the CMS plan, up to 20,000 on Business, and custom limits on Enterprise. The Basic plan doesn't include CMS access.

What are the Webflow CMS collection and field limits?

On the CMS plan you get 20 collections, on Business 40. Each collection supports up to 60 fields regardless of plan.

Can I increase the Webflow CMS item limit without upgrading to Enterprise?

Yes. If your content doesn't need to be SEO-indexed, you can bypass the limit entirely by moving your data to an external database and loading it client-side (e.g., Webflow + Wized + Xano) or by building a fully custom application (e.g., Next.js + Supabase). If SEO is required, you can either automate the removal of old items to stay under the limit, or use a Native Reverse Proxy (Webflow Cloud) with a Headless CMS to serve unlimited pages under your existing Webflow domain.

What happens when I hit the Webflow CMS limit?

Webflow will prevent you from adding new items to any collection until you either delete existing items, upgrade your plan, or move content to an external database.

Is Webflow CMS good for large-scale content?

For up to 20,000 SEO-indexed items it works well. Beyond that, you'll need the Enterprise plan, a Webflow Cloud native reverse proxy with a Headless CMS, or a fully custom code-based architecture that removes platform limits altogether.

To Recap

If your goal is to generate SEO-friendly content and you are under the 20k item limit, the best option is to stick with Webflow CMS. If SEO is not a priority and you want to stay on Webflow, the WWX stack (Wized + Xano) lets you bypass the limit client-side. If you want to keep using Webflow for design but need unlimited SEO content, a native reverse proxy via Webflow Cloud combined with DevLink and a Headless CMS gives you the best of both worlds. And if you need a fully robust, testable, and scalable foundation — with or without SEO — a code-based architecture (like Next.js + Supabase) gives you complete control, automated testing, and no platform constraints.