From published URL to portable files

Export Framer to HTML

Download your published Framer site as portable HTML, CSS and JavaScript for self-hosting, editing or developer handoff.

How it works·01

Paste your Framer URL and choose pages.

scanning…

Pages found0

/
/about
/blog/*
/pricing
/contact

Choose what to include

Paste the public Framer link

Copy the address of your published site, not its editor. The page must open without a login.

Choose the pages to export

The scan follows links up to three levels deep. Select the pages you need from the results, within your plan’s limit.

How it works·02

Download your Framer site as HTML files.

yoursite.framer.website

HTML

IMAGES

CSS

Inside your ZIP download

Page content and design

Your published Framer pages, visible content and responsive styles. This is a copy of the live site, without the Framer editor. Review page titles and search settings before publishing.

Images and fonts

Choose downloaded assets to include available images and fonts. Free exports keep them linked to the original site. Videos and embeds may still need an internet connection.

Menus and animations

Supported menus, component states and animations are included. Test custom components and embeds; some still need external services.

How it works·03

Test your exported site then publish it.

framer-export.zip

Vercel

Netlify

Cloudflare

GitHub

Choose your hosting

Test the exported site

Unzip the download and open the files through a local web server or temporary hosting. Check layouts, links, forms and animations on desktop and mobile.

Publish on your chosen host

Upload the tested files to Vercel, Netlify, Cloudflare Pages or GitHub Pages. Check the live site before changing your domain. Hosting costs and provider terms apply.

Before you move your domain. CMS content is a fixed copy; export again after updates. Reconnect forms and hosted services. Test custom components and advanced animations before launch.

Framer vs HTML Export Tool Comparison

Framer documents that published site files are portable. NoCodeExport automates selecting public pages and packaging their rendered output for review and self-hosting.

What you need	Framer native workflow	Recommended path NoCodeExport
Portable HTML output	Framer says its published HTML, CSS, JavaScript and assets can be downloaded and hosted elsewhere.	Packages rendered HTML, CSS, and JavaScript for a standard static hosting workflow.
Export workflow	Follow Framer’s portability guidance to retrieve published files; CMS data uses CSV or JSON plugins.	Starts from the live site and produces a ready-to-review export.
Ownership after launch	Published files can move to another host; CMS editing and hosted features need separate planning.	The exported front-end files can live on your infrastructure; hosted services still need replacements.
Best fit	Staying fully inside Framer for design and hosting.	Moving to HTML, reducing lock-in, or handing code to another team.

Framer portability guidance, checked 7 September 2026: www.framer.com

Framer guides that support the export flow

Use these guides for migration planning, interaction checks, and deployment of a rendered Framer export.

One site or ongoing exports?

Export once with Site Pass, or choose Pro for regular updates and client projects.

Site Pass

One-time export

One site to move. One payment. No subscription.

$15once

Export once — $15

Features included:

One successful export, up to 100 pages
Website files with downloaded assets
30-day access to your download

Scan your site and review the pages before checkout.

A failed export restores your pass so you can retry.

Pro

Keep exporting as your sites evolve.

$10/ month

Get Pro — $10/month

Features included:

50 exports every month
Up to 100 pages per export
Download files and assets, or deploy to GitHub and Netlify

Billed monthly. Renews until canceled.

Annual billing and Agency options. See all plans

Frequently Asked Questions

Everything you need to know about the export process.

You can use the free plan to test a publicly accessible Framer page. Full-site scope, local assets and deployment options depend on the current plan limits shown in the exporter.

Framer's editor has no code-export button on any plan: it can copy individual components as React, export assets as JPG or PNG through the desktop app, and take CMS entries out as CSV or JSON with a plugin. Your published site is a different matter — Framer's own documentation says every Framer site is published as standard HTML, CSS and JavaScript that you can download and host elsewhere. NoCodeExport retrieves exactly that: it loads your public URL, captures the rendered pages, and packages them with reachable assets as a ZIP, without access to your Framer account.

Supported scroll, hover, menu and transition behavior can be retained through captured runtime files or recovery helpers. Results vary by site, so test important interactions at every breakpoint; stateful code components and hosted embeds may need manual work.

Yes. Export the published Framer site, unzip the HTML, CSS, JavaScript, and assets, then deploy that folder to Vercel, Netlify, Cloudflare Pages, GitHub Pages, or a private server. Test navigation, forms, analytics, and custom domains before moving production traffic because services tied to Framer may need to be reconnected.

Single-page export captures the submitted page. Full-site export follows reachable same-site links up to the crawler depth and the selected plan's page limit. Unlinked, private or login-protected routes are not discovered automatically.

The local-assets option downloads reachable images and fonts and rewrites their references. Large videos, third-party embeds and inaccessible files can remain remote, so inspect the ZIP before unpublishing the original site.

Published CMS pages can be captured as static HTML at export time, so the content remains visible but no longer updates from Framer automatically. Forms and other services that depend on Framer should be tested after export and, when necessary, connected to a new form endpoint or backend before launch.

Framer Export Code: What the ZIP Contains

This Framer export code workflow starts from the public, published URL rather than the private editor. NoCodeExport captures the rendered frontend and packages the selected pages with their HTML, CSS, JavaScript, and metadata. Images and fonts are referenced or included according to the export options and plan.

The result is portable static code you can inspect, version, edit, and self-host on Vercel, Netlify, Cloudflare Pages, GitHub Pages, or your own server. It is not the original Framer project file or an editable set of React components; teams that need application architecture should choose a React or Next.js rebuild.

What Is Preserved and What Is Not

NoCodeExport captures the rendered HTML, styles, metadata and reachable assets. Supported menus, reveals and other browser interactions may continue through captured runtime files or recovery helpers, but each page still needs visual and functional testing.

The ZIP is not the original Framer project. CMS updates, forms, custom code components, external embeds and advanced stateful behavior may still depend on Framer or another service and can require replacement.

Framer Export Code vs a React or Next.js Rebuild

Choose a static export when the published design is finished and the goal is portable files, independent hosting, a backup, or a fast developer handoff. Choose a React or Next.js rebuild when the site needs reusable components, application state, authentication, a database, or frequent feature development.

The two outputs solve different problems. Review the tradeoffs in our Framer to code vs Framer to HTML comparison before treating an exported snapshot as a replacement for a maintained application codebase.

How to Verify a Framer Export Before You Migrate

Treat the export like a release candidate, not a blind download. Compare representative pages at desktop and mobile widths, click every navigation path, check images and custom fonts, exercise forms and interactive elements, and review the browser console for missing files.

For an SEO-safe migration, inspect the rendered title, description, canonical, robots directive, structured data, and internal links on each important template. Record anything that depends on Framer — especially CMS updates, form delivery, analytics, or advanced Motion behavior — and reconnect or rebuild it before switching the domain.

Ready to export your Framer site?

Paste your published URL and review the pages. No payment is needed to scan.

Check my site

Also Explore Our Solutions For