Webflow CMS Limits in 2026: Every Limit Explained with Workarounds

Webflow CMS item limits by plan: Starter (free workspace) = 50 items lifetime. CMS plan = 2,000 items across all Collections. Business plan = 10,000 items (some sources cite 20,000 — Webflow's limits page is authoritative). Enterprise = custom. These are total items across ALL Collections — not per Collection. A site with 10 Collections on a CMS plan shares the 2,000-item pool across all of them. Check your current usage: CMS panel (top bar context) → click on any Collection → item count is displayed next to the collection name. To see total usage, go to Site Settings > CMS > usage indicator.

Each Collection can have a maximum of 30 custom fields (not counting the auto-generated Name, Slug, Created On, Updated On, Published On, and Status fields). This limit is universal across all plans including Enterprise. If your schema needs more than 30 fields: Option 1 — split the Collection into two linked Collections connected via a Reference field (e.g., 'Products' + 'Product Details' with a one-to-one Reference). Option 2 — use a Rich Text field to store structured content that combines multiple logical 'fields' into one formatted block. Option 3 — store extended metadata in a JSON-formatted Plain Text field and parse it with custom code. Note: once a field type is set, it cannot be changed — delete and recreate if needed.

By default, a Collection List shows a maximum of 100 items (or the limit set under 'Limit items'). Native pagination handles larger datasets but forces a full page reload. For load-more without page navigation — or to display more than 100 items in a single list — install Finsweet CMS Load. Steps: Go to Site Settings > Custom Code > Before </body> code > add the Finsweet script tag: `<script defer src='https://cdn.finsweet.com/files/cms-attributes-v1.js'></script>`. On the Collection List Wrapper element: add custom attribute (Element Settings D > Custom Attributes) `fs-cmsload-element` = `list`. On the load-more button: add attribute `fs-cmsload-element` = `load-more`. Set the Collection List limit to 100 items in Element Settings. Finsweet fetches subsequent pages automatically when the button is clicked.

Webflow limits nested Collection Lists (a list inside another list's item) to 2 per page and 10 items per nested list on non-Enterprise plans. This is a hard platform limit you cannot override in the Designer. Finsweet CMS Nest removes both restrictions. Installation: same script tag as CMS Load (the Finsweet v1 script covers all Attributes). Implementation: on the parent Collection List Wrapper, add attribute `fs-cmsnest-element` = `list`. On the child/nested Collection List Wrapper, add `fs-cmsnest-element` = `list`. Finsweet fetches child data client-side, bypassing Webflow's server-side nesting limits. Note: adds a client-side fetch on page load — test performance on pages with many parent items.

Webflow's native filtering requires a page reload (or a separate Collection List) for each filter combination. Finsweet CMS Filter adds client-side filtering with no page reload. It works by loading ALL Collection List items (up to 100 per load batch) and filtering the DOM client-side. Setup: add Finsweet script to site. Collection List Wrapper attribute: `fs-cmsfilter-element` = `list`. Each filterable field needs a corresponding filter UI element (checkbox, radio, dropdown, or text input). On filter UI elements: attribute `fs-cmsfilter-field` = [field slug], `fs-cmsfilter-value` = [value to match]. The value must match the CMS field value exactly. Multiple filter elements of the same field use OR logic; filters across different fields use AND logic.

If you need more than 20,000 items (Business plan ceiling), the extreme workaround is splitting content across multiple Webflow projects and proxying the frontend. Architecture: Project A hosts the main site and CMS up to the limit. Project B hosts overflow content (e.g., archived blog posts, regional content). A reverse proxy (Cloudflare Worker or Netlify Edge Function) routes /blog/* to Project A and /blog/archive/* to Project B, presenting a unified domain to users. This is a complex engineering pattern — only pursue it when you genuinely exceed Business plan limits. For most sites, Business plan (10,000–20,000 items) is sufficient for years of growth.

Each page can contain a maximum of 20 Collection List elements (across all Collections). On complex directory or marketplace pages that rely heavily on CMS data, this limit can be reached. Optimization strategies: 1) Consolidate multiple lists with similar layouts into one list with more sophisticated filtering. 2) Use tabs or toggles where only one list is 'active' at a time — Webflow still counts all lists toward the limit, so use Finsweet CMS Tabs which renders lists on demand. 3) Use JavaScript to fetch and render additional CMS data via the Webflow Data API without Collection List elements (requires custom code added to Page Settings > Before </body>). 4) Evaluate whether some 'lists' can be static elements — if a set of items never changes, hard-code them rather than using CMS.

Proactively monitor your CMS usage to avoid hitting limits unexpectedly. Check item count per Collection: CMS panel > each Collection shows item count in the list. Check total fields per Collection: CMS panel > Collection > Edit Fields > count the fields. For Collections approaching 2,000 items (CMS plan): initiate a plan upgrade before the limit is reached — Webflow blocks new item creation (not editing) once the limit is hit. Set up a simple spreadsheet tracking Collection name, current items, fields used, and projected growth rate for any content type that grows continuously (blog posts, products, user-generated content).