Before you convert a Framer site to HTML, five minutes of prep prevents almost every issue people run into — this is the checklist, in order, to run through before and after converting. Nothing here is complicated; it's the difference between a clean first conversion and troubleshooting afterward.
Before you convert
☐ Confirm the site is published. The converter reads your live, published URL — a page still open only in the Framer editor isn't visible to it yet. Publish first.
☐ Check every page is linked. The converter discovers pages by following links from your homepage and nav. A page with no inbound link anywhere on the site won't be found automatically — make sure your full nav/footer is in place before converting, or note any orphan pages to convert individually by direct URL.
☐ Note any password-protected pages. These can't be converted (the tool only reads public URLs) — decide ahead of time whether those pages need a different handling.
☐ Know which output you want. HTML export for maximum speed with the runtime stripped, or Next.js export for exact fidelity with the runtime kept. Undecided? See HTML export vs Next.js export — or just run both, it's free either way.
☐ Have your deploy target ready (optional but saves a step). If you're deploying to Netlify or Vercel, have your access token ready so you can go straight from conversion to live in one flow.
During conversion
☐ Watch the pipeline log. It shows page discovery, HTML capture, image optimization, and the SEO pass in real time — a useful first signal if something's about to be off (e.g., far fewer pages discovered than you expected).
☐ Don't close the tab. Most conversions finish in under a minute, but larger multi-page sites can take a couple of minutes — let it finish rather than retrying mid-run.
After conversion — verify before you deploy
☐ Click through every page in the live preview. Not just the homepage — check nested routes too.
☐ Check images loaded. Scroll the full length of a few image-heavy pages.
☐ Check fonts render correctly. Compare against the original at a glance.
☐ Test a few internal links. Especially any deep links to nested pages like /work/project-name.
☐ Run the PageSpeed comparison. Paste your original Framer URL and the converted URL — a successful conversion should show Performance and SEO holding steady or improving, never regressing.
After deploying
☐ Point your domain and verify DNS propagated. Usually one CNAME record — see the self-hosting guide if this is your first time.
☐ Re-check your canonical tag on the live domain. It should point at your new domain, not back at *.framer.website.
☐ Submit the new URL to Search Console (or your search engine of choice) to speed up re-indexing, especially if you changed domains.
☐ Repoint any forms. Framer's form backend doesn't come along in the export — swap the form action to a service like Formspree or Tally.
☐ Decide on your Framer subscription. If the converted site is now live and stable, see cancel Framer, keep your website for the right order of operations.
If something's off
Nearly every issue on this list traces back to one of two things: a page wasn't linked (so it wasn't discovered), or you're checking a preview URL instead of the final deployed domain. Full symptom-by-symptom fixes in Framer to HTML conversion problems.
Run through it now
Print this list or keep the tab open, then convert your Framer site — checklist in hand, first-pass issues become rare.