OnlineDocTranslatorGuides

Answer

How Webflow Localization Works and What Translators Need to Know

Webflow Localization lets translators adapt a primary locale into secondary locales with per-locale URLs, hreflang, CMS fields, and asset swaps — here is how

Webflow Localization sits inside the broader site-localization lane that translators and agencies deliver every day, alongside the editorial, product, and service work covered in our How App Localization Works and What Clients Are Buying and Website Localization: What Translators and Agencies Actually Do on the Project guides. This page covers Webflow as one delivery lane: how the primary/secondary locale model works, what belongs in scope, and how handoff survives contact with a real CMS.

What is Webflow Localization and what does it actually give a translator?

Webflow Localization is a native feature of Webflow that adds secondary locales to a primary locale, exposing per-locale fields for static pages, CMS items, components, assets, slugs, and metadata, with hreflang and subdirectory routing emitted on publish. It is an editing surface, not a translation engine.

For a translator, that means three practical takeaways:

  • Every text field, image slot, slug, and SEO field becomes an override you edit under the secondary locale.
  • Structural elements — components, CMS schema, interactions — stay owned by the primary locale.
  • URL plumbing (subdirectories, hreflang, sitemap) is emitted by Webflow at publish time without translator intervention.

Which core features does Webflow Localization expose in the Designer?

The Webflow Designer exposes a locale switcher at the top of the canvas and per-locale overrides on every localizable field. The surface covers the editing points below.

  • Locale switcher that toggles the canvas between primary and secondary locales.
  • Per-locale text fields on static pages and CMS items.
  • Per-locale asset slots for images, videos, and files.
  • Per-locale slug fields on pages and CMS items.
  • Per-locale SEO title, meta description, and Open Graph image.
  • Per-locale alt text on image elements.
  • Per-locale visibility toggles on components, so a block can hide in one locale.
  • A localization panel that groups static pages and CMS collections under each secondary locale.

How does Webflow Localization differ from a translation plugin or third-party tool?

Native Webflow Localization writes directly into the primary site's data model rather than mirroring the DOM from outside. Secondary locales share one component library, one CMS schema, and one publish pipeline. Third-party translation layers sit outside the CMS and sync by API or script injection.

DimensionNative Webflow LocalizationThird-party translation layer
Data locationInside the Webflow site's own data modelExternal database synced via API or injected at runtime
Component modelOne shared library across all localesMirrored or re-rendered copy per locale
Publish pipelineSingle Webflow publish per environmentSeparate sync step on top of Webflow publish
hreflang + sitemapEmitted by Webflow at publishDepends on the external tool's rewriter
Translator surfaceDesigner + Webflow APIExternal UI + connector

How does the primary-vs-secondary locale model shape a translator's scope?

A Webflow site has one primary locale that owns source copy, structure, and defaults, and one or more secondary locales that inherit everything and override on a per-field basis. The translator's scope is every overridable field across static pages, CMS items, components, and assets — not just visible page copy. See our i18n: What Internationalization Means for Translators Producing Localized Builds guide for how this inheritance model compares to other platforms.

What belongs to the primary locale and cannot be overridden per locale?

Structural choices propagate from the primary locale to every secondary locale unchanged. Secondary locales inherit them and cannot fork them from the Designer.

  • The component tree and class system.
  • CMS collection schema (field names, types, reference relationships).
  • Interactions and animations.
  • Site-wide classes, breakpoints, and global styles.
  • Page tree and route structure (though slugs localize per page).

What can a secondary locale override field-by-field?

Secondary locales override content, not structure. Each item on the list below is a discrete per-locale edit the translator makes under the secondary locale.

  • Text content inside paragraphs, headings, buttons, and rich-text blocks.
  • Image, video, and file assets through per-locale asset slots.
  • Link URLs on buttons and text links.
  • Slugs on static pages and CMS items.
  • SEO titles, meta descriptions, and Open Graph images.
  • Alt text on images.
  • Component visibility (show/hide per locale).

How do you translate static pages, CMS items, components, and assets inside Webflow Localization?

Static pages translate inline in the Designer, CMS items translate field-by-field inside each item under the secondary locale, components translate once per instance, and assets localize by uploading a locale-specific file into the per-locale slot. The sequence below is the practical order of work.

  1. Confirm the primary locale is frozen for the sprint.
  2. Switch the Designer to the target secondary locale.
  3. Walk each static page top-to-bottom, overriding text, assets, slug, and SEO fields.
  4. Open each CMS collection under the secondary locale and translate items field-by-field.
  5. Verify component visibility per locale where layout must change.
  6. Upload localized assets into per-locale slots.
  7. Publish to staging and verify hreflang, slugs, and sitemap.

