How to host a Framer site yourself with a static export
By Jake Marsh · Updated
Framer doesn't export published sites for self-hosting, but you can host a static copy of your design. Open Sourceferry, tick your pages on the Export tab, choose Static HTML and CSS, pick Save into the ZIP for images and click Download ZIP. The ZIP holds a folder per page with an index.html, shared and per-page CSS and an assets/ folder, all with relative paths, so it runs from any static host. Effects, animations, forms and Framer's hosting features don't come along.
What you get
| Path | What it holds |
|---|---|
index.html | The home page |
about/index.html and so on | A folder per page, so addresses stay like /about/ |
css/site.css | Shared rules: color and text styles, components |
css/<page>.css | Each page's own rules |
assets/ | Images and SVGs, with alt text in the markup |
README.md, sourceferry-report.csv | How to open it, and what didn't carry over |
Steps
- Open Sourceferry and tick the pages on Export.
- Choose Static HTML and CSS under Format.
- Choose Save into the ZIP under Images, so the site doesn't depend on Framer's image servers.
- Click Preview first page to check each breakpoint.
- Click Download ZIP and unzip it.
- Test it locally with any static server, for example
bunx serve ., and open the address it prints. - Upload the folder to your host: drag it into Netlify or Cloudflare Pages, push it to a GitHub Pages repository, or copy it to your own server's web root.
- Point your domain at the new host.
Before you switch your domain
Check these, because a static copy behaves differently from a Framer-hosted site:
- Forms. Forms aren't exported. Add each one in HTML and connect it to a form service or your own endpoint.
- CMS pages. A CMS detail page is exported once as a layout, and the items as JSON if you ticked CMS collections as JSON. A static site needs a page per item, which means generating them yourself, or using the Next.js format, which builds one per item.
- Animations and hover states. Not exported; add them in CSS if they matter.
- SEO tags. Page titles, descriptions and social images live in Framer's page settings, which the export doesn't carry. Add a
<title>and meta description to eachindex.html. - Redirects, analytics, search and password protection are Framer hosting features. Set up their equivalents on your host.
- Fonts you uploaded to Framer. Add their files and
@font-facerules. Google Fonts and Fontshare are already linked.
Keeping it up to date
The export is a snapshot. When the design changes in Framer, export again and replace the files you haven't edited. If you plan to edit the code by hand, keep it in version control so a new export can be compared, not copied over.
What it costs
Scanning and the preview are free. The trial covers 5 exports of up to 3 pages over 7 days, with no card. After that Sourceferry is $59 a month, $499 a year or $799 once per seat, for every project and page. Details are on the Sourceferry page.
Sourceferry
Export a Framer project as code you edit: a static HTML and CSS site or a Next.js project, built from the canvas inside the plugin, with breakpoints, styles, images, fonts and CMS content $59 a month or $499 a year per seat, or $799 once.
Questions
Is it allowed to host a Framer design somewhere else?
Sourceferry writes new code from your own design on the canvas. Whether you can use every asset elsewhere depends on its source: fonts, images and templates you bought may have their own license terms.
Do I need a build step?
No. The static export is finished files. Upload the folder as it is, or serve it locally with any static server.
Does JavaScript run on the exported site?
The export is HTML and CSS. SVGs are inlined with scripts and event handlers removed.
Can I export only some pages?
Yes. Tick only those pages; links to pages you left out are listed in the report.
More Sourceferry guides
- How to export a Framer component or section as React code
- How to export a Framer site to a Next.js project