No — Framer does not support code export. There is no built-in way to download your site as HTML, React, or Next.js from the Framer editor. Published sites run on Framer's hosting, and that's the product's design. But your site isn't trapped: third-party converters can turn any published Framer site into static HTML or a Next.js project in about a minute.
Here's the full picture — what Framer officially offers, what it doesn't, and every real way to get your site out.
What Framer officially supports
- Publishing to Framer hosting — a
*.framer.websitesubdomain free, or your custom domain on a paid site plan. - Copy/paste of design elements — you can copy components between Framer projects, and paste into Framer from Figma.
- Framer API / plugins — for extending the editor, not for exporting sites.
What's not on that list: any "Export code," "Download ZIP," or "Eject to React" button. Searches like does Framer support HTML export or can you export Framer to code all land on the same answer — not natively.
Why not?
Hosting is Framer's revenue. An export button would let every finished site leave. That's a legitimate business choice — but it's also why "vendor lock-in" is the most common complaint from teams who outgrow the builder. If your site's future involves developers, custom features, or cost control, you eventually need an exit path.
The real export options
1. Converter → static HTML
Paste your published URL into a Framer to HTML converter. Good converters don't just save the page source — they strip Framer's runtime, self-host images as WebP, inline fonts, and run an SEO pass. The output is a fast static bundle (Lighthouse 90–100 Performance on desktop is typical) that hosts free on Netlify or Cloudflare Pages.
2. Converter → Next.js project
The Framer to Next.js export generates a real App Router codebase — one prerendered route per page with the runtime kept, so everything behaves exactly like the original. Right choice when a developer takes over.
3. Manual save (not recommended)
View Source → save each page by hand. Assets stay pointed at Framer's CDN, the heavy runtime stays, and multi-page sites are miserable to do this way. Fine for grabbing one page's markup; wrong for a migration.
Common follow-up questions
Is using a converter allowed? Yes, for your own site. Converters read the same public pages any visitor or search engine sees. Only convert sites you own or have permission to export.
Will I lose my design? No. The published page is your design — capture-based conversion preserves layout, fonts, and breakpoints exactly. Appear/scroll animations are rebuilt in CSS (HTML mode) or kept via the runtime (Next.js mode).
Will my SEO break? No — titles, descriptions, and URLs are preserved, and canonicals get repointed to your domain. Done right, scores go up because the runtime is gone. Verify it yourself with the PageSpeed comparison.
What about the "Made in Framer" badge? Removed automatically during conversion — details in the badge removal guide.
Bottom line
Framer doesn't export code, and probably never will. But a published Framer site is just rendered web pages — and those can be converted into files and code you own. Try it on your site free, and read the full export walkthrough if you want every step spelled out.