By Mehdi HassanWhat are the Framer CMS limits?
The Framer CMS limits are plan-based caps on how many CMS collections and items a site can hold, alongside softer limits on how content can relate to other content. Higher plans and paid add-ons raise the caps. The structural limits, like how deep relations go, don't change with the plan.
We don't print exact numbers here on purpose. Our research found that third-party roundups disagree on Framer's caps, and Framer revises its plans. The reliable source is the plan comparison on Framer's pricing page. What we can give you is how the limits behave and what to do about them. If you're already deciding whether to leave, our guide to leaving Framer maps every ceiling to a destination.
Limit type | Changes with plan? | Who it hurts most |
|---|---|---|
Number of CMS items | Yes, and via add-ons | Blogs, directories, programmatic pages |
Number of collections | Yes | Sites with many content types |
Relations between collections | No | Integrations pages, multi-author blogs |
Locales for CMS content | Priced per locale | Multilingual sites |
API and sync options | No | Teams feeding content to apps or tools |
What happens when you exceed a Framer CMS item limit?
When you reach a Framer CMS item limit, you can't add more items until you upgrade, buy more capacity or delete items. Your published site keeps working, so the cap is a publishing problem rather than an outage.
The real cost shows up in the workflow. Writers stop publishing, someone has to decide what to delete, and the question of whether to pay more becomes urgent instead of planned. Teams running programmatic pages feel it first, because one template can need hundreds of items. Our guide to programmatic SEO in Framer covers how to plan those page sets within the CMS.
How do you check which Framer limit you'll hit first?
You check which Framer limit you'll hit first by counting what you have, projecting a year of growth and comparing both against the plan page. It's a short spreadsheet exercise, and it turns a surprise into a budget line.
Count items per collection
Write down each collection and its current item count, including drafts, since drafts may count toward caps.
Estimate growth
Multiply your publishing rate by 12 months for each collection. Add planned launches, such as a glossary or integrations directory.
Count collections you'll need
List content types you plan to add. Each new type is a new collection.
Add locales
If you'll translate CMS content, note how many locales you'll need and check how Framer prices them.
Compare with the current plan page
Read the limits for your plan and the next one up, plus add-on pricing, and pick the cheapest path that covers the projection.
Hypothetical example: a growing blog
For example, suppose a startup's Framer blog has 180 posts and publishes three a week. In a year that's about 150 more posts, plus a planned 120-term glossary and a 60-item integrations directory, so the site needs room for around 510 items across three collections.
If the current plan covers that with one add-on, staying is the cheap answer. If it needs two plan jumps, compare that cost against syncing the glossary from an external CMS or moving the blog. The decision comes from the projection, not from the moment someone hits the wall.
What are the workarounds before migrating off Framer?
The workarounds before migrating are upgrading or adding capacity, pruning content, moving one content type to another tool, and syncing collections from an external CMS. Each one is cheaper than a migration, and most can be done in days.
Workaround | What it fixes | Trade-off |
|---|---|---|
Upgrade or buy an add-on | Item and collection caps | Ongoing cost; doesn't fix relations |
Prune and merge content | Item caps | Takes editorial time; needs redirects |
Move one content type out | Caps and structure for that type | Two systems, possibly a subdomain |
Sync from a headless CMS | Editing, structure, reuse | Extra tool; synced items still live in Framer |
Migrate the whole site | Everything | A full rebuild |
Pruning deserves more credit than it gets. Merging thin posts into stronger ones and deleting outdated items usually helps rankings too, as long as every removed URL redirects to its closest match. For the sync option, read Framer with a headless CMS, and for loading content in bulk, see importing content into Framer CMS.
How do Framer CMS limits compare with Webflow's?
Framer and Webflow both cap CMS content by plan, so compare the current plan pages side by side rather than trusting a roundup. For reference, BRIX Templates' write-up of Webflow's May 2026 change reports that it merged the CMS and Business plans into a Premium plan with a 20,000-item limit; confirm that on Webflow's pricing page before you plan around it.
Webflow also has a more mature relational CMS and API, which is why our research found teams moving from Framer to Webflow mostly want relations and API access. Framer's advantage is speed of design and editing. For the full plan-by-plan comparison, see Webflow vs Framer pricing, and if you're coming from Webflow, Webflow CMS to Framer CMS shows how collections map across.
When are Framer CMS limits a reason to migrate?
Framer CMS limits are a reason to migrate when the problem is structure or long-term scale, not a temporary spike. If your content model needs real relations, if you're publishing thousands of programmatic pages, or if CMS content must feed apps and other tools, a workaround only delays the move.
- Stay if a plan upgrade or one add-on covers your 12-month projection.
- Sync if editing and structure are the pain, but the design workflow is working.
- Move one section if a single collection, such as docs, dwarfs the rest.
- Migrate if you need relations, scale and ownership together. Our Framer to Next.js migration guide covers the rebuild, and Framer alternatives compares destinations.
Whichever you choose, model the content properly first. A clean structure is what makes any CMS hold more with less. Our content modeling guide walks through structuring collections for a SaaS site.
