Most Framer to HTML conversion problems fall into four categories: missing pages, broken images, missing fonts, and pages that look "frozen" without animations — and each one has a specific, fixable cause. This is a troubleshooting guide for exactly those symptoms, written from what actually goes wrong during conversion and how to fix it.
"Some of my pages are missing"
Cause: the converter discovers pages by following links from your site — a page with no inbound link anywhere on the site is invisible to it, the same way it would be invisible to Google.
Fix: make sure every page is linked from your nav, footer, or another page, then re-convert (it's free, no limit on retries). If a page is intentionally unlinked (a landing page for an ad campaign, say), convert it individually by pasting its exact URL.
"My images are broken or missing"
Cause: almost always one of two things — the image was hosted somewhere other than Framer's own asset CDN and that source is no longer reachable, or the page hadn't fully loaded when the source was captured (rare, but possible on very asset-heavy pages).
Fix: re-run the conversion — a fresh fetch usually resolves transient loading issues. If specific images consistently fail, check they're not behind a login or referrer-restricted source in the original Framer project.
"The fonts look different after converting"
Cause: the HTML export inlines fonts during conversion — if a font was loaded from a source with restrictive licensing or CORS headers, it can't be captured and the page falls back to a system font.
Fix: this is uncommon with fonts served through Framer's own pipeline (Google Fonts, Framer's font library). If you're using a custom self-hosted font with strict CORS rules, that's the likely culprit — check the browser console on the original Framer page for CORS warnings as a diagnostic.
"My animations aren't playing — the page looks frozen"
Cause: this is often not a bug — it's the difference between the two export modes. The HTML export strips Framer's JavaScript runtime for speed and rebuilds appear/scroll animations in lightweight CSS. If an animation type isn't a simple appear/scroll effect (custom cursors, complex scroll-linked timelines, WebGL), it's trimmed intentionally to keep the page fast.
Fix: if you need every animation to behave exactly like the original, use the Next.js export instead — it keeps Framer's runtime intact, so all interactions are pixel-identical. See HTML export vs Next.js export to decide which trade-off is right for your site.
"The converted site looks different on mobile"
Cause: almost always a pre-existing responsive design gap in the original Framer breakpoints, made visible because the converted site now loads fast enough that you're actually looking closely at mobile for the first time.
Fix: compare the original Framer site on mobile against the converted one — if both show the same issue, it's a Framer-side breakpoint setting, not a conversion bug.
"My SEO/Lighthouse score dropped after converting"
Cause: this should not happen with a properly configured converter — a good one repoints canonical tags to your new domain and preserves meta/OG tags. If you're testing a /api/preview/... style temporary preview URL rather than your final deployed domain, some tools' preview infrastructure can itself be flagged by Lighthouse as non-indexable, which isn't a reflection of your actual deployed site.
Fix: always run your PageSpeed comparison against your final deployed URL, not an intermediate preview link, for an accurate read.
"Links point to the wrong place after converting"
Cause: internal links using relative paths sometimes need the export's <base>/canonical handling to resolve correctly under a preview subpath; on your real deployed domain at the root, this resolves itself.
Fix: verify links on the final deployed domain, not a nested preview path.
Still stuck?
Re-running the conversion fixes the majority of one-off issues — it's free and takes a minute. If a problem is consistent across multiple attempts, it's worth isolating: does the original Framer page have the same issue? If yes, it's a Framer-side setting, not a conversion problem.
Convert your site and check it against this list — most conversions have none of these issues, but now you know exactly what to look for if something's off.