7 Framer CMS Limits to Check Before You Pick a Plan

Published 8 November 2026 · Last updated and fact-checked November 2026

Short answer: Framer CMS limits are plan caps, and CMS item pages do not count against the page limit. Framer's pricing gives Pro 2,500 CMS items and 10 collections, rising to 40,000 items and 40 collections with add-ons. The risk at scale is a separate, unpublished publishing size limit.

Some guides on this topic still tell you every blog post eats a page slot on your Framer plan. That was true once. Framer split the two limits in its October 2025 pricing change, and plenty of articles never caught up, which is why a head of marketing can read two answers on the same results page and trust neither.

The numbers on the pricing page are the easy part. The harder question is what happens when a site with thousands of pages hits a limit Framer has not put a number on. I run demanddesigner.com on Framer: on 8 November 2026 its sitemap listed 142 URLs, and 117 of them (57 blog posts and 60 project pages) came from CMS templates. So this guide separates what Framer publishes, what I have seen, and what nobody has measured in public.

Key takeaways

• CMS item pages do not count against the site page limit on current plans, per Framer's October 2025 pricing update.

• Pro starts at 2,500 CMS items, and add-ons cost $20 per 10,000 items up to 40,000, on Framer's pricing page.

• A 5,000-page content site fits on Pro with one item add-on, at about $50 a month on yearly billing.

• Framer stops updating a collection that passes its publishing size limit, and its help article gives no number for that limit.

• Google caps one sitemap at 50,000 URLs (Google Search Central), so Pro's 40,000-item maximum sits under it.

1. Site pages: CMS item pages do not use them

The site page limit covers pages you design, and it suits anyone comparing Framer plans by page count. Basic includes 30 and Pro includes 150, with add-ons at $20 per 100 up to 700. CMS item pages sit outside that count on current plans, according to Framer's pricing update.

• Basic: 30 site pages

• Pro: 150 site pages

• Add-on: $20 per 100 pages

• Pro maximum: 700 site pages

• Item pages: counted as CMS items

"In the new plans, these are now separate limits. So CMS item pages don’t count against this page limit," Framer wrote in its pricing update, published 9 October 2025.

The older answer still circulates for a reason. Before that change, the same post says, page limits "included both pages and CMS items combined". If your project's plan name contains ’24, Framer says you are on a legacy plan, and the old combined rule is the one to check against your own invoice.

Framer does not spell out how it counts the template itself, the page that generates every blog post. I treat each template as one designed page, because it is a page you lay out on the canvas. On my own site that makes the sums short: 60 project pages come from one template, so I budget one page slot, not 60.

Plan this limit around the pages a designer builds by hand: the homepage, service pages, landing pages for campaigns. A B2B site rarely needs 150 of those. If you are building location or industry pages, make them CMS items instead, and they leave this count altogether.

2. CMS items: the cap that scales with money

CMS items are the rows in your collections: every blog post, case study or location. This limit suits content-heavy sites deciding between Basic and Pro. Basic holds 1,000 and Pro holds 2,500, and Framer's pricing page sells more at $20 per 10,000 items, up to 40,000 on Pro.

• Basic: 1,000 CMS items

• Pro: 2,500 CMS items

• Add-on: $20 per 10,000 items

• Pro maximum: 40,000 CMS items

• Above that: Enterprise, custom limit

Framer's pricing page lists one number per plan and no per-collection figure, so I read the limit as a total across the project. I could not confirm on any Framer page whether translated content counts toward items, so ask Framer in writing if you run more than one language. My Framer localization cost breakdown covers the locale pricing.

"When you reach certain limits, we will ask you to upgrade your plan in Framer," the company said on its pricing page.

Add-ons look small next to the base price, which makes them easy to approve and easy to forget. The sensible check is the count you expect in 18 months, not today. A blog publishing 3 posts a week adds about 234 items in 18 months, so it stays inside Pro for years. A programmatic build with a page per city and service reaches 2,500 in its first import.

Count every collection when you add this up. Authors, categories and testimonials are items too, even when they never get their own URL. On a 5,000-page plan, leave room for those supporting rows before you decide one add-on is enough.

3. CMS collections: how many content types you can run

A Framer CMS collection is one content type, such as blog posts, authors or case studies. This limit suits teams with several content types, and it is usually the first one Basic hits. Basic includes 2 collections and Pro includes 10, with add-ons at $40 per 10 up to 40, on Framer's pricing page.

• Basic: 2 collections

• Pro: 10 collections

• Add-on: $40 per 10 collections

• Pro maximum: 40 collections

• Free plan: 10 collections, per Framer's FAQ

Two collections go fast. A blog with an authors collection uses both on Basic, and a case study collection pushes you to Pro on its own. That is the usual reason a small B2B site pays $30 rather than $10 a month on Framer's plans, and the full Framer plan comparison walks through the rest of that decision.

The one place you may want more collections than content types is the fix for item 4. Framer's own advice for an oversized collection is to split it, so a 20,000-item collection might become 4 of 5,000 items, organised by region or product line.

