Framer does not include a one-click export of an entire published site as portable HTML files. If you own or are authorized to migrate the site, a Framer to HTML converter can capture its public pages and package a static bundle for your own hosting. The meaningful question is not just whether index.html exists; it is whether the complete site works after leaving the original host.
This guide covers the conversion, the trade-offs of removing Framer's JavaScript runtime, and a safe path to launch. For a project that retains Framer's runtime inside a Next.js application, see the Framer to Next.js guide.
What is in an HTML export?
A typical export contains HTML pages, styles, scripts, and assets. FNJ's HTML mode starts from the published URL, discovers linked public routes, optimizes supported assets, and removes Framer's primary runtime. It rebuilds common appear and scroll-reveal effects with lightweight CSS and an observer script. The result can be hosted as static files without a Next.js server.
That is a conversion of the published site, not an export of Framer's private editor project. It also does not include a new backend for forms, a live copy of Framer CMS, or every third-party service your site may use. The HTML independence audit explains how to find remaining remote dependencies.
Convert a Framer site to HTML
- Publish the source. Open the public site in a browser and note every route you care about. Private drafts cannot be read from a public URL.
- Enter the URL. Use the Framer to HTML converter and select the HTML output. FNJ requires a signed-in account for conversions.
- Review the result. Check page count, visual layout, images, and links in the preview. Try the phone menu and any important interactive CTA.
- Download the static bundle. Extract the ZIP and identify the folder containing
index.html. Keep the export and your changes in version control. - Deploy to a preview host. Static hosts can serve these files without a Next.js build. For an example, follow our Cloudflare Pages deployment guide.
- Test and move the domain. Verify direct nested routes, forms, canonicals, redirects, and search indexing settings before changing DNS.
If a page is missing, first check whether it was linked from a public page. If a page exists only in a private Framer draft or is never linked, a URL crawler may not discover it automatically.
What survives, and what needs work?
| Feature | What to verify after conversion |
|---|---|
| Layout and typography | Compare desktop and phone widths, including custom fonts. |
| Images and video | Check every image-heavy section and any video or third-party embed. |
| Basic reveal animation | HTML mode reconstructs common appear and scroll effects; inspect the timing and final state. |
| Complex interaction | Test hover effects, menus, carousels, custom cursors, and stateful components individually. |
| Forms | Submit a test message and confirm its destination. |
| CMS-driven pages | Confirm existing routes and plan how new entries will be added later. |
| Search metadata | Check title, description, canonical, sitemap, and redirects on the deployed domain. |
Removing a runtime can improve the delivery profile of a static site, but it also changes what drives its interactions. There is no honest universal promise of a particular Lighthouse score or perfect behavior for every Framer design. Test your own URL and compare the output with the published source. If exact animation behavior matters more than a lighter static bundle, try the Next.js export, which retains the runtime.
How to host the files
Upload the folder containing index.html and its assets to a static host. Make sure the host serves nested pages using the same paths visitors used on the original site. Cloudflare Pages, Netlify, Vercel's static hosting, and other file hosts can all serve static HTML, but their directory-index and redirect behavior can differ. Test direct links and refreshes on a preview URL before moving the production domain.
If you keep the same public URLs, the move is mostly a hosting change. If paths or domains change, map each old URL to its closest new equivalent. Google documents separate processes for changing hosting without URL changes and changing URLs. Keep the old site available until the new deployment passes QA and traffic is reaching it.
Does HTML mean no Framer dependency at all?
No export format can answer that without inspecting the actual site. FNJ's HTML mode removes the main Framer runtime, but a particular page may still call an external video, font, analytics service, form endpoint, or other asset. Use your browser's Network tab on the preview deployment, scroll through the page, and exercise each interactive feature. Keep or replace each dependency deliberately before canceling the original service.
For a compact pre-launch list, use the Framer to HTML export checklist. When you're ready, convert your published Framer site to HTML and judge the result on your own pages.