Framer limitations: what it can't do (2026)

Framer’s real limits are commerce, app logic, code export, and self-hosting. Plus two features gated behind plans: redirects need Pro, and localization is a paid add-on. Each limit has a workaround, and none of them matter for most marketing sites.

This is the honest list — what Framer cannot do in 2026, why, and what to do instead.

1. No native checkout

Framer has no built-in store. There is no cart, no product inventory, no order management. Selling means embedding a third-party checkout — Shopify’s Buy Button, Stripe, Gumroad, or a similar service.

When it matters: if your business is a shop. A florist selling arrangements at volume, a brand with a catalog, anyone who needs inventory and shipping logic should start on Shopify or Webflow. The Framer vs Shopify comparison covers the split.

When it doesn’t: a consultant selling a template or two, or a studio selling an occasional print run. An embedded checkout handles that fine.

2. No app logic or memberships

Framer builds websites, not applications. There is no server-side code, no database, no user accounts. Password protection exists for whole sites, but member areas, gated content, and logins need an external service.

When it matters: SaaS products, course platforms with accounts, anything with “log in” as a core feature. These need real application platforms, not website builders.

When it doesn’t: every marketing site. Most “we need logins” projects turn out to need a client portal somewhere else and a website that links to it.

3. No code export or self-hosting

Framer sites run on Framer’s hosting. There is no export-to-HTML, no bring-your-own-server, no headless option. Your design lives in the workspace; the site lives on Framer’s CDN.

When it matters: teams with hosting mandates, data-residency requirements, or a long-term ownership plan. Enterprise plans add guarantees, but the hosting stays Framer’s.

When it doesn’t: the vast majority of sites. Managed hosting is why there is nothing to maintain — no servers, no security patches, no backups.

4. CMS limits are real

The lower plans are capped: 2 CMS collections on Basic, 10 on Pro, with 1,000 and 2,500 CMS items respectively. Overages scale up to 40 collections and 40,000 items — but the architecture stays flat.

When it matters: large content operations with rich relationships — hundreds of projects linked to materials, publications, and people. That data wants a deeper CMS, like Webflow or Sanity.

When it doesn’t: most sites. A restaurant’s menu, a studio’s projects, a practice’s services — all fit comfortably.

5. Localization is a paid add-on

Multi-language support exists, but it costs extra: $20 per locale, up to 20 locales, with AI-assisted translation. There is a free locale to try. For a bilingual business site, that is a modest line item — but it is not included.

When it matters: sites that genuinely run in several languages from day one. Price the add-on into the plan.

When it doesn’t: single-language sites — which is most of them. Do not pay for locales you will not maintain.

6. Redirects and staging are Pro features

Two professional necessities sit behind the $30/month plan:

• Site redirects — the manual list you need when replacing an existing site. (Framer does handle 301s automatically when you rename a page inside Framer.)
• Staging — test changes before they go live.

When it matters: every migration. If you are moving a site to Framer, budget Pro for the redirects alone.

When it doesn’t: a brand-new site with nothing to redirect.

What is not a limitation

To keep this fair, three things people assume are limits — and are not:

• SEO. Framer ships metadata controls, CMS variables, auto sitemaps, redirects, JSON-LD support, and an AI visibility scanner. The full story is in is Framer good for SEO.
• Performance. Global CDN, WebP images, and built-in optimization. Pages are fast by default.
• Animation. Motion is a strength, not a workaround.

The bottom line

Framer’s limits are clear. There is no checkout, no app logic, and no code export. The CMS is capped, translations cost extra, and redirects sit behind the Pro plan. If none of that touches your project, the limits are trivia. If one does, they are a dealbreaker. The honest move is a different platform — not a workaround. Best Framer alternatives covers where to go.