Skip to main content
FXFramExporter
Export a site
Documentation

How it works

The three steps

  1. 1. Paste the published URL. It has to be the live, public address — the exporter reads what a visitor sees, so a password-protected site will not work.
  2. 2. Preview the full site. Free, every page, rendered from your own content. This is where you confirm the export is worth paying for.
  3. 3. Download the bundle and deploy it. Unzip, then follow the guide for your host.

What is in the bundle

Typical export layout
my-framer-export/
├── index.html
├── about.html
├── pricing.html
├── 404.html
├── assets/
│   ├── styles.css
│   └── app.js
├── images/
└── fonts/

Flat files, no build step, no runtime dependency. Any host that serves static files will serve this.

Two things to fix before launch, every time
Exported forms post nowhere until you point them at a form service or your own endpoint — they will look fine and silently swallow submissions. And most hosts need a small config file to serve /about rather than /about.html; without it, every internal link 404s.

Questions

›What does the exporter actually capture?

The fully rendered page as an anonymous visitor sees it: markup, CSS, JavaScript that ships with the page, images at the sizes used, fonts, and the head tags including your meta and Open Graph data.

›What can it not capture?

Anything behind a login or a password, anything that only exists in the Framer editor rather than the published site, and interactions that depend on Framer's runtime rather than on CSS.

›Does it handle multi-page sites?

Yes — full-site mode crawls the published site and captures every page it can reach from your navigation and internal links.

›What about CMS collections?

Pre-rendered CMS pages are captured as static HTML, one file per entry. What you lose is the ability to add a new entry through the Framer UI, because there is no longer a CMS behind it.