How are static pages translated in the Designer?

Switch to the secondary locale and edit text, SEO fields, and asset slots in place. Webflow stores the override against the element without duplicating the page tree, so one page object exists across all locales with per-locale values hanging off it.

How do you translate CMS items and CMS fields across locales?

CMS items translate one item at a time, field by field, under the secondary locale. Open the collection in the target locale, open the item, and overwrite each localizable field.

  • Slug.
  • SEO title and SEO description.
  • Rich-text and plain-text fields.
  • Image fields (per-locale asset slot).
  • Alt text on image fields.
  • Any custom text fields marked localizable in the schema.

This is where scope collapses on large sites. Translators should quote by field count × item count × locales, not page count — a 300-item knowledge base with eight localizable fields and three secondary locales is 7,200 field edits, not 300 "pages." See our Content Localization: How Translators and Agencies Produce It guide for how editorial content lanes feed into collections like these.

Is there a one-click 'translate all CMS items' button?

Native Webflow Localization has no single bulk "translate every CMS item" button in the Designer on lower plans. Bulk work goes through one of two paths: agentic AI translation on Enterprise, or a scripted Webflow API loop on any plan.

How do agencies automate CMS translation with the Webflow API?

Agencies script a loop that iterates collections, iterates items, iterates localizable fields, and PATCHes translated values back per locale. This is the only practical path for catalogs past a few hundred items.

  1. List all collections on the site via the API.
  2. For each collection, list all items.
  3. For each item, read every localizable field value in the primary locale.
  4. Send source strings to the translation engine, MT engine, or CAT tool.
  5. Receive translated strings back after human review.
  6. PATCH the item under the secondary locale with the translated field values.
  7. Verify the per-locale item in Webflow's localized collection view.

How does asset localization work for images, videos, and PDFs?

Each image, video, and file field exposes a per-locale asset slot; uploading a locale-specific file replaces the primary asset for that locale only. Screenshots, infographics, product shots with on-image text, and downloadable PDFs all swap through this mechanism. The primary asset stays as the fallback for locales that do not upload a replacement.

How does Webflow Localization handle URLs, slugs, hreflang, and the locale switcher?

Webflow publishes each secondary locale under its own subdirectory, localizes slugs per page and per CMS item, emits hreflang tags on every page, and exposes a locale switcher component. URL plumbing is automatic once locales are configured. For how these emissions feed ranking, see our Localization SEO: How Translators Make Localized Pages Rank guide.

How does Webflow emit hreflang tags across locales?

On publish, Webflow writes hreflang link tags into every page's head referencing every alternate, including the page itself. It uses the ISO 639-1 language code and, when the locale carries a region, the ISO 3166-1 country code. A locale configured as Mexican Spanish emits hreflang="es-MX"; a generic German locale emits hreflang="de". The self-referencing alternate is included, which is correct hreflang behavior.

How do localized slugs and the sitemap behave?

Each secondary locale can carry its own slug per static page and per CMS item, and Webflow regenerates the sitemap at publish. The resulting URL structure looks like:

Primary locale URLSecondary locale URLLocalized slug
/pricing/es-mx/preciosyes
/blog/post-title/de/blog/beitrags-titelyes
/about/fr/a-proposyes

The sitemap lists each locale's URLs under its subdirectory and pairs them in the hreflang map.

How does the locale switcher route visitors between languages?

The Webflow locale switcher component lists published locales and links to the current page's alternate URL. On Advanced and Enterprise plans, Webflow can auto-route visitors by browser language preference at the edge, so a visitor with Accept-Language: fr landing on /pricing redirects to /fr/tarifs.

Pricing

What does Webflow Localization cost, and which deliverables does each plan unlock?

Webflow Localization is sold as a site add-on in Essential, Advanced, and Enterprise tiers that progressively unlock locale count, asset localization, per-locale slugs, visitor routing, and agentic AI translation. The plan the client holds dictates which deliverables an agency can commit to in a statement of work.

Which localization capabilities belong to Essential, Advanced, and Enterprise?

Each tier unlocks a distinct deliverable set. The capability map below is what translators scope against.

CapabilityEssentialAdvancedEnterprise
Secondary locale countLow ceiling (small number)Higher ceilingHighest ceiling, negotiated
Text translation (static + CMS)YesYesYes
Asset localization (per-locale images/videos/files)NoYesYes
Per-locale slugsNoYesYes
Custom URL routing per localeNoYesYes
Visitor routing by browser languageNoYesYes
Agentic AI translation + TMNoLimitedYes
Publishing SLANoNoYes

How should an agency map Webflow plan tiers onto a translator deliverables table?

