.webp)
What is Webflow Localization?
Webflow Localization is Webflow's native tool for building and managing multilingual versions of a site, right inside the Designer. Rather than bolting on a translation plugin or running a separate site per language, you add locales to your existing project and edit content, images and styles for each one without leaving Webflow.
Once a locale is added, you can switch into it from the Designer and see exactly how the site will look for that audience before anything goes live. Nothing publishes automatically, and you can build and preview every locale for free, only paying once you're ready to make it live.
Webflow Localization plans: Essential vs Advanced vs Enterprise
Localize is sold as an add-on, priced per locale rather than as a flat fee, with three tiers that unlock different levels of control.
Essential: $9 per locale, per month
Covers up to three locales, 10,000 AI-translated words per locale each month, and the core localization tools: CMS content, static pages, alt text and style overrides. This is enough for most small sites adding one or two languages.
Advanced: $29 per locale, per month
Extends to ten locales and 50,000 words per locale a month. It also adds asset localization (swapping the actual image, not just the alt text), localized URLs and automatic visitor routing based on browser language.
Enterprise: custom pricing
Built for larger sites: custom locale counts and word limits, plus element visibility per locale, so you can show or hide specific sections for specific audiences.
Worth knowing before you scope a project: if your site needs different images per locale, not just translated alt text, that's an Advanced-tier feature.
How to localize a Webflow site: the basic process
The mechanics are straightforward once a project is scoped properly.
- Add your locales in Site Settings, choosing a subdirectory (like /de/ or /sv/) for each one. This is preferable to using subdomains, as it keeps your SEO authority in one place.
- Audit what already exists, what should be translated and what shouldn't. On sites with any history, it's common to find some content already written in the target language, mixed in with everything else. Such content needs sorting into the right locale before you translate anything.
- Translate the rest. Webflow's built-in AI translation handles the first pass, triggered per item in the Designer. From there, it's worth building in a review step where your team checks the translations, since AI translation is a solid starting point but not something to publish blind.
- Add a locale switcher so visitors can move between languages, and decide whether to also turn on automatic routing based on browser language (Advanced and Enterprise only).
- Check the layout in every locale before publishing. Text length changes between languages, and localization only fixes the words, not what happens when text suddenly doesn't fit the space designed around it.
How localization works in the CMS
Inside the CMS, each locale gets its own version of every collection item, built from a copy of the primary locale's content. The primary locale itself stays the same, so any translation work happens on the secondary locales only, whether that's done by hand or scripted.
There's no bulk translate option. Webflow's "Translate all fields" button works on one CMS item at a time, and there isn't a batch action to run it across a whole collection. For a small blog this barely matters. For a site with a couple of hundred items across several collections, it adds up, and it's worth accounting for in your time estimate rather than assuming it's a quick toggle. It's not yet possible through the Webflow MCP either, so this isn't something you can easily hook an AI assistant up to automate.
SEO and localized URLs
Webflow handles the SEO groundwork automatically once locales are set up: hreflang tags in the page head, an updated sitemap, and a subdirectory for each locale (like /fr/) to keep domain authority in one place.
That subdirectory is included on every plan, but the page slug itself isn't. On Essential, a French page still uses the English slug, so it sits at /fr/about-us. Advanced lets you rewrite the slug too, giving you /fr/a-propos instead.
Design considerations: handling longer translations
Some languages simply take up more space than English. German is the classic example: compound words can run long, and translated text is often 20 to 35% longer than the English original. A button label or nav item that fits comfortably in English can overflow or wrap awkwardly once translated.
Webflow's style localization helps here. It lets you override typography and spacing, font size, padding, line height, for a specific locale without touching the design anywhere else, so a slightly smaller font or extra padding on one locale doesn't affect the rest of the site. It's worth checking navigation, buttons and cards specifically, especially on mobile, where fixed-height elements and no-wrap text are the most common place this breaks.
Limitations to check before you start
A few things are worth knowing before quoting or scoping a localization project.
- Ecommerce doesn't work with Localize. Products, categories and checkout pages can't currently be localized, and there's no announced timeline for that changing.
- There's no bulk CMS translation, as covered above, only per-item.
- Asset localization needs the Advanced plan. Different images per locale aren't available on Essential.
- Your primary locale is permanent. You can't delete it, and there's no way to promote a secondary locale into that role later, so the language you choose as primary at setup is a decision you're stuck with, not one you adjust down the line.
None of this makes Webflow Localization complicated exactly, but these limitations can affect the project and, in the Ecommerce case, might mean localization isn't the right fit at all for that particular site. Once you know what each plan actually includes and where the rough edges are, it's a solid tool for getting a site in front of a worldwide audience.
