Framer Limitations
Every cap Framer puts on a site in 2026 — CMS collections, items, bandwidth, pages and editor seats — with the real numbers per plan, which ones you can pay to raise, and the one you cannot.
The short answer
Framer limits five things by plan — CMS collections, CMS items, bandwidth, pages and editors — and all five can be raised by paying more. The sixth limit cannot be raised at any price: Framer has no code export, so a published site cannot be taken off Framer's hosting. That is what turns the other five from inconveniences into a ceiling.
The oddest one is worth knowing before you upgrade: the Free plan includes 10 CMS collections, but Basic includes 2. Paying Framer $10/month can cost you eight collections.
The limits, plan by plan
| Plan | Price | Collections | Items | Bandwidth | Pages |
|---|---|---|---|---|---|
| Free | $0 | 10 | 1,000 | 1 GB | 30 |
| Basic | $10/mo | 2 | 1,000 | 50 GB | 30 |
| Pro | $30/mo | 10 | 2,500 | 100 GB | 150 |
| Enterprise | Custom | Custom | Custom | Custom | Custom |
Quoted from framer.com/pricing and verified 8 September 2026. Pro add-ons extend the ceiling to 40 collections, 40,000 items, 2 TB of bandwidth and 700 pages. Additional editors are $20/month each on Basic and Pro. Framer changes these — check before deciding.
1. CMS collections
The cap most people hit first, and the one with the strangest shape: the Free plan includes 10 collections, but Basic — the first paid tier — includes 2. Upgrading from Free to Basic can therefore cost you eight collections. Pro restores 10, and add-ons extend it to 40. A collection is a content type, so a site with blog posts, case studies, team members, testimonials and job listings is already over Basic by three.
2. CMS items
1,000 items on Free and Basic, 2,500 on Pro, up to 40,000 with paid add-ons. Generous for a marketing site, tight for a real publication or a product catalogue, and worth checking before you commit — migrating a large collection later is manual work.
3. Bandwidth
1 GB on Free, 50 GB on Basic, 100 GB on Pro, up to 2 TB with add-ons. This is the cap that fails at the worst possible moment, because it binds exactly when a launch goes well. A single image-heavy page and a good week on social can clear 50 GB.
4. Pages
30 on Free and Basic, 150 on Pro, up to 700 with add-ons. Rarely a problem for a marketing site; a hard ceiling for programmatic or location-based pages, where hundreds of URLs is the entire strategy.
5. Per-editor pricing
Editors beyond the owner are $20/month each on Basic and Pro. For a team of four that is $60/month on top of the site plan — often more than the hosting itself. This is a pricing limit rather than a technical one, but it changes the arithmetic of every comparison.
6. No code export
The structural one. Framer's own help documentation states that published sites cannot be exported as standalone HTML, because they depend on Framer's React runtime and backend services. There is no supported way to take the site with you, which means every other limit on this list is one you have to live with rather than leave.
Which limits converting actually removes
Converting a Framer site to code you host yourself removes the limits that come from living on Framer's plan. It does not remove the limits that come from Framer being a design tool. The honest split:
Gone once you own the code
- · Bandwidth caps — they become your host's terms
- · $20/month per additional editor
- · The page ceiling
- · CMS collection limits — FNJ's collections are unlimited on every plan
- · Not being able to leave at all
Still true after converting
- · You design in Framer; structural changes mean re-converting
- · Framer CMS data does not come across as dynamic content
- · FNJ's CMS is its own — you populate it, it is not an import
- · Hosting still costs whatever your host charges
The usual resolution is not to leave Framer but to stop hosting on it: keep the canvas, publish the output yourself, and let Follow Framer re-import the project on a schedule so the live site keeps tracking your design work.
Related: Framer alternatives compared · Framer vs owning your code · How to self-host a Framer site · What FNJ costs
FAQ
What are Framer's main limitations?
Six, in the order people hit them: CMS collections (10 on Free, 2 on Basic, 10 on Pro, 40 with add-ons), CMS items (1,000 on Free and Basic, 2,500 on Pro, 40,000 with add-ons), bandwidth (1 GB Free, 50 GB Basic, 100 GB Pro, 2 TB with add-ons), pages (30 Free and Basic, 150 Pro, 700 with add-ons), $20/month per additional editor, and no code export at all. The first five are caps you can pay to raise. The sixth is structural — there is no supported way to take a published Framer site with you.
Why does Framer's Basic plan have fewer CMS collections than the free plan?
It does, and it surprises almost everyone: Free includes 10 CMS collections while Basic, the first paid tier at $10/month, includes 2. Pro returns to 10. If you are on Free and using more than two collections, upgrading to Basic is a downgrade on that axis specifically — check your collection count before you pay.
What happens if I exceed Framer's bandwidth limit?
Bandwidth is metered per plan — 1 GB on Free, 50 GB on Basic, 100 GB on Pro — and exceeding it pushes you toward an add-on or a higher tier. It is the limit most likely to bite at the worst time, because traffic spikes are exactly when a site is doing its job. Hosting the site yourself moves this onto your host's terms instead: Cloudflare Pages does not meter bandwidth on its free plan, Vercel includes 100 GB, and Netlify 15 GB.
Can I get around Framer's CMS limits?
Partly. Add-ons raise collections to 40 and items to 40,000 on Pro, at additional cost. External sources can be synced in for some use cases. The cap itself cannot be removed while the site lives on Framer — the only way past it entirely is a site whose CMS is not Framer's, which means converting the site to code you own.
Can I export my Framer site to escape these limits?
Not using Framer itself — its documentation is explicit that published sites cannot be exported to standalone HTML. A converter works from your public published URL instead and returns a real Next.js project or a static bundle you host yourself. That removes the bandwidth cap (it becomes your host's), the per-editor charge, and the collection ceiling, because the site is no longer running on Framer's plan.
Does converting a Framer site remove every limitation?
No, and it is worth being precise about which ones it does not touch. Converting does not give you Framer's canvas — for structural redesign you go back to Framer and re-convert. It does not import Framer CMS collection data as dynamic content; components bound to a Framer collection come across without it, and FNJ's own CMS is a separate thing you populate yourself. What conversion removes is the hosting-side limits: bandwidth, editor seats, page count, collection ceilings, and the inability to leave.
Is Framer still worth using despite these limits?
For design speed, yes — few tools get you to a polished responsive site faster, and the caps above are irrelevant to a five-page marketing site run by one person. The limits matter when you scale along any axis: more content, more traffic, more editors, or more pages. A common answer is to keep designing in Framer and host the output yourself, which keeps the canvas and drops the ceilings.
Hit a limit? Take the site with you.
Paste your published Framer URL and get a real Next.js project or a clean static bundle you host yourself — no bandwidth cap from us, no per-editor charge, unlimited CMS collections. First conversion free.
Example: https://your-site.framer.website