- There are two kinds of limit: how much the CMS can store, set by your plan, and how much one page can show, set for every plan.
- Storage limits cover CMS items, Collections, fields per Collection and reference fields. Check the current numbers on Webflow's pricing page.
- Display limits: a Collection list shows up to 100 items by default, and a page can hold up to 40 Collection lists, with nesting capped.
- Budget items for three years, not for launch day. Blogs, jobs and resources grow; teams and categories do not.
- Not everything needs a Collection. Content that lives on one page can stay on that page.
The short answer
Webflow sets two kinds of CMS limit. Your site plan decides how much you can store: the number of CMS items, the number of Collections, and the fields and reference fields each Collection can have. Separately, every plan has limits on what one page can display: by default a Collection list shows up to 100 items, and a page can hold up to 40 Collection lists. Plan around both before you build. Count the content you will have in three years, not at launch, and only make a Collection for content that really repeats.
The exact storage numbers change by plan and over time. Check them on Webflow's pricing page, under Compare all site plans, in the CMS section.
Storage limits: set by your plan
Webflow's pricing page lists these CMS rows for each plan:
- CMS items. Every blog post, job, author or location is one item. Lower plans allow far fewer than higher ones.
- CMS Collections. Each content type, such as Posts, Authors or Categories, is one Collection.
- Collection structure. A cap on fields per Collection, and a separate cap on reference fields.
- Content management APIs. A request rate for the CMS API, which matters if you import or sync content with code.
Plans and their numbers change, so we do not repeat them here. Write down the current numbers for your plan before you plan anything else. For how plans fit together, see how Webflow pricing works.
Display limits: the same on every plan
Webflow's help page on dynamic content limits says these limits control what visitors see on a page, not what you can store:
- Up to 40 Collection lists per page, nested lists included.
- Up to ten nested Collection lists per page, and up to three levels of nesting.
- Each Collection list shows up to 100 items by default. Pagination splits the rest across pages of up to 100.
- You can show more than 100 on one page by duplicating the list and using Skip, but each copy counts toward the 40.
- You can't nest Collection lists inside components.
The last one surprises teams who build everything as components. Plan where nested lists will live before you design those sections.
Worked example: an item budget
Here is how we would budget a typical B2B marketing site. The numbers are an example, not a rule. Use your own publishing plans.
| Collection | At launch | Added per year | In three years |
|---|---|---|---|
| Blog posts | 40 | 100 | 340 |
| Authors | 5 | 2 | 11 |
| Blog categories | 6 | 1 | 9 |
| Case studies | 8 | 6 | 26 |
| Jobs | 4 | 20 | 64 |
| Integrations | 30 | 15 | 75 |
| Landing pages | 10 | 40 | 130 |
| Total | 103 | 184 | 655 |
Three things show up straight away. Most growth comes from two or three Collections. Jobs pile up unless someone removes old ones. And landing pages built from the CMS can become the biggest Collection of all; our post on CMS API landing pages covers that case.
Compare the three-year total with your plan's item limit. If it lands near the cap, plan the clean-up or the upgrade now.
Does this need to be a Collection?
Collections cost items, fields and plan limits. Use one when content repeats, has its own page, or is reused in several places. Leave it on the page when it does not.
- Yes: blog posts, case studies, jobs, authors, integrations, locations.
- Usually yes: testimonials and logos, if they appear on many pages.
- Often no: FAQs used on one page, team members on the About page only, a short list of three values.
- Often an option field, not a Collection: labels with a fixed short list, such as a status or a region, when they need no page of their own.
A Collection you never needed still takes a slot from your plan, and it adds a step for every editor.
Budgeting fields and references
Fields run out faster than people expect on busy templates. A case study with a hero, four stats, three quotes and a gallery can use a lot of them. Ways to keep the count down:
- Use rich text for long sections instead of many small text fields, when the layout allows it.
- Group repeating things into their own Collection, such as quotes, and link them with a multi-reference field.
- Share one SEO set of fields per template: meta title, meta description and social image.
- Drop fields nobody fills in. An empty field is still a field.
References have their own cap, separate from the field cap. Map them early: which Collection points to which. Our Webflow CMS guide explains reference and multi-reference fields in more detail.
Planning for lists and filters
The 100-item display limit matters most on index pages. A blog index with 340 posts needs pagination, or filters that load more. Plan which it will be in the design, not after launch. If a page needs many nested lists, such as categories each with their posts, count them against the limits above, and remember nested lists cannot sit inside components.
For large imports, note that Webflow's help on responsive images says images added through CSV import or the API do not get responsive variants. Size them before import.
When you get close to a limit
- Clean up. Remove expired jobs, merged posts and test items. Redirect any removed pages that had traffic.
- Merge Collections that store the same kind of thing, using an option field to tell them apart.
- Move up a plan if the content is worth it. Check the new plan's numbers first.
- Split the content. A docs site or a huge resource library can live on its own site or another CMS. See one Webflow site or several.
- Change platform when content is the product. For very large libraries, a headless CMS such as Sanity with Astro can be a better fit; we compare them in Webflow vs Astro.
A one-page planning checklist
- Current plan numbers written down: items, Collections, fields, reference fields.
- Every Collection listed, with a reason it is a Collection.
- Three-year item budget per Collection.
- Field list per template, with the count under the cap.
- Reference map: which Collection points where.
- Index pages: pagination or filters decided.
- Nested lists counted per page, none inside components.
- Owner and routine for clean-up, such as old jobs each quarter.
What to do next
Run the item budget for your own site before the design is final. It takes an hour and it saves a rebuild later. If you want a second pair of eyes on your CMS plan, see our Webflow CMS service or send us your sitemap.
Terms used: Webflow, Webflow CMS