"Split one large collection into several smaller collections," Framer wrote in its help article on the warning.

Splitting has a cost that the help article does not mention. Each collection is a separate list on the canvas, so a single index page that shows everything gets harder to build, and your URL pattern may have to change. People judge a path through a site by the cues near it (Pirolli and Card, 1999), so split along lines a visitor would recognise, such as industry or location, and not by alphabet or import batch.

4. Publishing module size: the limit with no number

Framer has a publishing size limit for each collection, page and component, and it matters most to sites with long records or many media files. Its help article confirms the limit and publishes no figure. A collection can sit inside 40,000 items and still trigger it, because Framer ties the limit to size, and item count is only one cause.

• Warning text: "Module too large"

• Applies to: CMS collections, pages, components, site modules

• Your data: kept, still editable

• Published figure: none

• First fix: remove unused items and layers

This is the limit I would worry about on a big build, because you only learn where it is by reaching it.

"Framer will stop updating that item during publishing until its size is reduced," the Framer help center stated.

Read that sentence as a publishing risk. Your editor keeps working and the content is safe, so nobody on the marketing team sees a problem. The collection just stops refreshing on the live site. On a site where the blog is the point, that is a quiet failure, and it can sit there until someone notices a new post is missing.

Framer's own fixes point at unused items, large collections and heavy media, so 5,000 short location records and 5,000 long articles may be different loads. I cannot give you a safe item count, and I would be wary of anyone who does without showing a test. The test is cheap: import a sample at your real field count and body length, publish, and repeat at double the size until you see a warning or you pass your 18-month estimate.

Framer's help article lists the reductions in order: remove unused items and layers, split the collection, then compress uploaded images and videos or host video on YouTube or Vimeo. Large inline images in rich text are worth checking first, because they are the part of a record that an editor can add without thinking about weight.

5. Sitemap and publish time: what nobody has measured

Google allows 50,000 URLs in one sitemap, per Google Search Central, and Framer Pro's 40,000-item maximum sits under that. I found no published measurement of how long a Framer site with thousands of CMS pages takes to publish, from Framer or anyone else, so time a sample build yourself.

• Google sitemap cap: 50,000 URLs or 50MB

• Pro item maximum: 40,000

• Crawl budget guide starts at: 10,000+ pages changing daily

• Published publish-time data: none found

"All formats limit a single sitemap to 50MB (uncompressed) or 50,000 URLs," Google Search Central stated.

Crawl budget is a smaller worry than most programmatic-SEO threads suggest. Google's guide is aimed at sites with 1 million or more pages changing weekly, or 10,000 or more changing daily, and it says those figures "are a rough estimate". A 5,000-page site that changes monthly is outside that audience. Whether Google indexes those pages depends far more on whether each one says something the others do not.

Publish time matters for a different reason. In my own work on demanddesigner.com, a publish ships everything waiting on the main branch, so several people or sessions editing the site at once are all releasing together. I check the change list before every publish. On a site with thousands of items and a daily editorial schedule, ask how long the wait is and who owns the release.

Time three publishes on your sample build: one with no changes, one with a single item edited, and one after a bulk import. Write the numbers down before you commit, because that is the only figure you will get for your own site.

6. Bandwidth: the limit big content sites actually pay for

Framer bandwidth is the monthly data your visitors download, and it suits media-heavy or high-traffic sites to check this before item counts. Basic includes 50 GB and Pro includes 100 GB, with add-ons at $40 per 100 GB up to 2 TB, according to Framer's pricing page.

• Basic: 50 GB a month

• Pro: 100 GB a month

• Add-on: $40 per 100 GB

• Pro maximum: 2 TB a month

• Over the limit: one month's grace

"For other limits, like bandwidth, we allow you to exceed your limit for one month," Framer said on its pricing page.

Going from 100 GB to 2 TB adds $760 a month in add-ons at Framer's listed prices, by far the largest line a Pro site can run up. A CMS item add-on costs $20. So a heavy site can spend more on traffic than on content capacity, and it is the number to forecast from your current analytics rather than guess.

The fixes overlap with item 4. Compressed images and video hosted elsewhere reduce both the publishing weight and the monthly transfer, and they make pages load sooner too. In a controlled experiment, drops in performance and behavioural intentions from slow pages began to flatten at 4 seconds, meaning most of the damage was already done by then (Galletta et al., 2004).

"The tolerable waiting time for information retrieval is approximately 2 s," wrote Fiona Fui-Hoon Nah (*Behaviour and Information Technology*, 2004).

That study is old, so treat 2 seconds as a rough guide rather than a benchmark. It still sets the direction. Media choices that keep a CMS page light pay you back three ways: on the bill, at publish and in front of the visitor.

7. Code access to the CMS: the limit that breaks custom work

Framer code components and overrides that read the CMS collection variable are unsupported, which matters to any team planning custom filtering or computed lists. Framer's help article says the variable is no longer an Array and its properties are private and may change at any time.

