Why every article about Webflow's limits contradicts every other one
Your Webflow limits depend on when the plan was bought, not which plan it is. Two sites on the same named plan can have different ceilings, which is why the published numbers conflict. Here they are, from Webflow's own documentation.
Search for Webflow's CMS limits and the first page of results disagrees with itself. One article says 30 fields per collection, another says 60. One says 2 nested lists per page, another says 10. Item caps are quoted as 2,000, 10,000 and 20,000 with no obvious pattern. It is tempting to conclude that most of these articles are careless. Several are, but the underlying reason is more interesting and it is the thing worth knowing.
Webflow's limits are not a property of your plan. They are a property of when you bought your plan.
The July 2024 split
On 15 July 2024 Webflow changed the limits attached to its Site plans. Crucially, it did not apply the change retroactively. Plans purchased before that date continue to operate under their legacy entitlements. So a CMS plan bought in 2023 and a CMS plan bought last week are the same product with different ceilings, and an article written about either one is accurate about that one only.
| Limit | Legacy, before 15 Jul 2024 | Current | Plan |
|---|---|---|---|
| Fields per Collection | 30 | 60 | Starter and CMS |
| References per Collection | 5 | 10 | Starter and CMS |
| Static pages | 150 | 300 | Business |
| Bandwidth | 400GB | 100GB, decreased | Business |
| Bandwidth | 200GB | 50GB, decreased | CMS |
| Bandwidth | 50GB | 10GB, decreased | Basic |
| Custom code characters | Lower | 50,000, all paid plans | All paid |
The misreading that is everywhere
Separately from the legacy split, one specific error has propagated through most of the published guides. You will read that Webflow allows 20 collections per site on the CMS plan and 40 on Business. Webflow's dynamic content documentation does not say that. What it documents is 40 Collection lists per site page, which is a limit on how many dynamic lists you can place on a single page, not on how many Collections your site may contain.
The nested list numbers have been garbled in the same way, and often inverted. Webflow documents 10 nested Collection lists per page, and up to 100 Collection items per nested list. Several guides state the opposite pair, 2 nested lists carrying 10 items, which would make a good deal of ordinary Webflow work impossible.
- 40 Collection lists per site page.
- 10 nested Collection lists per site page.
- 100 Collection items per Collection list, unless pagination is enabled.
- 100 Collection items per nested Collection list.
CMS items, and the add-ons nobody mentions
The Business plan includes 10,000 CMS items. Add-ons of 5,000 and 10,000 exist, and self-serve customers can reach a total of 20,000 items per site including the 10,000 the plan carries. That is where the 10,000 and 20,000 figures both come from, and both are right depending on whether an add-on is being counted.
The trap in upgrading to get the new limits
If you are on a legacy plan and you want the 60 fields, upgrading looks like the obvious move. Webflow states plainly that manually upgrading a legacy plan removes all legacy entitlements, bandwidth included. Since bandwidth went down rather than up in the same release, a site with a legacy CMS plan trades 200GB for 50GB in exchange for the extra fields. For a media-heavy site that is a bad trade made for a good reason.
Worth knowing too: exceeding your bandwidth limit two months running converts you to the new plan automatically. So the legacy entitlement is not permanent, and a traffic spike can end it without anybody deciding anything.
How to find out what your own site actually has
Do not take it from an article, this one included. Webflow added a usage dashboard in site settings in the same release, and it reports the limits your site is actually operating under rather than the ones its plan is advertised with. That is the only authoritative answer for your project, and it takes about ten seconds to check.
If the limits turn out to be the thing blocking the build, the honest next question is whether Webflow is the right tool for it, which is covered in when not to use Webflow. Framer has its own ceilings and they sit in different places, covered in Framer's CMS limits.
