Framer doesn't export HTML. When that matters, and when it doesn't

A client asks for “the site files” so their IT team can host it next to everything else. You built it in Framer. What do you send them?

Nothing, it turns out. Framer’s help center says it in one line: “Framer does not offer HTML export for self-hosting.” (source)

Its performance features run on Framer’s own hosting, so the site lives there. Scraper tools exist, but they aren’t Framer’s, and a scraped copy can lose whatever the hosting was doing for it.

Disclosure up front: we make Swebsy, a visual builder that does export plain HTML. So weigh what follows. Every Framer fact links to Framer’s own pages, checked 30 September 2026.

When it doesn’t matter

For a lot of sites, managed hosting is exactly what you want. Framer is a very good design tool that happens to publish, and on its plans you get:

• a CMS (2 collections on Basic at $10/month billed yearly, 10 on Pro at $30)
• staging and redirects on Pro
• team editing, at $20/month per extra editor
• a built-in AI agent on monthly credits

(pricing)

Framer's editor and built-in agent, from the demo on framer.com.

If your site needs a CMS, several editors, or heavy motion, and nobody will ever ask for the files, Framer is a strong pick, and losing HTML export costs you nothing.

When it does

• The site has to live on your infrastructure. Compliance, a company CDN, an internal network.
• A client owns the deliverable. “Here’s the ZIP” is a cleaner handoff than “here’s a seat on my account”.
• You want to be able to leave. If pricing or limits change, moving off Framer means a rebuild, not a redeploy.
• You want free hosting for a small site. GitHub Pages and Cloudflare Pages host static files for $0 on your own domain. Framer’s custom domain starts at the $10/month Basic plan.

What exporting looks like in Swebsy

Swebsy exports a ZIP of plain HTML, CSS and assets on every plan, including free, with no account. It’s one click from the Deploy menu.

Deploy → Export code downloads the site as a ZIP.

What’s inside is what any static host expects:

├── index.html
├── about.html                  # one file per page
├── css/
│   └── styles.<hash>.css       # every style, in one file
├── js/
│   └── swebsy-components.<hash>.js  # only when a page needs it
├── assets/                     # your images
├── fonts/                      # self-hosted fonts
├── sitemap.xml
└── robots.txt

Exporting the website ZIP from Swebsy.

You also get an editable project file you can import later. On the free plan the pages carry a small “Made with Swebsy” badge; a paid plan removes it.

The trade-offs, plainly: no CMS, no team seats yet, and no Framer importer. Moving means rebuilding the pages, usually from a template.

It also has an MCP bridge, so Claude Code or Cursor can edit a project open in the editor. You bring your own agent and pay its provider; nothing is billed per token on our side. Framer has its own take on this: external agents, currently in beta.

The short version

Pick by where the site has to live. If Framer’s hosting is fine forever, Framer’s design tools are hard to beat. If the files have to leave with you, check that before you build, not after.

The full side-by-side, with prices for a few common jobs: Swebsy vs Framer.