• Applies to: code overrides and components built on Framer internals

• What changed: the collection variable is no longer an Array

• Status: unsupported, may change without notice

• Reason given: performance, stability, larger collections

• Check before build: any feature that reads every item in code

"The properties provided by the collection variable are a private implementation detail that may change at any time," Framer's help center stated.

This is the limit most agency estimates miss. A filter, a directory search or a calculator that reads across a collection is often sold as a small custom component. If it depends on those internals, it may break on a Framer update, and the vendor has told you so in advance. Framer's stated reason is fair enough: the change was made for performance, stability and larger collections. The cost lands on whoever built against the old behaviour.

The honest question for a developer quoting this work is simple: which supported route does this feature use, and what happens when Framer changes the internals? Bulk imports are where I would start on a large build, because I have used Framer's own agent tooling to write CMS items on my site.

I would put this ahead of raw item counts if your site's value depends on interaction rather than reading. A 40,000-item directory that cannot be searched the way your buyers need is a website with a storage problem.

Which limit will your site hit first?

Each Framer plan fails at a different limit, so match your site type before comparing prices. This matrix lists 5 common B2B builds with the Framer limit each is likely to reach first, based on the published caps in the 7 items. Read across your row, then run the worked cost for your size.

What does Framer Pro cost at your size?

Framer Pro costs $30 a month on yearly billing, and each add-on is priced in fixed blocks on Framer's pricing page. These 5 worked examples round each add-on up to a whole block, which is my reading of the listed prices. Confirm your total at checkout, because Framer lists add-ons in blocks only.

The $210 line breaks down as $30 for Pro, $40 for two item blocks, $40 for one collection block, $20 for one page block and $80 for two bandwidth blocks. Enterprise is the answer once any single number passes the Pro maximum, or if you need the custom limits, annual billing and dedicated support Framer reserves for that plan.

Frequently asked questions

These are the questions people type when they check Framer's limits against a real build: what counts as a page, whether large sites work, and what the free plan includes. Each answer uses Framer's published numbers as of November 2026, so check them against the pricing page before you buy.

Do CMS pages count toward the Framer page limit?

No, CMS item pages do not count toward the Framer page limit on current plans. Framer separated the two limits in October 2025, so items use the CMS item cap instead. Legacy plans with ’24 in the name combined them, so check your plan name inside the project first.

Can Framer handle 5,000 CMS pages?

Yes, on published limits, Framer can hold 5,000 CMS pages. Pro plus one item add-on allows 12,500 CMS items for about $50 a month on yearly billing. Framer publishes no size figure for that scale, so import a sample at your real record length and publish it first.

What is the Framer CMS collection limit?

Framer Basic includes 2 CMS collections and Pro includes 10. Pro can add collections at $40 per 10, up to 40 in total, and Enterprise limits are custom. Authors, categories and testimonials each use a collection, so count every content type you plan to run on the site.

What does "Module too large" mean in Framer?

"Module too large" means a CMS collection, page, component or site module has passed Framer's publishing size limit. Your content stays safe and editable, but Framer stops updating that item when you publish. Remove unused items, split the collection, or compress and move heavy media to fix it.

What is the Framer free plan CMS limit?

Framer's FAQ says projects on the Free plan include 10 CMS collections, 1,000 pages and 5 MB file uploads. Framer describes that plan as a way to explore the product, and it needs an upgrade before you can connect a custom domain to the site.

Who should set this up for your team?

Most B2B sites I build never reach these limits, and the ones that will should run a test build before signing anything. A sample import, three timed publishes and a written answer from Framer on anything unpublished will take a day or two. It costs far less than moving platforms after launch.

If you are still choosing a platform, my Framer vs Webflow comparison covers the wider trade-offs, and the WordPress to Framer migration guide covers the move itself. I build conversion-focused B2B sites on Framer at fixed prices from $3,250 to $14,999, and I run that sample test before I quote a large CMS build.

Start with the free Pipeline Leak Scorecard. It takes about 15 minutes, and it shows whether your site's problem is capacity at all.

Sources

Peer-reviewed research

• Galletta, D. F., Henry, R. M., McCoy, S., and Polak, P. (2004). Web site delays: How tolerant are users? Journal of the Association for Information Systems, 5(1).

• Nah, F. F.-H. (2004). A study on tolerable waiting time: How long are Web users willing to wait? Behaviour and Information Technology, 23(3).

• Pirolli, P., and Card, S. (1999). Information foraging. Psychological Review, 106(4).

Industry and vendor sources (not peer reviewed), read 8 November 2026

• Framer. Pricing. Plan limits and add-on prices, yearly billing.

• Framer. Simplified pricing, published 9 October 2025.

• Framer Help. How to fix the "Module too large" warning.

• Framer Help. Limitations when accessing the CMS with code.

• Google Search Central. Build and submit a sitemap.

• Google Search Central. Crawl budget management for large sites.