Framer export
Example: https://your-site.framer.websiteYour published site’s address — the one visitors see. A custom domain works too.
Discover linked and sitemap pages across the whole site, including sites with more than 500 routes.
Framer has no built-in export or download button for a published site. Its self-hosting help article says it does not offer HTML export, even though a separate data-portability article says the published files can be moved to any host. So getting a Framer site out means going around Framer: convert the published URL, use a marketplace plugin, save pages by hand, or rebuild. The fastest path is our Framer to HTML converter: paste your published URL and get static HTML, a Next.js project or an Astro project.
Not with a Framer feature. Two of its help articles read differently, so here is what each says.
Self-hosting
Framer's help article Can I export my website to HTML and self-host it? says Framer “does not offer HTML export for self-hosting” and has no way to export a published site as HTML files or a static bundle. Its reason is that published sites rely on services that run on Framer's hosting: page pre-rendering, image optimization, font subsetting, server-side rendering, and content delivery and caching. None of the plans on Framer's pricing page lists a code, HTML or site export.
Data portability
A second article, Porting your data from Framer, written around the EU Data Act, reads differently. It says every Framer site is published as standard HTML, CSS, JavaScript and static assets, and that you can download those files at any time and move them to any hosting provider. It doesn't name a button, menu item or plugin that does this, and the self-hosting article says the opposite. On CMS content it is specific: collections can be exported with plugins as CSV or JSON.
So the accurate answer is that Framer has no built-in export or download feature, although its data-portability article says the published files can be moved. Getting them out in practice means a third-party tool. Framer's own marketplace now lists export plugins, and converters like this one read the same public HTML a visitor's browser already receives, with no access to the Framer project needed. Either way, it only makes sense for a site you own or are authorized to convert, not for reproducing someone else's.
Plugin details are from their Framer Marketplace listings in November 2026; check each listing for current pricing.
Swipe the table to compare →
| Option | Works from | What you get | Best for | Link |
|---|---|---|---|---|
| Framer to HTML converter | The public URL | Static HTML files for the whole site | Hosting it yourself with no build step | Open tool |
| Framer to Next.js | The public URL | An App Router project of named section components | Developers who will keep building | Open tool |
| Framer to Astro | The public URL | An Astro project, one component per section | A static site in an Astro codebase | Open tool |
| Framer marketplace export plugin | The project, open in Framer | Depends on the plugin: a static copy, a Next.js copy or React components | Exporting from inside the editor | Compare |
| Saving pages by hand | Your browser | One HTML file per page, still loading from Framer | One page's markup, for reference | — |
| Manual rebuild | Your design | Exactly the code you write | Full redesign control, slowest | — |
Option 1
Option 2
Option 3
./about-us with no file extension, so saved pages don't open each other until you fix the links or host them at matching pathsOption 4
Swipe the table to compare →
| Output | What you hold | How you work on it | Where it comes from |
|---|---|---|---|
| Static HTML | One .html file per page, plus images and other assets | Any text editor; nothing to build | FNJ's HTML export, Full Site Export's static copy, Framer to Code's ZIP, other URL converters |
| Next.js project | An App Router project, one route per page | React and the Next.js toolchain; FNJ splits each page into named section components (Hero.tsx, Pricing.tsx) | FNJ's Next.js export, Full Site Export's Next.js copy |
| Astro project | One .astro file per route, one component per section | Astro; npm run build writes static HTML | FNJ's Astro export |
| React components | Chosen components as React files, for an app you already have | Your own React codebase | React Export with the unframer CLI; Full Site Export's readable rebuild for whole pages |
Underneath every format sits one trade. An export can keep Framer's runtime, so the page renders exactly and every interaction works, but most of the original JavaScript still loads. Or it can replace the runtime with code of its own, which reads more like a developer wrote it but means effects that depended on the runtime have to be rebuilt, and the result is close to the original rather than identical. All three FNJ outputs keep the runtime and trim what sits around it: trackers removed, images re-encoded as WebP. FNJ has no runtime-free mode. More on the formats: Framer to HTML, Framer to Next.js, Framer to Astro and Framer to React.
All three FNJ exports keep Framer's own runtime, which is why animations behave as authored, and also why none of them is a runtime-free rebuild. Only publicly published pages can be exported.
Swipe the table to compare →
| Part of your site | HTML export | Next.js export | Astro export |
|---|---|---|---|
| Layout and breakpoints | Kept | Kept | Kept |
| Animations and interactions | Kept, via Framer's runtime | Kept, via Framer's runtime | Kept, via Framer's runtime |
| Framer's runtime and fonts | Still load from Framer's CDN | Still load from Framer's CDN | Still load from Framer's CDN |
| Every page and its URL | Kept | Kept, one route per page | Kept, one .astro file per route |
| CMS item pages | Kept as pages, as of the export | Kept as pages, as of the export | Kept as pages, as of the export |
| Titles, descriptions and Open Graph tags | Kept, plus an SEO pass | Kept, plus an SEO pass | Kept, plus an SEO pass |
| Images | Copied in as WebP | Copied in as WebP | Copied in as WebP |
| Forms | Shown; repoint submissions | Shown; repoint submissions | Shown; repoint submissions |
| Trackers | Removed | Removed | Removed |
| “Made in Framer” badge | Removed | Removed | Removed |
| What you edit afterwards | Static HTML files | Named React components, one per section | Astro components, one per section |
| Password-protected pages | Not exported | Not exported | Not exported |
A converter reads the published site, so each CMS item page, such as a blog post or a project, comes across as an ordinary page, as it was when you exported. Items you add or edit in Framer afterwards don't appear until you export again, and nothing stays connected to Framer's CMS. To move the content itself, Framer's porting article points to plugins that export collections as CSV or JSON.
Framer's built-in form handling stays with Framer. The form still shows, but point its submissions at a service such as Formspree or Tally after you move.
Appear and scroll effects, hover states and other interactions work because the runtime still loads from Framer's CDN. That is also why the Framer project should stay published, and why the export is not a speed rebuild on its own.
FNJ keeps your routes, titles and descriptions and points canonicals at your domain. Keep every URL the same, add 301 redirects for any that change, and compare the old and new pages in PageSpeed Insights rather than assuming a speed gain.
Export before you cancel a paid Framer plan, so the export captures the live site.
Step 1
Only public pages can be exported. Confirm the site — one you own or are authorized to convert — loads without login on framer.website or your custom domain.
Step 2
HTML = plain files, no build step. Next.js = a React project of named section components. Astro = a static site in an Astro codebase.
Step 3
Paste the URL into the converter and pick an output. It finds the pages from the site's links and sitemap, and says so if it can't find them all.
Step 4
Download the files, or deploy in one click to your own Cloudflare Pages or Vercel account. Keep the Framer project published, since its runtime and fonts still load from Framer, and point DNS at the new host when you’re ready.
Convert your entire Framer website into code you own for one payment, with no subscription. The AI website builder has its own plans.
Builder
Freelancers and creators
$25per month
AI website builder · 60 credits a month
FNJ Lifetime
Convert Framer sites into code you own and host.
Was $79$49once
Framer converter · flash-sale price
2,100+ sites converted by 740+ people. Not for you? Ask for a refund within 30 days.
Agency
Agencies building for clients
$99per month
AI website builder · 250 credits a month
Site Pack · $29 once
50 credits, used as you build. Enough for about 3 complete sites. Up to 10 pages per site. For the AI builder, with no subscription.
Need more? 20 credits for $10
Top-up credits work on any builder plan. A complete 5-page site over 10 prompts is about 15 credits.
Prices in USD. Builder credits are used as you build: one prompt is 1 credit, and each page the AI builds is 1 more. Conversions and the AI builder are separate products.
If something doesn't work as expected, let us know. A person answers.
Not with a built-in Framer feature. Framer's help article on self-hosting says it does not offer HTML export for self-hosting, and no plan on its pricing page lists an export. A separate data-portability article says the published files can be downloaded and moved to any host, but it names no feature that does it. In practice you use a third-party route: a converter that reads the published URL, an export plugin from Framer's marketplace, or a rebuild.
Yes, for a site you own or are authorized to convert, but through a third-party tool rather than Framer. A published Framer page is HTML, CSS and JavaScript that every visitor's browser downloads, so a converter can package the whole site as static HTML or as a Next.js or Astro project, and some marketplace plugins export it from inside the editor. Saving pages from your browser gets you single pages that still load their images and scripts from Framer's servers.
No. None of the plans on Framer's pricing page lists code, HTML or site export. Paying for a plan gets you things like a custom domain, not a download of your site.
Paste the published URL into a converter and download the result or deploy it. With FNJ most sites convert in under a minute (large multi-page sites take a few), and you can download the files or deploy them in one click to your own Cloudflare Pages or Vercel account. No Framer login or plugin is needed.
Choose HTML for plain files with no build step that any static host can serve. Choose Next.js when a developer will keep building: you get an App Router project with each page split into named React components that render the original page exactly. Both keep Framer's runtime, so animations behave as authored either way, and both start from the same published URL.
It comes across as a snapshot. Each published CMS item page, such as a blog post or project page, is exported as an ordinary page as it was at that moment, with no live link to Framer's CMS, so items you add later need a new export. Framer's data-portability article says the CMS content itself can be exported with plugins as CSV or JSON.
They still render, but submissions need a new backend. Framer's built-in form handling stays with Framer, so point each form at a service such as Formspree or Tally after you move the site.
Yes, if you export with FNJ. Every FNJ output keeps Framer's runtime, which runs the animations and interactions, and it and the fonts still load from Framer's CDN, so the Framer project should stay published. If you need no dependency on Framer's servers at all, FNJ is not the right tool; a rebuild is.
Not with FNJ. FNJ Lifetime Unlimited is one payment of $49 for unlimited Framer site conversions and every shipped feature, through November 30, 2026. The exported code can be hosted anywhere.
This is meant for sites you own or are otherwise authorized to convert, not for reproducing someone else's site without permission. You're responsible for having the rights to the content and design you convert.
No. This is an independent, third-party tool and isn't affiliated with, endorsed by, or sponsored by Framer.
AI website builder
FNJ also makes an AI website builder. Describe the site and show it one you like: it designs every page for desktop, tablet and phone on a canvas you can edit, then gives you the code, a Next.js project or static HTML, to host wherever you want.
See the AI website builder →
Paste your published Framer URL to generate a production-ready project in minutes.
Example: https://your-site.framer.website— your published site’s address. A custom domain works too.