Framer to Code
Framer has no code export, so every route to real code is a third-party one. Here is the whole field — what each route actually hands you, what it quietly drops, and which of them are free.
The short answer
Framer cannot export code. Its help documentation is explicit: published sites depend on Framer's React runtime and backend services and cannot be exported as standalone HTML. There is no button on any plan.
So the real question is which third-party route you take, and they differ in one way that matters more than price: how much structure survives. An HTML converter gives you one flat generated file per page — correct on screen, unpleasant to edit. A React conversion gives you a project with named components per section that a developer can actually work in. Pick by what you intend to do next, not by what the site looks like on arrival.
Every route, compared
| Route | What you end up with | Free? |
|---|---|---|
| Framer's own export | Nothing | — |
| View source / DevTools | Fragments | Yes |
| HTML converters | A static HTML/CSS/JS bundle | Some, partly |
| React / Next.js conversion | A component project you can develop | No |
| Rebuild by hand | Exactly what you build | Your time |
1. Framer's own export
You end up with: Nothing · Free: —
Worth stating first because most searches start by looking for it: there isn't one. Framer's help documentation says published sites cannot be exported as standalone HTML, because they depend on Framer's React runtime and backend services. No button, no plan, no add-on. Every other route on this page exists because of that.
2. View source / DevTools
You end up with: Fragments · Free: Yes
Genuinely free, and genuinely limited. You can read the served markup and save individual assets, but a Framer page's styling is generated at runtime and split across hashed bundles, so what you copy renders as a broken approximation. Fine for lifting one SVG or checking a font stack. Not a way to get a site.
3. HTML converters
You end up with: A static HTML/CSS/JS bundle · Free: Some, partly
The largest category — tools that crawl your published URL and package the rendered output as static files. You get pages that look right and host anywhere. What you do not get is structure: it is one flat HTML file per page, so editing means hunting through generated markup, and anything driven by Framer's runtime has to be re-created or dropped. Good when the goal is hosting, not development.
4. React / Next.js conversion
You end up with: A component project you can develop · Free: No
The output is a real App Router project: each page split into named React component files taken from your Framer section names, composed by one view per page, with a prerender step that renders them back to the original DOM. The difference from an HTML bundle is what happens next — a developer can extend it, wire it to an API, or drop a section into another project. This is what FNJ's Next.js Converter produces.
5. Rebuild by hand
You end up with: Exactly what you build · Free: Your time
Always an option and sometimes the right one. If the Framer site is small, or if the design is about to change anyway, a developer rebuilding five pages properly will beat any conversion on code quality. It stops making sense the moment the site is large, finished, and merely in the wrong place.
“Framer to code, free” — the honest answer
This is the most-searched variant, so it deserves a straight answer rather than a landing page that says “free” and then asks for a card.
Free routes exist. DevTools costs nothing and gets you assets and fragments. Several HTML converters run free tiers, usually capped by page count or watermarked. If your site is small and you only need it hosted somewhere else, start there — you may not need to pay anyone.
FNJ is not free. There is no free tier and no pay-as-you-go as of September 2026; plans start at $15 a month at launch and include three conversions. Saying so here costs us the click from people who only wanted free, which is the point: they were never going to convert, and a bounced visit helps nobody.
Which one should you use
Use an HTML export if…
- · The goal is hosting it somewhere else, cheaply
- · Nobody is going to edit the code afterwards
- · You want the highest possible Lighthouse score
- · The site is finished and static
Use a React conversion if…
- · A developer will keep working on the site
- · You want named components, not one generated file
- · Animations must survive exactly as authored
- · The site needs to grow beyond what the canvas allows
Related: Framer to React components · Framer to HTML converter · Convert Framer to Next.js · How to export a Framer site · Framer's limits, plan by plan
FAQ
Can you export code from Framer?
Not from Framer itself. Framer's own help documentation states that published sites cannot be exported as standalone HTML, because they rely on Framer's React runtime and backend services. There is no export button on any plan, including Enterprise. Getting code out means using a third-party converter that works from your published public URL, or rebuilding the site by hand.
Is there a free Framer to code converter?
There are free routes, but they trade away something. Browser DevTools cost nothing and give you fragments — individual assets and unstyled markup — not a working site. Some HTML converters have free tiers that watermark, limit page count, or cap exports. FNJ is not one of them: it has no free tier as of September 2026 and starts at $15/month at launch. If free is the hard requirement, a limited HTML converter is the honest recommendation, not this one.
What is the difference between Framer to HTML and Framer to code?
How much structure survives. An HTML export gives you one flat file per page: it renders correctly and hosts anywhere, but the markup is machine-generated and unpleasant to edit. A code conversion gives you a project — named React components per section, a route per page, and a build you can run. Both are 'code'; only one is code you would willingly work in. Choose HTML for hosting and speed, a component project for development.
Does exported Framer code keep the animations?
It depends on the route. Conversions that keep Framer's runtime reproduce animations and interactions exactly as authored — measured element parity with the source is 100%. Routes that strip the runtime for speed re-create appear and scroll animations with lightweight CSS and IntersectionObserver, which covers most sites but can simplify runtime-only effects like custom cursors or WebGL.
Can I export a Framer site to React components?
Yes, through a converter — Framer offers no such export itself. FNJ's Next.js Converter emits one named component file per section, named from the section names you set in Framer, so a Hero section becomes Hero.tsx. That is the difference from an HTML export, which gives you a single generated file per page with no component boundaries at all.
Do I need my Framer login to get the code?
No, and you should be wary of any tool that asks. Conversion works from the site's public published URL — the same pages any visitor can load. No Framer account access, password, plugin or API key is required. If a page is publicly published, it can be converted.
Is it legal to export a Framer site to code?
For a site you own or are authorised to convert, yes — it is your design and your content. Converting someone else's site that you have no rights to is not something any of these tools make acceptable. FNJ's terms limit use to sites, designs and content you own or are authorised to convert, and that limit is the meaningful one.
What does a Framer code export cost?
It varies by route and by unit, and the unit matters more than the number. Some tools price per page, which scales badly on a large site. FNJ prices per site on a subscription — $15/month at launch for Starter, which includes three conversions a month, so a twenty-page site costs the same as a one-page one. There is no free tier and no pay-as-you-go.
Get your Framer site as real code
Paste your published Framer URL and get a Next.js project of named React components, or a clean static bundle. Priced per site, not per page, so a twenty-page site costs the same as a one-page one.
Example: https://your-site.framer.website