What Framer gates behind which plan, and why the free one has higher limits
Framer's free plan carries 10 CMS collections and 1,000 pages; its cheapest paid plan carries 2 and 30. Here is the full control table from Framer's own pricing page, including the three rows that decide whether a technical project is possible at all.
Framer's free plan gives you 10 CMS collections and 1,000 pages. Its cheapest paid plan gives you 2 collections and 30 pages. Paying, in other words, reduces four of your limits until you reach Pro, and the reason is that the free plan is built for designing and for selling templates rather than for publishing a site, so it withholds the custom domain instead of the capacity.
That inversion is a fair warning about the rest of the table. Framer's controls are not distributed the way you would guess, several of the ones that decide a technical project sit on Pro, and the comparison content that asserts the gates mostly does not cite Framer for them. So here is the table from Framer's own pricing page, read on 16 September 2026, with prices deliberately left out.
What sits on which plan
| Control | Free | Basic | Pro |
|---|---|---|---|
| Custom domain | No | Yes | Yes |
| Site pages | 1,000 | 30 | 700 with add-ons |
| CMS collections | 10 | 2 | 10, or 40 with add-ons |
| CMS items | Not published | 1,000 | 40,000 with add-ons |
| Site redirects | No | No | Yes |
Static and .well-known files | No | No | Yes, 50 via Advanced hosting |
| Custom security headers | No | No | Permissions-Policy, Referrer-Policy, X-Frame-Options, via add-on |
| Rewrites | No | No | 6 via Advanced hosting |
| Staging environment | No | No | Yes |
| Branching with previews | No | No | Yes |
| Bandwidth | 1 GB | 50 GB | 100 GB, 2 TB with add-ons |
The three rows that decide a technical project
Redirects come first, because without them a migration cannot preserve anything. That row alone is the subject of Framer vs Webflow redirects, where the behaviour differs as much as the availability.
Static files come second, because .well-known is where domain verification, payment provider files and several authentication flows live. A site that cannot serve that directory cannot complete some integrations at all, and the capability sits behind Pro and then behind an add-on on top of it, capped at 50 files.
Security headers come third, and they are the row we would check before agreeing to anything. Permissions-Policy in particular is easy to set once and forget, and it silently disables browser features on your own pages. We have had camera=() on our own sites break a screen recorder's camera bubble, which took longer to diagnose than it should have because nothing errors: the feature simply is not there. On Framer that header is editable only on Pro with the Advanced hosting add-on, so on Basic you inherit whatever the platform sets.
How to read any plan table, including this one
Two habits are worth more than memorising a table that will change. Ask which plan a feature sits on rather than whether the platform has it, because every comparison article answers the second question and the first is the one that costs money. And write the figure into the project brief with the date you read it, because both vendors revise these: Webflow replaced its entire plan lineup on 13 May 2026, which is covered in Webflow's May 2026 plan changes, and it invalidated three posts on this site that had quoted the old one.
