To export a Framer website, you have one honest constraint and two good options. The constraint: Framer has no built-in code export — there is no "Download HTML" button anywhere in the editor. The options: convert your published site to static HTML or to a real Next.js project using a converter. Both work from your public URL without a Framer plugin or login. Conversion time varies with site size and features.
This guide walks through every method people try, what actually works, and how to do it properly without losing your design or your SEO.
Why Framer doesn't have an export button
Framer's business model is hosting. Your site lives on Framer's servers, renders through Framer's JavaScript runtime, and stays online as long as you keep paying (or accept the free plan's limits and badge). That's fine for many teams — but it means "exporting" was never built into the product. When people search for how to export a Framer website, they're really asking: how do I get my finished site out of Framer's ecosystem?
Method 1: Convert to static HTML (recommended for most sites)
The fastest path is a Framer to HTML conversion. You paste your published URL, and the converter:
- Crawls every public page of your site
- Captures the fully rendered HTML
- Strips Framer's JavaScript runtime (the biggest performance win)
- Self-hosts your images, re-encoded to WebP
- Inlines fonts and runs an SEO pass (canonicals pointed at your domain, alt text, badge removed)
- Hands you a static bundle you can download or deploy to Netlify/Vercel in one click
Removing Framer's runtime can reduce script weight, but performance depends on your site's media, third-party scripts, and host. Measure the converted deployment rather than assuming a particular Lighthouse score. Appear and scroll animations are rebuilt in lightweight CSS, so the site still feels like your design.
Best for: marketing sites, portfolios, landing pages — anything where speed and simple hosting matter most.
Export your site to HTML here.
Method 2: Convert to a Next.js project
If you want a real codebase instead of a folder of files, the Framer to Next.js export produces a deployable Next.js App Router project — one statically-prerendered route per page, with Framer's runtime kept intact to retain authored animations and interactions. Test the generated deployment against the original, especially custom components, forms, and embeds.
Run npm install && npm run build and deploy it like any Next.js app. This is the right choice when a developer will keep working on the site, or when preserving complex runtime effects matters more than minimizing JavaScript. Verify the result on your own site.
Best for: teams moving to a code workflow, sites with heavy interactions, projects that will grow beyond what a site builder can do.
Method 3: Manual export (works, but painful)
You can right-click → View Source on each published page and save the HTML by hand. Three problems:
- Assets stay on Framer's CDN — images and fonts still load from framerusercontent.com, and can break if you unpublish
- The runtime comes along — you keep the slow JavaScript without any of the hosting convenience
- It's per-page — a 15-page site means 15 manual saves, and internal links need fixing by hand
Manual export makes sense only for grabbing a single page's markup as reference. For a real migration, use a converter.
What survives the export?
| Feature | HTML export | Next.js export |
|---|---|---|
| Layout, fonts, breakpoints | ✓ | ✓ |
| Appear/scroll animations | ✓ (rebuilt in CSS) | ✓ (original runtime) |
| Complex runtime effects (WebGL, custom cursors) | Trimmed for speed | ✓ |
| Multi-page structure and URLs | ✓ | ✓ |
| SEO meta, OG tags | ✓ + SEO pass | ✓ |
| "Made in Framer" badge | Removed | Removed |
| Framer form backend | Repoint to Formspree/Tally | Repoint to Formspree/Tally |
| Password-protected pages | Not converted (public URLs only) | Not converted |
After exporting: hosting and domains
Converted sites deploy anywhere static files run: Netlify, Vercel, Cloudflare Pages, GitHub Pages, S3, or classic shared hosting. Free tiers comfortably serve most sites, which is why the whole move usually lands at $0/month — see the full self-hosting guide for the domain/DNS steps and the pricing breakdown for what's included.
Your SEO carries over: the converter preserves titles, descriptions, and URL paths, and repoints canonicals to your new domain. Keep the same domain and paths when possible, then monitor Search Console; a host move is not a guarantee of unchanged rankings. If URLs change, map old pages to their closest new pages with permanent redirects.
Export your Framer website now
Paste your published URL into the converter — FNJ requires an account and lifetime access for conversions. Review the preview and measure your own result in PageSpeed Insights.
Before switching the domain, use the Next.js interaction QA checklist or the HTML independence audit, depending on the output you choose.