Framer Pricing Tiers Explained

Framer Pricing Tiers Explained

Framer's pricing page is short, but choosing a plan for a company website is not as obvious as it looks. The plans differ less in price than in what they let your team do: how many pages and CMS items you can run, who can edit, whether you get staging and redirects, and what security your IT team will ask for.

This guide walks through each tier in plain language, explains what actually changes between them, and gives a simple way to pick the tier your company needs. We build Framer sites for venture-backed tech companies, so the advice is written for founders and marketing leads, not hobbyists.

One note before we start: Framer updates its plans and prices regularly. The figures below reflect framer.com/pricing at the time of writing (October 2026). Always check current pricing before you buy.

How Framer pricing is structured

Framer's paid plans are site plans. A plan attaches to a project (one website), and that plan sets the limits for that site: pages, CMS collections and items, bandwidth, analytics history and a handful of features. If you run a marketing site and a separate docs or campaign site as two projects, you are looking at two plans.

On top of the plan, you pay for people and for add-ons:

• Seats. Full editors cost extra per person per month. Framer also offers cheaper content-editor seats for people who only update CMS content and copy on the page. Viewers who only comment are free.

• Localization. Locales are an add-on, priced per locale.

• A/B testing. Framer's testing add-on is priced by event volume and is available on Pro.

• Advanced hosting. Running several sites under one domain with rewrites and custom headers is a paid add-on on Pro and included on Enterprise.

So the real question is never just "which plan". It is "which plan, how many seats and which add-ons".

Free: for testing, not for your company site

The Free plan lets you design and publish on a Framer subdomain with a small bandwidth allowance and a "Made in Framer" badge. It is useful for prototypes, internal concept pages or trying Framer before you commit.

It is not a plan for a company website. No custom domain means no brand credibility, and the limits are set for experiments. If a page is meant to be seen by customers or investors, it should not be on Free.

Basic: for a small, simple site

Basic is the entry plan for a site on your own domain. At the time of writing it lists 30 pages, 2 CMS collections and 1,000 CMS items, with a modest bandwidth allowance and 30 days of analytics.

It works for a pre-seed company with a homepage, a few product pages and a simple blog. It stops working quickly for most venture-backed teams, because the features you will want within months are Pro-only: site redirects, staging, site search and more CMS collections. Two collections run out fast once you have a blog, case studies, careers and integrations.

Pro: where most SaaS and startup websites live

Pro is the realistic tier for most of the companies we work with, from seed to Series C. At the time of writing it lists 150 pages, 10 CMS collections and 2,500 CMS items, more bandwidth, 90 days of analytics, and the features that make a site safe to run as a team:

• Staging and branching with previews, so changes can be reviewed before they go live.

• Site redirects, which you need the moment you rename a page or migrate from another platform.

• Site search for resource hubs and docs-style content.

• Access to add-ons such as A/B testing and advanced hosting.

For a primary marketing site plus a blog, customer stories, integrations directory and careers page, Pro is usually enough. The limits matter more than the price: if your content plan includes hundreds of programmatic pages or several thousand CMS items, check the numbers against your roadmap before you build.

Enterprise: for organizations with IT, security and scale needs

Enterprise is custom-priced and custom-scoped. Framer positions it around unlimited editors, custom limits, SSO and SCIM, role-based access, uptime guarantees, priority support and compliance documentation such as SOC 2 Type II and ISO 27001.

Companies usually reach Enterprise for one of three reasons: IT requires SSO and user provisioning, the site has outgrown Pro's limits, or many people across teams and regions need to edit safely. We cover that decision in detail in our comparison of Framer Pro vs Enterprise.

What actually changes between tiers

Beyond the monthly price, moving up a tier changes four things:

1. How much you can manage. Pages, CMS collections and items, bandwidth and locales all scale by tier. This decides how far your content strategy can grow on one site.

2. Who can collaborate, and with what permissions. Seats, content-editor roles and, on Enterprise, SSO, SCIM and finer role control.

3. How safely you can ship. Staging, branching and redirects are what let a marketing team change a live site without breaking it.

4. What you can measure and test. Analytics history, A/B testing and advanced hosting options grow with the tier.

Team seats: the cost people forget

Seats are where budgets drift. A common pattern: a team buys Pro, then adds full editor seats for everyone who might touch the site. Most of those people only change copy, publish a blog post or update a job listing.

A better setup is to separate roles:

• Full editors for the people who change layouts, components and structure. Usually 1 to 3 people, or your agency.

• Content editors for marketers, recruiters and product marketers who update CMS items and on-page text.

• Viewers for founders, sales and legal who review and comment.

This keeps costs down, and it protects the site. Fewer people with layout access means fewer accidental changes to components that the whole site depends on.

Choosing the right tier for your company

Do not start with "what is cheapest". Start with "what level of collaboration and complexity do we actually need". A practical way to decide:

• Pre-launch or validating an idea: Free for internal prototypes, Basic if you need a simple public site on your own domain.

• Seed to Series C, one main marketing site: Pro. Add content-editor seats for the marketing team, localization if you sell in several languages, and A/B testing once you have the traffic to make tests meaningful.

• Several sites or surfaces under one domain: Pro with advanced hosting, or Enterprise if security and seat counts also point that way.

• Multiple departments, regions or brands, plus IT requirements: Enterprise.

Before you commit, map your next 12 months of content against the plan limits. How many pages will the site have after the next product launch? How many blog posts, case studies and integration pages? Which languages? If the honest answer exceeds Pro's limits within a year, plan for it now instead of hitting a ceiling mid-quarter.

Common mistakes we see

• Launching on Basic to save a little. The first redirect, staging need or third CMS collection forces an upgrade anyway, often during a launch.

• Buying full seats for everyone. Content-editor seats cover most people at lower cost.

• Ignoring CMS limits during architecture. A site designed around many collections and thousands of items needs a plan that supports them. This is a design decision, not a billing detail.

• Jumping to Enterprise too early. If no one is asking for SSO and you are within Pro's limits, Pro plus a well-built system is usually the better use of budget.

The short version

Free is for testing. Basic is for very small sites. Pro is where most venture-backed SaaS, AI and fintech websites belong. Enterprise is for organizations where security, governance and many editors matter more than price. Pick the tier based on how many people need to build on your site and how much content it must carry in the next year, then add seats and add-ons deliberately. The plan is the smaller part of the cost. How well the site is structured decides whether your team can actually use it.

Allsite builds brands and Framer websites for venture-backed tech companies — designed to perform, and built for the teams that have to run them.