By Mehdi HassanCan you move a localized Webflow site to Framer?
Yes, but every page is rebuilt and every translation is moved by hand or by import. No tool converts a Webflow project into Framer, and that's doubly true for locales. What makes a localized Webflow site to Framer move safe is copying the URL structure exactly, so search engines see the same addresses in every language.
Teams usually make this move for speed: Framer is quicker to design in and easier for marketers to edit. The cost is that Framer's CMS is simpler than Webflow's. If your translated content depends on multi-reference fields or many linked collections, read the limits below before you commit. For the decisions that apply to every multilingual move, start with our multilingual website migration playbook.
What should you check before moving locales to Framer?
Check three things first: whether your CMS structure fits Framer, how many locales you'll pay for, and whether your slugs are translated. Each one can change the plan or the price.
Check | Why it matters | What to do if it fails |
|---|---|---|
Multi-reference fields in CMS | Framer's relational fields are more limited than Webflow's | Test your structure in Framer first; flatten references or reconsider the move |
CMS items per collection | Framer caps items and collections by plan | Confirm the current limits on Framer's pricing page |
Number of locales | Framer charges per locale | Price every current and planned language |
Translated slugs | Each changed slug needs a redirect | Copy slugs exactly to avoid most redirects |
Locale-specific pages | Some pages may exist in one language only | List them so they aren't forgotten |
If any of these is a dealbreaker, a different route may suit you better. Our Webflow Localization vs Framer Localization comparison weighs the platforms on cost per locale and SEO control.
How do you move a localized Webflow site to Framer step by step?
Rebuild the primary language first, then add locales, then translations, then validate. Doing it in that order means you translate a finished design once instead of chasing layout changes across every language.
Export a full URL list per locale
Crawl the live site and list every URL in every language, including CMS items. Export Webflow CMS collections to CSV, one file per collection, and note which fields are localized.
Rebuild the design in the primary language
Recreate pages and components in Framer using your design system. Leave room for longer strings; German and French copy often runs longer than English.
Recreate CMS collections
Rebuild collections with matching field names and slugs. Re-host images, because Webflow CSV exports point at Webflow's CDN and rich-text images often come through as placeholders.
Add Framer locales matching Webflow's subfolders
Create each locale with the same code and subfolder you use today, such as /de/ and /fr/. Matching the path prefix keeps URLs stable.
Enter translated slugs and content
For each page and CMS item, copy the translated slug from Webflow exactly, then add translated text, SEO title, description and image alt text.
Validate hreflang on staging
Crawl the Framer staging site with a tool that reports hreflang, and check that every page has a reciprocal, self-referencing set with x-default.
Redirect what changed, then launch
Add 301s in Framer only for URLs that changed, connect the domain, and resubmit the sitemap. Then re-crawl the live site.
How do you handle translated slugs in Framer?
Treat translated slugs as data to copy, not text to translate. Build a sheet with one row per page or CMS item and one column per locale, filled from the Webflow export or a crawl. Then enter each locale's slug in Framer from that sheet.
If you want to improve slugs during the move, decide that deliberately and limit it. Every changed slug needs a 301 from the old URL and an updated hreflang set, and changing many at once makes it harder to tell why a language lost traffic. A safer approach is to keep slugs identical at launch and fix the worst ones a month later, once rankings have settled.
For example, suppose a customer stories collection exists in three languages
Hypothetical example: a collection of 30 customer stories is published in English, German and Spanish on Webflow, with slugs like /customers/acme, /de/kunden/acme and /es/clientes/acme.
The slug sheet has 30 rows and three slug columns. In Framer, the collection path per locale must produce the same prefixes: customers, kunden and clientes. If Framer's setup only lets you translate the item slug and not the collection path, every German and Spanish URL changes, and you'd need 60 redirects. Check how your Framer version handles localized collection paths on a two-item test before importing all 30.
How do you validate hreflang in Framer?
Framer generates hreflang for localized pages automatically, so validation is about confirming the output, not writing it. Check a sample by hand and the full site with a crawler, on staging and again after launch.
- View source on one page per template per locale. Look for a link tag for every locale, a self-reference and an x-default.
- Crawl the whole site. Use a crawler with hreflang reporting to find missing return tags and annotations pointing to redirects or 404s.
- Check locale-only pages. A page that exists only in German shouldn't list English or French alternates that don't exist.
- Match canonicals. Each locale page should canonicalize to itself, not to the English version.
- Recheck after launch. Domain connection can change absolute URLs, so crawl the live site within a day of going live.
For a deeper look at multilingual ranking risk, see our guide to migration SEO for hreflang and locale URLs.
What does it cost to run a localized site on Framer?
The running cost is the Framer site plan plus a charge for each locale. That makes Framer cheap for two or three languages and progressively more expensive as you add more. Check Framer's current pricing page, since plan names and locale pricing have changed more than once.
Compare that with the alternatives before you move. Webflow sells localization as a site add-on, and a Next.js site with a headless CMS has no per-locale fee but needs developers to change templates. If you expect many locales, our Next.js internationalization guide shows the code route, and Framer to Next.js migration cost shows what leaving Framer later would cost.