Agencies should refuse scope the client's current plan does not support and quote tier-matched deliverables. The translator-side map below is what belongs in the proposal.

PlanDeliverables agency can commit toDeliverables to decline or escalate
EssentialText-only translation of static pages and CMS items; SEO fields in body language; hreflang verifiedLocalized assets, localized slugs, auto-routing
AdvancedFull visual parity: localized assets, per-locale slugs, SEO metadata, visitor routing, custom URL structureContinuous publishing SLA, TM-leveraged bulk CMS translation at scale
EnterpriseContinuous or AI-assisted multi-locale publishing, agentic translation workflows, TM reuse, higher locale countNone platform-side; constraints become linguistic

Our Localisation Strategy: How Agencies Plan, Price, and Deliver Multi-Locale Programs guide covers how this plan-tier map slots into a multi-lane program.

Get a quote

Where does Webflow Localization fit next to CAT tools, TMS platforms, and the Webflow API?

Webflow Localization is the per-locale editing surface; CAT tools hold translation memory and term bases; a TMS orchestrates the round-trip; the Webflow API is the glue. No single tool does all four jobs well on a mid-sized site.

LayerRoleExamples
CAT toolSegmentation, TM, term base, QA checksmemoQ, Trados, Phrase
TMSProject orchestration, string sync, review workflowLokalise, Phrase TMS
Webflow APIProgrammatic PATCH of translated values per localeWebflow Data API
Webflow DesignerVisual QA, override of exceptions, publishWebflow Localization panel

How do translators route Webflow content through a CAT tool?

Translators export source strings via the Webflow API or a TMS connector, segment in the CAT tool against the project TM and term base, review, and PATCH reviewed strings back to the matching locale fields. The CAT tool is where linguistic work happens; Webflow is where it lands.

  1. Pull source strings per collection and per page via the Webflow API.
  2. Convert to the CAT tool's bilingual format (XLIFF or vendor-native).
  3. Pre-translate against TM and run MT where allowed.
  4. Have the translator revise and the reviewer sign off inside the CAT tool.
  5. Export reviewed target strings.
  6. Map target strings to Webflow field IDs and PATCH per locale.
  7. Visual-QA the pages in the Webflow Designer under the secondary locale.

Native TM lives inside Enterprise agentic translation; outside Enterprise, TM lives in the CAT tool or TMS and is applied before the API push.

When does an agency move from native Webflow Localization to Lokalise, Phrase, or a custom pipeline?

Move off native Designer editing when scale breaks the field-by-field model. The four triggers below are the decision rule.

  • Locale count exceeds roughly five secondary locales.
  • CMS item count passes the point where in-Designer editing stops scaling (practical ceiling around a few hundred items per collection).
  • The client requires TM leverage reporting (fuzzy match percentages, repetition analysis).
  • Continuous publishing SLAs demand automated string sync between source changes and locale updates.

What are the limitations of Webflow Localization translators should flag before quoting?

Known constraints include per-field CMS editing on lower plans, limited rich-text structural overrides, component-visibility quirks when layout must change per locale, RTL layout work that still needs manual CSS, and plan-gated features that silently cap scope. Each belongs in the proposal as a flagged assumption.

What breaks or slows down at scale?

Field-by-field editing becomes untenable past a few hundred CMS items. The practical pain points to flag:

  • Assets must be uploaded one slot at a time; no bulk asset swap per locale.
  • Rich-text fields cannot restructure (reorder headings, change embed types) per locale.
  • Component visibility toggles help, but layout changes often need per-locale component variants.
  • Right-to-left layouts require manual CSS adjustments and per-locale component variants; Webflow does not auto-mirror layout for Arabic or Hebrew.
  • Script-specific font loading (Arabic, Hebrew, CJK) needs explicit per-locale font declarations.
  • Translator hours scale linearly with item count unless a scripted Webflow API loop is in place.

How should agencies price platform-risk and migration conversations?

Agencies should price the engagement around transferable deliverables, not Webflow-specific overrides. When clients weigh migration from Webflow to a custom AI-assisted stack, the artifacts below survive the platform change and anchor the quote.

  • Clean source files per locale.
  • Translation memory (TMX export).
  • Term base (TBX or glossary CSV).
  • hreflang map and locale/slug matrix as a standalone spreadsheet.
  • Asset localization inventory (which assets swap, in which locales, from which source files).
  • Style guide and QA checklist independent of Webflow.

What does a translator's pre-handoff readiness checklist for Webflow Localization look like?

