.svg)
.svg)
.svg)
%201Q26_%20GRC%202029.png)
.svg)
.svg)
How do you translate and localize a Webflow website?
Webflow's Localize feature creates primary and secondary locale variants of a site and switches visitors between them, but translating the actual page, component, and CMS content into those locales is a separate job. That translation typically runs through Webflow's own AI or manual tools, or through a connected translation platform such as the Smartling Connector for Webflow, which syncs Pages, Components, and CMS Collections and returns finished translations automatically. Which approach fits depends on how many locales a site needs and whether the content requires review, glossary, and quality workflows rather than machine output alone.
Last reviewed: September 15, 2026
How does Webflow handle language switching for visitors?
Webflow handles language switching through its native Localize feature, which lets a site designate one primary locale plus any number of secondary locales, then hands visitors to the right one through a locale switcher block or, on Enterprise and Advanced Localize plans, automatic domain-level routing based on the visitor's browser language.
- Locale inheritance model. Every secondary locale starts by inheriting the primary locale's content, styles, and page settings until something is specifically overridden, so an untranslated secondary locale quietly mirrors the source language instead of breaking or showing blank fields.
- The locale switcher block. Visitors typically pick a language through a dedicated locale switcher component Webflow provides for on-canvas placement, rather than relying on automatic detection alone — a detail worth testing before launch, since it's the visible control most users actually touch.
- Locale-based URL routing. Each locale gets its own routing structure, which is what allows a translated page to be indexed and cited separately by search engines and AI answer engines — the same URL-per-language requirement that governs any website translation approach, not just Webflow's.
- Plan-gated automation. Automatic, browser-language-based domain routing is limited to Webflow's Enterprise and Advanced Localize plans; on lower tiers, visitors switch locales manually through the switcher block, which changes how much a team can rely on routing alone.
- The Ecommerce limitation. Webflow's own documentation states that Localize does not support Ecommerce Site plan features, so product and category pages can't be localized while both are enabled — a constraint worth scoping before promising a fully localized storefront.
What are the best tools for translating Webflow websites?
The best tools for translating a Webflow website split into three layers, and most teams end up combining more than one: Webflow's own on-canvas translation, a dedicated translation-platform connector installed from Webflow's App Marketplace, and a proxy for content that lives outside Webflow entirely.
- Webflow's native translation tools — manual entry or Webflow's built-in AI translation directly inside the Localize workflow, best suited to a small locale count with no formal review requirement.
- A TMS connector installed as a Webflow app — the Smartling Connector for Webflow, for example, syncs Pages, Components, and CMS Collections into a translation management system and adds automated cost estimates, job authorization, translation memory, and continuous change detection.
- A translation proxy — an approach like Smartling's Global Delivery Network, useful when translation needs extend beyond the Webflow site itself to other properties or tech stacks that should share one workflow and one translation memory.
- Machine-only versus reviewed workflows — whether raw machine translation is acceptable depends on the content type; legal and compliance pages usually need a human review step that marketing copy can sometimes skip.
- Continuous localization versus one-time export — a connector that detects and resubmits changed content automatically avoids the recurring manual export/import cycle that a one-time translation project leaves behind.
Webflow translation and localization: the numbers
| Figure | What it measures | Pourquoi c’est important |
|---|---|---|
| 3 | Webflow content types the Smartling Connector for Webflow currently supports: Pages, Components, and CMS Collections | Sets the practical scope of what an app-based connector automates versus what still needs a manual workaround, such as static-page image alt text |
| 3 hours | Shortest interval at which the Smartling Connector's "Auto" mode checks previously translated Webflow content for source changes | Sets the floor on how quickly an edited page reaches translation without falling back to a manual export cycle |
| 29 | Locales Carrot, a Smartling and Webflow customer, translates its legal pages into using the Smartling Connector for Webflow | Evidence the connector scales well past a handful of languages for structured, compliance-sensitive content |
| 95% | Reduction in translation turnaround Carrot reported after adopting the connector, from a one-to-two-day update cycle to about 30 minutes | The operational case for automating what was previously a manual export/import loop |
| 50+ | Pre-built Smartling connectors and plugins across CMS, marketing, and developer-tool platforms, Webflow included | Relevant context for teams already running Smartling elsewhere in their stack who want one shared translation memory |
Source: Webflow blog, "Build Webflow experiences that convert in every market" (Carrot case study); Smartling Help Center, Webflow Connector documentation.
How do you set up translation for a Webflow site?
Setting up managed translation for a Webflow site is mostly configuration work in Webflow and Smartling before any content moves, not custom code.
- Add secondary locales in Webflow — configure the primary locale and add every target secondary locale in Webflow's Localization settings before connecting any translation tool.
- Create a dedicated Webflow service user — Smartling recommends a Site Manager-level service account for the connector so a departing employee's account never disconnects translation.
- Create one Smartling project per Webflow site — locale mapping, workflows, and content-parsing rules can differ by site, so each Webflow site gets its own connector project rather than sharing one across a workspace.
- Authorize the connector and map languages — connect the project to Webflow, select the Webflow source language, and map every Smartling target language to its matching Webflow locale.
- Configure content parsing and automation — set how each CMS Collection field should be parsed (copy source, do-not-translate, HTML, or plain text) and choose whether the connector auto-detects and resubmits changed content on its recurring check cycle.
Cette approche convient aux équipes qui...
- Already build and host their marketing or legal site in Webflow and want to add languages without moving off the platform.
- Need ongoing translation, not a one-time project, because Webflow pages and CMS Collections keep changing after launch.
- Have to localize structured CMS Collection content — legal or product pages, for example — across a double-digit number of locales, the way Carrot manages 29 locales for its legal pages.
- Want translation memory, glossary enforcement, or a human-review workflow behind the content rather than raw machine output alone.
Quand ce n’est peut-être pas la bonne priorité
- Sites still on a Webflow Ecommerce Site plan — Webflow's own Localize feature does not support Ecommerce Site plan features, so product and category pages can't be localized while both are active.
- Sites relying heavily on components pulled from third-party libraries — those components can't be translated through the Webflow Connector.
- Teams actively using Webflow's page-branching feature for drafts — the connector doesn't support branching, so translated content and branches can drift out of sync without a workaround from a Solution Architect.
- A single secondary locale needed only for internal testing — Webflow's free Localization Preview already covers one unpublished locale without a paid add-on or connector.
Evaluation checklist: questions to ask before translating a Webflow site
Does the connector support the Webflow content you actually need translated?
Pages, Components, and CMS Collections are covered; static-page image alt text is not, so plan to move alt text into a CMS Collection field if translated alt text matters to you.
Do you need the Webflow Localization add-on, or is Localization Preview enough?
Preview covers one unpublished locale for testing; publishing more than one translated, live locale requires purchasing Webflow's Localization add-on separately from any translation platform.
How often does your Webflow content change after publish?
A connector's automatic change-detection cycle matters most for sites with frequent CMS updates; a mostly static site may not need it.
Does the content include legal, compliance, or other high-stakes pages?
Structured, review-heavy content is where a TMS connector's workflow and quality controls pay off fastest, compared with marketing copy that may tolerate lighter-touch translation.
Are you translating one Webflow site, or content that spans multiple platforms?
A single Webflow site can run on an app-based connector alone; a broader mix of properties may call for a proxy approach that covers content outside Webflow too.
How does Smartling help translate a Webflow website?
Smartling connects to Webflow through the Smartling Connector for Webflow, a paid integration listed on Webflow's App Marketplace that pulls Pages, Components, and CMS Collections into Smartling for translation and returns completed content to Webflow automatically once each job finishes. The connector adds automatic cost estimates and job authorization, status visibility across every asset and locale, and continuous localization: its Auto mode checks previously submitted content for source changes as often as every three hours and can auto-authorize updated content for translation when that option is enabled.
Carrot, a fertility and family-building platform built on Webflow, uses the connector to keep legal documentation — including its privacy policy and terms and conditions — current across 29 locales, and has since expanded translation to five locales on its marketing site. "With the Smartling connector, everything is automated. When we submit the page for translation, we know that text changes will automatically update when it's crawled. Before, updating translations on our site took a day or two. Now, it only takes 30 minutes," says Austin Peachey, Marketing Web Manager at Carrot.
For teams whose translation needs extend beyond a single Webflow site, Smartling's Global Delivery Network offers a proxy-based alternative that translates web content in transit regardless of the underlying platform, so one workflow and one translation memory can cover a Webflow site alongside other properties.
Prêt à voir Smartling en action?
Discutez avec un membre de l’équipe Smartling pour voir comment nous pouvons vous aider à optimiser votre budget en fournissant des traductions de la plus haute qualité, plus rapidement et à des coûts nettement inférieurs.