Framer supports localized/multi-language sites, and exporting one adds a layer of complexity beyond a single-language export — worth understanding before you convert.
How Framer structures localized content
Framer's localization typically works through locale-specific routes or subdomains, with each language variant being its own set of pages sharing the same underlying design and layout, differing in content. The exact routing pattern (path-based like /es/about, or subdomain-based) depends on how the site was configured.
What a proper export needs to preserve
Every locale's full route set. A page-discovery process that only crawls the default language will silently miss every other language's pages entirely — an easy mistake if the export tool wasn't built with localization specifically in mind.
hreflang tags, which tell search engines which language/region each page variant is for, and which URL to serve to users in a given locale — critical for correct international SEO, and easy to lose entirely in a naive export that only preserves visible content, not this kind of metadata.
Locale-specific metadata — titles, descriptions, and Open Graph tags should be genuinely translated per locale, not just the visible page content, if the original Framer site had them translated (which not all localized sites bother with — worth checking your source site's actual completeness here too).
What to verify after exporting a multi-language site
- Every locale's routes actually exist in the exported output, not just the default language
- Language switcher UI (if the original site had one) still works and points to the correct corresponding page in each language, not just to a fixed URL
hreflangtags are present and correct in the exported HTML's<head>- Locale-specific metadata (title/description) is genuinely per-locale, not duplicated from the default language
If your export tool doesn't handle this well
Multi-language sites are a meaningfully more complex export case than a single-language site, and not every converter handles the full scope correctly on the first pass — this is worth explicitly testing (checking a non-default locale's pages, not just assuming they came along) rather than assuming a tool that handles single-language sites well automatically handles multi-language ones equally correctly.