Before translation starts, verify primary locale freeze, secondary locale creation, component conversion, localizable CMS fields, flagged assets, and a scoped API key. Skip any item and the project pays for it in rework.

  1. Primary locale is content-frozen for the translation sprint; new copy goes into a parked branch.
  2. Secondary locales are created in Webflow with correct ISO 639-1 / ISO 3166-1 codes.
  3. Static copies of blocks have been converted to real components so one edit propagates.
  4. CMS collections expose slug, SEO title, SEO description, and alt text as localizable fields.
  5. Assets requiring swap per locale are flagged in a localization inventory.
  6. Component visibility and per-locale layout exceptions are documented.
  7. Webflow API key is scoped to the correct site with read + write permission on CMS.
  8. TM and term base are prepared in the CAT tool or TMS.
  9. Style guide for each target locale is agreed with the client.
  10. Staging environment is available for visual QA before production publish.

What does the translator receive, and what do they return?

The translator receives Designer access or an API-exported bundle plus the term base and style guide, and returns per-locale field updates ready to publish. The return bundle includes translated text, localized slugs, localized SEO metadata, localized assets, and a QA log tying each change to its Webflow field ID. Our Service Localization: What Translators and Agencies Actually Deliver guide frames this handoff inside the agency's wider service contract.

The questions below cover the issues translators and agencies raise most often when scoping a Webflow handoff: CMS automation, cost-to-value, plan limits, and alternatives to native editing.

Frequently asked questions

How does Webflow localization work?

Webflow Localization lets you create locale-specific versions of a site by duplicating content into separate locale slots and translating each field individually. You set a primary locale, add secondary locales (e.g., French, German), and Webflow stores translated strings per locale for both static Designer text and CMS fields. Editors can switch between locales inside the Webflow Editor or via the API. Machine translation is offered as a starting point, but human review — and for certified outputs, professional translator sign-off — is still required to produce accurate, publishable content.

How do I translate CMS items in Webflow localization?

CMS item translation in Webflow requires opening each Collection item individually and entering translated content field-by-field in the target locale. There is no bulk-export-and-reimport workflow natively; translators must either work inside the Webflow Editor or use the Webflow CMS API to push translated strings programmatically. In practice, agencies handling large CMS collections build custom scripts or use third-party connectors to extract source strings, run them through a CAT tool or first-draft translation service, then write translated values back via the API before a human translator reviews and approves each entry.

Does Webflow localization support CMS content or just static pages?

Webflow Localization supports both static Designer content and CMS Collection items, but CMS support has meaningful constraints. As of the current feature set, not every CMS field type is fully localizable — Reference and Multi-Reference fields, for example, have limited locale-specific handling. Each CMS item must be translated per locale rather than inheriting from the primary, meaning large catalogues multiply the editorial workload significantly. Translators working on Webflow-built sites should confirm with the client which field types are in use before scoping a project.

Can you automate translation of Webflow CMS fields across locales?

Yes, CMS field translation can be automated via the Webflow CMS API combined with an external translation pipeline. The typical workflow extracts source-locale field values through API GET requests, passes them to a translation service (machine translation for a first draft, then human post-editing), and writes the translated strings back with PATCH requests on each CMS item per locale. Fully automated pipelines without human review are risky for certified or regulated content; a translator still needs to verify accuracy, tone, and terminology before the content is published or certified.

What are the limitations of Webflow's built-in localization for CMS?

Webflow's built-in localization has several practical limitations for CMS-heavy projects: no native bulk string export (XLIFF, CSV, or similar), limited localizability of Reference and Multi-Reference fields, no Translation Memory or glossary management inside the platform, and no built-in workflow for translator review or approval. The Editor-based translation interface is designed for content editors, not professional translators using CAT tools. Agencies typically work around these gaps by combining the CMS API with external translation management systems or first-draft tools to keep per-word costs and turnaround times manageable.

What is localization in simple words?

Localization means adapting content so it feels native to a specific language, region, and culture — not just translating the words. Beyond language, localization covers date and number formats, currency symbols, images, legal disclaimers, and tone of voice. For professional translators, localization is a step beyond straight translation: it requires understanding the target market's conventions and expectations. On a Webflow site, this means every CMS field, alt text, form label, and metadata string may need locale-specific treatment, not just a word-for-word swap.

Is Webflow localization worth the cost?

Whether Webflow Localization is worth the cost depends on the site's scale and the client's existing Webflow investment. The feature is gated behind higher-tier plans, adding a meaningful monthly cost on top of the base site plan. For clients already on Webflow who need two to five locales with moderate CMS volume, it can be more cost-effective than migrating to a different CMS. For large multilingual catalogues with dozens of locales, the per-item manual effort and API workarounds often make purpose-built localization platforms or headless CMS alternatives more economical in the long run.

Related