Guide · Whole-site backup

Can you export a Framer site to HTML?

Not from Framer itself. Framer's help center says there is no native HTML export, and your published site depends on Framer's hosting. You can still keep an offline copy of what you published. It won't be a working website, but it shows every page as it looks, and that is enough to rebuild from if you ever need to.

Why an offline copy works at all

Framer renders published pages on the server. The HTML a visitor receives already contains the text, image tags and the CSS for every breakpoint. JavaScript then adds the animations and interactions on top. Save the HTML with its images, fonts and stylesheets and leave the scripts out, and the page still renders.

We tested this on our own seven-page Framer site with a blog. Every page opened with the network blocked: no requests, no broken images. At desktop and phone widths it looked the same as the live site. The only difference was Framer's “Made in Framer” badge, which is added by script.

What a copy like this does and doesn't keep

  • Kept

    Every page in your sitemap as HTML, the layout for desktop, tablet and phone, text, images in every size Framer serves, fonts and stylesheets. Links between your pages point to the local copies.

  • Scripts

    A copy with the scripts removed shows how each page looks once it has loaded, without animations, hover effects or carousels. Keeping them means saving every script bundle and everything it imports, and serving the copy from a web server, because browsers don't run module scripts from file://. Forms keep their markup but still send submissions to the original service.

  • Not the project

    It is not an editable Framer project. Components, variants and the canvas stay inside Framer. Framer's version history is the way back for those.

  • Not the CMS

    Collection pages are saved as they look, but the CMS data itself (fields, drafts, slugs, references) needs its own backup in JSON or CSV.

Doing it yourself

Mirroring tools such as wget or HTTrack can get you most of the way, but the details matter. These steps are the ones that made our copy work offline:

  1. List every page from https://your-site.com/sitemap.xml. Pages missing from the sitemap, such as password-protected or unlisted pages, won't be found.
  2. Save each page's HTML, then download what it references: images on framerusercontent.com (including every size in srcset), fonts from fonts.gstatic.com, and the URLs inside stylesheets and inline <style> tags.
  3. Rewrite those URLs to relative local paths, and point links between your own pages at the local files.
  4. Remove the script tags. Otherwise the copy keeps trying to load Framer's code from the network.
  5. Check the result with your network switched off. A copy that only works online is not a backup.

Only copy sites you own or manage, and repeat it after big changes. A copy from six months ago shows the site as it was six months ago.

Or let FrameVault keep it with your CMS backups

On Pro, Studio and Agency, every connected site has a Site archive button. FrameVault finds the published URL through your Framer connection and saves every page in the sitemap, however many there are, with the original HTML, the script bundles and everything they import, images, fonts and CSS, plus sitemap.xml, robots.txt and a README for hosting the copy on Netlify or Cloudflare Pages. You get one ZIP, with a list of anything it couldn't download. It can also run weekly or daily, with desktop and mobile screenshots of every page and older archives kept as history. Your CMS content is backed up on a schedule alongside it, so you can restore items into Framer. A customer asked for this so they would never have to rely on Framer alone, and we built it the same week.

Start 7-day free trial →Compare backup options

Pro: 7 days free, then $12/month. Cancel any time before day 7 and you pay nothing. Only need the CMS? Start free: weekly CMS backups for one site, no card.