Webflow's Premium Site plan includes 20,000 CMS items and 40 Collections, according to its pricing page in October 2026. That is ten times the 2,000 items the old CMS plan held before Webflow merged its CMS and Business plans on 13 May 2026. Most sites never come close to the item count. The limits that bite sooner are the smaller ones: 100 items per Collection list, 10 reference fields per Collection, and an API that answers 120 requests a minute.
This guide lists every CMS limit Webflow currently publishes, by plan, then the workarounds we would ship. Numbers come from Webflow's pricing page, help centre and developer documentation unless stated.
The plan limits after the May 2026 change
From 13 May 2026, Webflow combined the CMS and Business Site plans into one Premium plan, at $25 a month billed yearly or $39 monthly, and added a Team plan for companies that have outgrown self-serve. The CMS add-ons that used to sell extra items in blocks of 5,000 and 10,000 were removed, because Premium now includes what they unlocked.
| Limit | Starter (free) | Basic | Premium | Team | Enterprise |
|---|---|---|---|---|---|
| CMS items | 50 | No CMS | 20,000 | 20,000, more for a fee | Custom |
| CMS Collections | 20 | No CMS | 40 | 100 | Custom |
| Static pages | 2 | 300 | 300 | 500 | Custom |
| Fields per Collection | 60 | No CMS | 60 (see note) | 100 | Custom |
| Reference fields per Collection | 10 | No CMS | Up to 10 | 20 | 20 |
| CMS API requests per minute | 60 | 60 | 120 | 600 | Custom |
| Price, billed yearly | Free | $15 a month | $25 a month | $2,500 a month, annual contract | Quoted |
Source: Webflow pricing page, read 2026-10-20; Webflow help centre articles on plan changes and reference fields; Webflow developer docs, rate limits
The Premium field count needs a caveat. The pricing page lists fields only for Team. The last figure Webflow published for the CMS plan, in July 2024, was 60 fields and 10 references per Collection, and the May 2026 notes do not change it. The reference field article says non-Enterprise plans get "up to 10 reference fields, depending on the site plan", and points to Site settings, Plans, All site features for the exact number on your site.
The rollout dates matter for agencies. New purchases got the new limits on 13 May 2026. For most existing sites the changes apply from 29 June 2026. Sites in Freelancer or Agency Workspaces, and sites on legacy discounts from 2022 or earlier, move from 16 November 2026, and even then only at the next renewal or on a billable change, which Webflow defines as an upgrade, a downgrade or a switch between monthly and yearly billing. A client site sitting in your Agency Workspace on a CMS plan can still be capped at 2,000 items and 20 Collections this month.
Legacy plans are a second trap. Webflow's July 2024 update raised fields per Collection from 30 to 60 and references from 5 to 10, but only for plans bought, changed or transferred after 15 July 2024. A site bought in 2023 and left alone keeps 30 fields and 5 references until someone changes the plan.
Limits inside a Collection
The item count is a ceiling for the whole site. The limits inside each Collection shape the content model, and force redesigns mid-build.
| Limit | Value | What it blocks |
|---|---|---|
| Fields per Collection | 60; 100 on Team | Wide types, such as a location with hours per day |
| Reference fields per Collection | Up to 10; 20 on Team and Enterprise | Hub types such as case studies |
| Images per multi-image field | 25 | Large galleries |
| Image file size | 4 MB | Uncompressed photography |
| Options from one CSV column | 100 | Long category lists |
| CSV import file | 4 MB | One-upload migrations |
| Sort by a reference field | Not supported | Lists ordered by author name |
| Filter or sort a multi-reference list | Not supported | Related lists sorted by date |
Source: Webflow help centre, Collection field articles updated 2026-08-01 to 2026-10-14; CSV import article updated 2026-08-18
The multi-reference article answers "Why can't I add a reference field?" with the same cap of 10, so we plan as if single and multi-reference fields share one budget. That budget goes quickly on a B2B site. A case study that references an industry, a service, a region, an author, a testimonial and three related case studies has used six before anyone adds a partner logo.
Limits on a page: lists, nesting and the 100-item ceiling
Display limits control what one page shows, not what the CMS holds, as Webflow's help centre puts it.
| Limit | Value |
|---|---|
| Collection lists per page, nested ones included | 40 |
| Nested Collection lists per page | 10 |
| Nesting depth | 3 levels |
| Items shown per Collection list, nested lists included | 100 |
| Items per page with pagination on | 1 to 100 |
| Nested Collection lists inside components | Not allowed |
| Filters, sorting, pagination, display limits | Dynamic lists only, not curated lists |
Source: Webflow help centre, Dynamic content limits (updated 2026-10-06) and Nest Collection lists (updated 2026-04-09)
These numbers moved recently, and third-party documentation has not caught up: Finsweet's List Nest page still describes Webflow's limit as two nested lists with a maximum of 10 items each, against 10 nested lists of up to 100 items in Webflow's current help article. Check the date on any limits table before you design around it, including ours.
The client-side filter trap. A filter, search or sort script that runs in the browser can only work on items that are on the page. With 140 case studies in a list of 100, items 101 to 140 never reach the browser, so a visitor filtering by an industry whose items all sit past 100 sees an empty grid. Nothing errors. The fix is to load every item first, with pagination plus a loader script, or to cut the list with a native Webflow filter before it renders.
Limits on the API, imports and publishing
Webflow applies rate limits per API key, by Site plan: 60 requests a minute on Starter and Basic, 120 on Premium, 600 on Team and custom on Enterprise. A request over the limit returns HTTP 429 with a Retry-After header, typically 60 seconds. Site publishing through the API is limited to one successful publish per minute.
| Limit | Value |
|---|---|
| Requests per minute, per API key | 60 / 120 / 600 / custom |
| Items created per request | 100, each locale variant counted |
| Items returned per list request | 100, paged with offset |
| Filter terms per list request | 10, plus 2 text-search terms |
| Sort fields per list request | 3 |
| Site publishes | 1 a minute |
| Cached Content Delivery API reads | Effectively unlimited |
Source: Webflow developer documentation, Data API v2, read 2026-10-20
The arithmetic is worth doing before a migration. Creating 20,000 items at 100 per request is 200 requests, under two minutes at Premium's 120 a minute. Updating the same 20,000 items one per request is 20,000 requests, about 167 minutes at 120 a minute and over five and a half hours at 60. Batch writes, and use webhooks rather than polling. On a multilingual site, an item created in three locales counts as three of the 100 in a request.
Reads have a separate route. Webflow's Content Delivery API serves published items from a cache at api-cdn.webflow.com. Cached requests have effectively no rate limit; uncached requests count against the plan. Anything that reads Webflow content into another app should use it.
Workarounds that hold, and ones that do not
We build marketing sites in Webflow and applications in Next.js, so we have a bias towards keeping marketing content in Webflow and moving data-shaped content out. Read the table with that in mind. One common trick is missing on purpose: storing related slugs in a plain text field and resolving them with a script, to dodge the reference cap, breaks silently when a slug changes.
| Limit | Workaround | What it costs |
|---|---|---|
| 100 items per list | Native pagination | Items past 100 move to page 2 |
| 100 items on one page | Duplicate the list, Skip 100 | Each copy uses one of the 40 lists |
| 100 items, filterable grid | Pagination plus Finsweet List Load, Render All | JavaScript; slower first render |
| 40 Collections | Merge small types, Option field for type | One shared template page |
| 40 Collections | Fixed taxonomies as Option fields | No landing page per tag |
| 10 reference fields | Fixed taxonomies as Option fields | No filtering by the page's tag |
| 60 fields | Child Collection referenced from the parent | One reference and one Collection |
| 10 nested lists | Finsweet List Nest | One request per parent item |
| 20,000 items | Archive old items to CSV, then delete | 301 redirects for lost URLs |
| 20,000 items | Generated pages in a Next.js app | A second stack to maintain |
| API rate limit | Bulk writes, webhooks, cached reads | Engineering time |
Source: Webflow help centre and developer docs as above; Finsweet Attributes documentation, read 2026-10-20
What does not hold. Splitting one content type across two Collections to dodge the 100-item cap leaves two templates to keep in sync. Hiding items with CSS to fake a filter still counts them in the 100. A script doing what native pagination can do is a dependency to recheck on every Webflow change.
How we would plan a CMS so it does not hit a wall
Across the 20 or more Webflow sites we have built in twelve months, the largest CMS held over 1,200 items, well inside 20,000. Item counts are rarely the problem. The model is.
Count Collections, not items, at scoping. List every content type and every taxonomy. If taxonomies are fixed, make them Option fields and keep Collections for content that needs its own page.
Budget reference fields per Collection. Write the reference list for the busiest Collection, usually case studies or resources, before anyone builds a template. If it passes eight, simplify now; you will want the last two later.
Name the lists that must show more than 100 items. A resources hub, a glossary and a locations index are the usual three. Decide at scoping whether each gets pagination, Skip copies or a loader script, and whether any client-side filter runs over it.
Check the site's real plan. For any existing site, read the limits in Site settings, not on the pricing page, and note whether it sits in an Agency or Freelancer Workspace that will not move until 16 November 2026.
Write the API budget into any integration. A sync that runs every five minutes over 2,000 items, one request each, needs 400 requests a minute, more than three times what Premium allows.
What this means for your next Webflow build
For most B2B marketing sites, Webflow's 2026 limits are generous on storage and tight on structure. 20,000 items and 40 Collections hold a blog, case studies, a resource centre and a glossary several times over. Ten reference fields and 100 items per list are where a model gets bent, and both are easier to plan for at scoping than to fix after launch.
If your content is data-shaped, tens of thousands of generated pages from a catalogue or a database, our comparison "Webflow or Next.js for a Marketing Site? The Decision in Four Questions" covers where the line sits, and "Webflow vs Framer in 2026" compares the CMS ceilings of the two visual builders. For a site that stays in Webflow, the planning steps above are what we would run first, and our Webflow development service page explains how we scope it.
