Publishing has been steady, traffic has not moved, and a builder’s notice says the site is close to a plan limit. On some builders the meter being tripped is not visitors. It is the count of CMS items, and it rises with every post, case study and resource page you add.
The meter nobody checks until the notice arrives
Webflow’s pricing page defines CMS items as “Individual CMS records, like a blog post or office location, that can be organized into CMS Collections.” It defines collections as groups of CMS items “that share a common template or layout.” Framer’s page is shorter: its CMS items row reads “Add CMS items to your collections.”
A blog, a case library and a resources section are three collections but, on a plan with one item figure, they appear to draw on one number. Webflow’s page states its prices are “per site” and lists one CMS item figure per site plan, as Framer does. Neither page, in the text fetched, says in so many words that every collection shares the item allowance. Treat shared draw as the working assumption and confirm it with support before you rely on it.
Stated item caps, builder by builder
The table lists only figures read from pricing pages that returned HTTP 200 on 2026-10-12 and mapped to the plan column shown. Empty cells say none listed. Webflow’s help articles returned 403 to curl on 2026-10-08 and were not used, so Webflow is cited from its pricing page only. Wix’s pricing page and help pages did not yield an item figure in this check, so Wix is not in the table and no number is inferred for it.
| Builder | Plan | Stated CMS item cap | Stated collection cap | Source URL | Date fetched |
|---|---|---|---|---|---|
| Framer | Basic | 1,000 | 2 | https://www.framer.com/pricing | 2026-10-12 |
| Framer | Pro | 2,500 | 10 | https://www.framer.com/pricing | 2026-10-12 |
| Framer | Enterprise | Custom | Custom | https://www.framer.com/pricing | 2026-10-12 |
| Webflow | Starter | 50 | 20 | https://webflow.com/pricing | 2026-10-12 |
| Webflow | Basic | none listed | none listed | https://webflow.com/pricing | 2026-10-12 |
| Webflow | Premium (labelled Premier in the comparison table) | 20,000 | 40 | https://webflow.com/pricing | 2026-10-12 |
| Webflow | Team | 20,000, more for a separate fee | 100 | https://webflow.com/pricing | 2026-10-12 |
| Webflow | Enterprise | Custom | none listed | https://webflow.com/pricing | 2026-10-12 |
Framer’s page adds that item capacity can be extended “then $20 per 10,000 (40,000 max)” and collections “then $40 per 10 (40 max).” Webflow describes Basic as “for simple sites that don’t need a CMS.” The Webflow page text carries more than one plan grouping. Only the Starter, Basic, Premier and Team, Enterprise groupings were tabulated. Other plan groupings on the page carry further numbers, but none that could be mapped to a CMS item cap for a named plan, so they are omitted.
Builders that do not publish an item cap on the pricing page
Ghost’s pricing page (https://ghost.org/pricing/) meters something else. It meters staff users and members by tier, and states that contributors are always free and do not count towards plan limits. Whether Ghost limits posts is not something that page states either way, so nothing is claimed here.
The Squarespace pricing page (https://www.squarespace.com/pricing) as fetched lists no CMS item count. Duda’s page (https://www.duda.co/pricing) lists dynamic pages as Limited, Standard or Advanced rather than as a number. This is what each page does not say, not a claim that no limit exists.
For someone planning a content hub, an absent number is itself a finding. Ask support, or read the terms of service, before you build several hundred records on a platform where the ceiling is unstated.
Counting your own items: a worked example
This is illustrative. The numbers are invented and are not data from any real site. Picture a site with a blog of 1,400 posts, a case library of 600 entries and a resources collection of 900 entries. That is 2,900 items before anything else.
Now add supporting records: categories and tags (150), authors (25) and FAQ entries (325). These often live in their own collections via reference fields. The pages fetched do not state that categories, authors or FAQ entries count toward the item cap, so check that with the vendor. If they do, the total is 2,900 + 150 + 25 + 325 = 3,400 items across six collections.
Compare 3,400 with the table. On Framer, Basic (1,000) and Pro (2,500) both fall short, so no fixed tier clears it; the route is Pro plus the item add-on. On Webflow, Starter (50) falls short and Basic lists none, so the first plan whose stated cap clears 3,400 is Premium at 20,000, with 40 collections.
The add-on arithmetic: Framer prices items at $20 per 10,000. The page does not say whether a step adds to Pro’s 2,500 or replaces it. Either way one step clears 3,400, since 2,500 + 10,000 is 12,500 and a replaced figure is still 10,000. The add-on cost is therefore $20 at the page’s rate, on top of the Pro plan price. Moving the 325 FAQ entries into ordinary pages would bring the total to 3,075, still above Pro’s 2,500, so trimming does not avoid the step here.
Plan transitions that items force, and ones traffic would not
Reading the table as a ladder, these are the stated steps where the item cap rises and what else moves with it:
- Framer Basic to Pro: items 1,000 to 2,500, collections 2 to 10, site pages 30 to 150, bandwidth 50 GB to 100 GB. The page toggle read $10 and $30 per month on yearly billing.
- Webflow Starter to Premium: items 50 to 20,000, collections 20 to 40. The page’s comparison table lists bandwidth of 1 GB for Starter, 10 GB for Basic and up to 2.5 TB per month for Premier.
- Webflow Premium to Team: the item figure stays at 20,000 while collections rise from 40 to 100, and the Team entry notes more items are available for a separate fee.
A step moves several meters at once, so the notice does not tell you which one tripped. On Framer, compare your item count with the item cap, and your monthly transfer with the bandwidth figure (50 GB or 100 GB). Framer’s FAQ says it allows some limits, “like bandwidth,” to be exceeded for one month, so the two overages may be handled differently. A traffic spike with a low item count points to bandwidth. A flat month with a growing collection points to items.
Before you reach the cap: archive or merge low-value items such as near-duplicate posts, move static material to ordinary pages, or plan to move the hub to another platform. That is practice, not a vendor recommendation.
The same mechanism shows up in other tool categories; see record caps on Airtable and Notion. For builder plan limits from a different angle, see what free portfolio plans hide.
Before you build the hub
Three questions are worth asking before you pick a builder. What is the item cap on the plan I will be on in a year? Is the cap per site or per collection? And what does the next step cost? Before comparing plans, list every collection on your site, write down its record count, and add the supporting collections. That one number is what you hold against the table.
Prices verified 2026-10-12 from https://www.framer.com/pricing and https://webflow.com/pricing, with Ghost, Squarespace and Duda read from https://ghost.org/pricing/, https://www.squarespace.com/pricing and https://www.duda.co/pricing on the same date. This is not Watchdog data and is not on the re-verification schedule, so check the vendor pages again before you decide.
followedapp is published by the team behind RecurPost, which is covered vendor #34 under the same rules as every other vendor.
FAQ
What counts as a CMS item on a website builder?
Webflow’s pricing page defines a CMS item as an individual CMS record, such as a blog post or office location, organized into a CMS Collection. Whether supporting collections like authors or categories count toward the cap is not stated on the pages fetched, so confirm it with the vendor.
Do a blog and a case library share the same item limit?
The pages fetched list one item figure per plan and prices per site, which is consistent with a shared allowance, but they do not say so in words.
Can you buy more CMS items without changing plan?
On Framer, the pricing page fetched on 2026-10-12 lists an item add-on of $20 per 10,000, up to 40,000 maximum. For Webflow, the Team entry says only that more items can be added for a separate fee, with no price stated in the text read.
Which hits first, the item limit or the page limit?
Framer’s fixed Basic tier lists 30 pages against 1,000 items. Because CMS items generate pages from collection templates, a content hub can reach one limit before the other, but there is no universal rule.
Sources
- Framer pricing, fetched 2026-10-12 (HTTP 200)
- Webflow pricing, fetched 2026-10-12 (HTTP 200)
- Ghost pricing, fetched 2026-10-12 (HTTP 200)
- Squarespace pricing, fetched 2026-10-12 (HTTP 200)
- Duda pricing, fetched 2026-10-12 (HTTP 200)