Code export · Framer
Framer code export, and where it stops being useful
Export policy checked on September 2026
What comes out
What Framer actually exports.
It's worth being exact here, because Framer's export policy has changed more than once and the honest 2026 answer is narrow: there is no way to take your site out as code. What you can extract are a few small pieces around the edges — none of which reconstitute the site as something you could host yourself.
No site codebase
Nothing comes out as a downloadable HTML/CSS/JS bundle or a React project — the site itself is not exportable as source.
CMS entries as CSV
You can export the content of a CMS collection as CSV — the data, not the pages that render it.
Your own code components
React code components you authored inside Framer can be exported individually — but you wrote those; the site around them can't leave.
Assets
Images and other assets can be downloaded. Useful for a rebuild, not a substitute for one.
How the export works: Framer sites publish on Framer's own managed hosting (custom domains are allowed, but the hosting stays managed). The help center is direct about why there's no export: "Framer does not offer HTML export for self-hosting. Sites built in Framer rely on platform-managed services that power performance, optimization, and publishing features behind the scenes."
The gap
What the export does not include.
Because nothing runnable comes out, the "gap" is the whole site. That's the honest shape of a host-only platform: it's excellent to build and publish on, and there is no supported door out to code you own.
The entire site as code
There is no static HTML/CSS/JS bundle and no React project to download. Every page, style and interaction lives inside Framer's managed system, so there's simply no source to hand to a developer.
BlockerSources: [1]No self-hostable output
You cannot take a Framer site off Framer's hosting. Framer attributes this to backend-dependent features — server-side rendering, image optimization, font subsetting, CDN — that only run on its infrastructure. Custom domain, yes; self-hosting, no.
BlockerSources: [1]"Code components" are inbound, not an export
This is the most common confusion. Framer's developer features — code components and code overrides — let you bring your own React into Framer. That's an extensibility feature pointing inward, not a way to get the finished site out. Having written code inside Framer doesn't mean you can export the site as code.
MajorThird-party extractors aren't official
Tools like "unframer" and various scrapers claim to pull a Framer site into code. None are official or vendor-supported, and results vary — treat anything they produce as an unverified rebuild starting point, not a sanctioned export.
Minor
The real question
Is the exported code maintainable?
Framer export:No code to assess
There's no exported code to assess, so the real question is portability, and there Framer is the sharp opposite of a platform like Webflow — which does export its front end. A Framer site is locked to Framer's hosting, and an engineer can't take it on because there's nothing to take. If you need to own or self-host the site, that's not a tweak to the export; it's a rebuild. The upside is that a rebuild in owned code (a static Next.js site, say) gives you exactly the self-hosting and control the platform withholds — and, unlike Framer, you'd be able to move it again later.
Your options
What to do with the export.
Three honest routes. The right one depends on how far the app has to go and who is going to own the code once it gets there.
- 01
Stay on Framer
Keep building and publishing on Framer. For a marketing or portfolio site, the managed hosting and design tooling are a genuine strength and the lock-in rarely bites.
- Right when it's a marketing/brand site and you're happy for Framer to host it.
- Wrong when you need to own the code, self-host, or fold the site into a larger app.
- 02
Rebuild the site in owned code
Rebuild the site as owned code — a static Next.js site is the usual target — using your exported CMS CSV and assets as the starting material.
- Right when you must self-host, own the source, or integrate the site with an app.
- 03
Move to a builder that does export
If you want to keep using a visual builder but need a real code export, a tool like Webflow exports its front end where Framer doesn't.
- Right when you value the no-code workflow but can't accept host-only lock-in.
The one sentence that settles the Framer export question
Framer's export policy has moved enough over the years that the only reliable answer is a dated one — so here is the current source, quoted rather than paraphrased. As of the help-center article last updated 7 August 2026, Framer states: "Framer does not offer HTML export for self-hosting. Sites built in Framer rely on platform-managed services that power performance, optimization, and publishing features behind the scenes." That's the whole answer. You can export CMS content and assets; you cannot export the site as code; and if you need to leave, you rebuild. We checked this on 2026-09-17 — if you're reading much later, re-verify against the same page.
- Code export
- None
- Self-host
- No
- CMS
- CSV only
- Leaving =
- Rebuild
Sources: [1]
FAQ
Questions people actually ask.
- Can I export my Framer website to HTML and self-host it?
- No. Framer's help center states directly that it does not offer HTML export for self-hosting — sites depend on platform-managed services (SSR, image optimization, CDN) that only run on Framer's own hosting. You can use a custom domain, but the site stays hosted by Framer. This was true when we checked on 2026-09-17.
- Does Framer let you export React or source code?
- Not the site. You can export individual React code components that you authored inside Framer, but there's no export that turns the finished site into a React project or a source bundle. The building blocks you brought in can come out; the assembled site can't.
- What's the difference between Framer code components and a code export?
- Direction. Code components and code overrides are an inbound feature — they let you push your own React into Framer to extend it. A code export would be outbound: taking the whole site out as source. Framer offers the former and not the latter, which is why "Framer supports code" gets misread as "Framer exports code."
- Can I move my Framer site off Framer hosting?
- Not as-is. Because there's no source or static export, moving off Framer means rebuilding the site elsewhere — commonly as a static Next.js site you host yourself — using your exported CMS content and assets. It's a rebuild, not a migration of files.
Every builder, one table
Code export across the hub, at a glance.
The same status table on every export page. “Exports” means real, usable source comes out; “partial” means a major layer is missing; “none” means no source export at all. The nuance is on each page.
| Platform | Code export | What you get |
|---|---|---|
| Lovable | Exports code | React repo via GitHub |
| Base44 | Partial export | Front end; backend locked |
| Webflow | Partial export | Front end only, no CMS |
| FlutterFlow | Exports code | Dart / Flutter source |
| FramerThis page | No code export | Host-only, no export |
| Bolt.new | Exports code | Project files / GitHub |
| Bubble | No code export | No source export |
| Replit | Exports code | Full code, you own it |
| Softr | No code export | No code (data only) |
| Glide | No code export | No code (data only) |
| Adalo | No code export | No source export |
| Retool | Partial export | Self-host, not source |
| Xano | Partial export | API portable, no export |
Sources
Every claim, traced to a primary source.
The numbered references in the body link here. We cite vendor docs, pricing pages, changelogs and named reporting — dated where the document is dated, so the page can be re-audited each quarter.
- [01]Can I export my website to HTML and self-host it?
Framer Help Center · 2026-08-07framer.com
- [02]How do I export my Webflow site code? (contrast — Webflow does export its front end)
Webflow Help Centerhelp.webflow.com
Own the Framer app outright?
We’ll map the route to code you actually own.
Book a call with Jackson, our Growth Partner — he’ll walk your export or app, the gaps that matter, and a fixed-price plan to get it production-ready, live on your screen. Or get an instant estimate first.
Or see fixed-price migration packages and how we work.