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.
Online tool to convert your Framer website to clean static HTML. No plugin, no Framer login, one payment and no subscription.
What is a Framer to HTML converter?
A Framer to HTML converter turns a live Framer website into standard web files — HTML pages, CSS, scripts, and images — so you can self-host outside Framer. Officially, Framer does not support HTML export for self-hosting. Converters work by reading the same public HTML visitors already receive, then packaging and optimizing it for portable hosting.
People search for this tool when they want to export a Framer site to HTML, cut hosting costs, remove vendor lock-in, improve Core Web Vitals, or hand a client a site they fully own.
Export or convert Framer to HTML?
For a Framer site, the two words describe the same job. Framer has no built-in export: its help center says it “does not provide a way to export published sites as HTML files or static website bundles.” So exporting Framer to HTML always means converting the published pages into files.
You can do that three ways: save pages one at a time from your browser, run a third-party export plugin from Framer's marketplace inside the editor, or paste the published URL into a converter like this one, with no plugin and no Framer login. A converter reads the live site, so you get the pages visitors see, not an editable Framer project.
Is it free? Not here: converting is paid. FNJ Lifetime Unlimited is one payment of $49 for unlimited Framer site conversions and every shipped feature, through November 30, 2026.Saving pages from your browser costs nothing but often leaves images on Framer's servers, and some marketplace plugins offer a few free exports before a paid license. Hosting the result can be free on a static host.
Why use this Framer to HTML converter?
Built for the exact keyword job. Paste URL → get static HTML. No generic multi-builder detour if all you need is Framer → HTML.
Lighter pages.Images are re-encoded to WebP and trackers removed; Framer’s runtime is kept, so results depend on the site. Measure yours before and after with Google's PageSpeed Insights.
Own the files forever.ZIP of HTML/CSS/assets — host on Cloudflare Pages, where requests to static files are free and unlimited, free plan included. Your domain leaves Framer hosting; keep the Framer project published, since the runtime and fonts still load from Framer's servers. See how to self-host a Framer site.
SEO pass included. Meta tags preserved, canonicals rewritten for your deploy domain, missing image alt attributes added, badge removed, lang and viewport ensured.
Edit after export. Update text, links, and images in the exported files without going back to Framer.
How to convert Framer to HTML (4 steps)
This is the full workflow for anyone searching how to export Framer to HTML or how to use a Framer to HTML converter:
1Publish your Framer site
Your site must be live on a public URL (your-site.framer.website or a custom domain). Private drafts cannot be converted.
2Paste the URL into the Framer to HTML converter
Drop the published URL into the form and start conversion. No Framer plugin, no code, no API key.
3Optimizer builds clean static HTML
Every page is captured, images become self-hosted WebP, trackers and the badge are removed, SEO tags are cleaned. Framer’s runtime is kept, loading from Framer’s servers with your fonts, so animations still play.
4Download the ZIP or deploy live
Get a static HTML bundle, or deploy to your own Cloudflare Pages or Vercel account. Edit the exported files whenever you need to update the site.
How to move from Framer to HTML without losing rankings
Converting is step one. Rankings are kept or lost in the move, and the rule is simple: every URL that ranks today must still answer, at the same address or through a permanent redirect. Do it in this order.
Open /sitemap.xml on your live site (Framer generates it automatically) and note the pages that get search traffic in Search Console's Performance report. That list is what you check against after launch.
2
Convert without changing a path
The converter keeps your URL structure, titles and meta descriptions, and points each canonical tag at whichever domain serves the files instead of your Framer address.
3
Deploy to a preview address first
Use one-click deploy to your own Cloudflare Pages or Vercel account, or upload the files to any static host (hosts compared). Open each URL on your list directly, not only by clicking through, and check images, menus and animations on phone and desktop.
4
Repoint your forms
Framer’s form backend stays with Framer. Connect each form to a service such as Formspree or Tally and send a test submission from the preview.
5
Lower the DNS TTL, then move the domain
Before the switch, lower the TTL on your domain’s DNS records (Google suggests a few hours) so the change reaches visitors quickly. Then add the domain to your new host and set the records it gives you. Keep the Framer project published: the pages still load Framer’s runtime and fonts from Framer’s servers.
6
Redirect anything that changed
Renamed a page or changed domain? Add a permanent (301 or 308) redirect from each old URL to its new one and keep it for at least a year, as Google advises. For a new domain, also use Search Console’s Change of Address tool.
7
Submit the sitemap and watch Search Console
Make sure the live site has a /sitemap.xml listing URLs on your real domain, not the host’s preview address; add or edit one if it doesn’t. Submit it in Search Console and check a few key pages with the URL Inspection tool. Google says a short dip in crawling right after a move is normal.
Framer to HTML launch checklist
Before you switch the domain
The Framer site is published and every page you need is public
Every URL on your list is in the export, nested pages included
Each URL loads directly on the preview, not only through links
Images, fonts, menus and animations match the original on phone and desktop
Every form sends to its new service
Each page keeps its title, meta description and canonical tag
Any URL that changed has a 301 redirect ready
After launch
Your domain loads over HTTPS from the new host, and its www and non-www versions end on one address
Canonical tags match the exact address served, trailing slash included
/sitemap.xml lists your real domain and is submitted in Search Console
The host’s default address redirects to your domain or stays out of search
Key pages pass URL Inspection in Search Console
PageSpeed Insights run on the old and new URL on the same day
The Framer project is still published
Export Framer to HTML — what people mean by related searches
Search intent
What this converter does
framer to html converter
Primary tool on this page — URL → HTML ZIP
export framer to html
Full multi-page export with assets, not a single “Save as”
export vs convert framer
The same job for Framer, which has no built-in export — explained above
convert framer website to html
Discovers all routes and preserves path structure
free framer html export
Conversion needs a plan; the exported HTML hosts free on a static host
Deploy to your own Cloudflare Pages or Vercel account
Made in Framer badge removed
Editable exported HTML files
Limitations (honest)
Public pages only. Password-protected or draft pages cannot be converted.
Static snapshot. Server-side Framer CMS updates after export require a new conversion or changes to the exported HTML files.
Framer’s runtime stays. Animations and interactions run on Framer’s own runtime, loaded from Framer’s servers along with your fonts, so the page’s JavaScript is no lighter than the original and the Framer project should stay published. Want editable React components instead? Use Next.js export.
Forms need a new backend. Framer's form backend stays with Framer; point each form at a service such as Formspree or Tally.
Own sites only. Only convert websites you own or have permission to export.
Framer to HTML troubleshooting
Problem
Likely cause
Fix
A page is missing from the export
It’s unpublished or password-protected, or it’s in neither Framer’s sitemap nor any link on a published page
Publish it, link it from your navigation or footer, and convert again
A nested page 404s when opened directly
The files were uploaded one folder too deep, or the host isn’t serving each folder’s index.html
Make the folder that holds the homepage’s index.html the site root, then test direct visits on the preview
Animations, interactions or fonts are missing
Requests to Framer’s servers are blocked, or the Framer project was unpublished
Keep the project published, and check the browser’s Network tab for failed requests
A form doesn’t send
Framer’s form backend stays with Framer
Point the form at Formspree, Tally or a similar service, and test it
New CMS items in Framer don’t appear
The export is a snapshot of the published site
Convert again after publishing, or edit the exported files
Search results still show the old address
Google hasn’t recrawled the moved pages yet
Check the canonical on the live page, submit the sitemap, and inspect key URLs in Search Console
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.
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
250 credits every month
About 16 complete sites a month
Up to 20 pages per site
AI designs every page
Desktop, tablet and mobile layouts
Edit by prompt or by hand on the canvas
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.
A Framer to HTML converter is a tool that takes a published Framer website URL and turns it into portable static HTML, CSS, JavaScript, and image files you can host anywhere. Framer does not offer official HTML export, so a converter is how you leave Framer hosting without rebuilding the site by hand.
Can you export HTML from Framer?
Not with a built-in feature. Framer’s help center says it “does not provide a way to export published sites as HTML files or static website bundles.” Third-party export plugins exist in Framer’s marketplace, and this converter works from your published URL instead, with no plugin and no Framer login.
Export or convert: what’s the difference for a Framer site?
For Framer they describe the same job. Because Framer has no built-in export, exporting a Framer site to HTML means converting its published pages into files, with a converter like this one or a marketplace plugin. A converter reads the published site, so you get the pages visitors see, not an editable Framer project.
Is this Framer to HTML converter free?
No. FNJ Lifetime Unlimited is one payment of $49 for unlimited Framer site conversions and every shipped feature, through November 30, 2026. There is no per-page export fee.
Is there a free way to convert Framer to HTML?
Only partly. Saving pages from your browser costs nothing, but it works one page at a time and often leaves images on Framer’s servers, and some Framer marketplace export plugins offer a few free exports before a paid license. Hosting the result can be free: Cloudflare Pages’ free plan serves requests to static files free and unlimited.
How does the Framer to HTML converter work?
Paste your public Framer URL. The tool discovers every page, captures the server-rendered HTML, re-encodes images to self-hosted WebP, removes trackers and the Made in Framer badge, runs an SEO pass, and returns a downloadable ZIP (or one-click deploy). Framer’s runtime is kept, so animations and interactions work as designed; it still loads from Framer’s servers along with your fonts, so keep the Framer project published.
Do my animations and interactions survive the HTML export?
Yes. The HTML export keeps Framer’s runtime, loaded from Framer’s servers, so appear, scroll and hover animations play as designed. Keep the Framer project published for that reason. Want the site as editable React components instead? Use the Next.js Converter.
Where can I host the exported HTML?
Anywhere that serves static files: Cloudflare Pages, Vercel, Netlify, GitHub Pages, Amazon S3, or classic shared hosting. One-click deploy goes to your own Cloudflare Pages or Vercel account (Vercel’s free Hobby plan is for personal, non-commercial use only); for any other host, upload the downloaded files. No build step and no Node server required.
Will a Framer to HTML converter make my site faster?
Sometimes. The HTML export keeps Framer’s runtime, so most of the original JavaScript still loads; the gains come from re-encoding images to self-hosted WebP and removing trackers. How much depends on the site. Compare your own site before and after in Google's PageSpeed Insights.
Does it convert multi-page Framer sites to HTML?
Yes. It discovers every published page — including nested routes like /work/project — converts each to HTML, and preserves your URL structure so existing links keep working.
Why is a page missing from my Framer HTML export?
Because the converter couldn’t reach it from the public site. It reads Framer’s sitemap and follows the links on every published page, so unpublished and password-protected pages are skipped, and so is a page that’s in neither the sitemap nor any link. Publish or link the page, then convert again.
Is the Made in Framer badge removed?
Yes. The Framer to HTML converter removes the Made in Framer badge from every page automatically during the SEO pass.
Do I need my Framer login or API key?
No. The converter only uses your public published URL. It never asks for your Framer account, password, or API key, and it cannot access private drafts or password-protected pages.
Will my Google rankings drop after HTML export?
Not if your URLs stay the same. The converter keeps your paths, titles and meta descriptions and points canonical tags at the domain that serves the files. If any URL changes, 301-redirect it, and expect some movement: Google notes rankings can fluctuate while it recrawls a moved site.
Framer to HTML converter vs NoCodeXport — what’s different?
Both can get a Framer site out as files. This Framer to HTML converter is Framer-focused: it re-encodes images to self-hosted WebP, removes trackers and runs an SEO pass, includes a PageSpeed comparison tool, and also offers a real Next.js project export. See the full comparison on our vs NoCodeXport page.
Framer to HTML vs Framer to Next.js — which should I pick?
Pick the Framer to HTML converter when you want static files you can upload to any host. Pick Framer to Next.js when you want a real App Router codebase, split into React components, that you can keep developing. Both keep Framer’s runtime, so animations behave the same in either. You can run both and compare.
How do I move from Framer to HTML entirely — not just export the files?
Convert the site, deploy the files to a host such as Cloudflare Pages or Vercel and check them on a preview address, then point your domain’s DNS at the new host and 301-redirect any URL that changed. The converter keeps your URL structure, which handles most of the redirect work. Keep the Framer project published, because the exported pages still load Framer’s runtime and fonts from Framer’s servers.
Do Framer forms work after converting to HTML?
Not as they are: Framer’s built-in form backend stays with Framer. Point each form at a service such as Formspree or Tally, then send a test submission from the preview before you move your domain.
Can I stop using Framer completely after converting to HTML?
Not completely. Every output, HTML included, loads Framer’s runtime and fonts from Framer’s servers, so the Framer project should stay published. Your domain, files and hosting move to you; the animations still depend on Framer.
What if a page fails to convert?
The rest of the site still converts: a single failed fetch does not abort the job, and the pipeline log shows what happened on each page. Fix the cause, then convert again; the troubleshooting table on this page lists the common ones.
Is this converter affiliated with or approved by Framer?
No. This is an independent, third-party tool and isn't affiliated with, endorsed by, or sponsored by Framer. It's meant for converting sites you own or are authorized to convert.