Webflow Localize: Tone and Formality, Finally Under Control Language by Language

A nuance that changes everything in multilingual translation

Have you ever received a machine translation that was grammatically flawless but... just sounded wrong? Too formal for a casual brand, or conversely too casual for a premium B2B site? That-s exactly the problem Webflow just tackled with its latest Localize update.

The starting point is simple but often overlooked: not all languages encode formality the same way. English, for instance, barely marks any register distinction in its grammar. French, German, Japanese, or Korean, on the other hand, require it through word choice, verb forms, or honorifics. The result: when you translate from a language that doesn-t specify this level, the AI has to guess. And it often guesses wrong, or defaults to something generic.

Tone suffers from a different issue: it does exist in your source content, but translation tends to neutralize it by trying to fit the target language-s rules. A brand with a strong voice, a bit edgy, or on the contrary very understated, often sees that personality evaporate during translation.

What Webflow is actually changing

With this update, you can now independently define, for each target language:

• A fixed formality level, useful for languages that require it structurally
• A specific tone, to prevent style from drifting toward a neutral middle ground
• A setting you can apply in bulk across several languages at once
• A translation preview before publishing, to check the result before it goes live

In practice, this means you can set a formal register for your Japanese version, keep a warm and direct tone in French, and go for a more relaxed approach in Spanish -- all from a single configuration panel, without having to go through a translation vendor for every adjustment.

This feature is limited to the Advanced Localize add-on or Enterprise plans that include Localize. A logical positioning: this is exactly the kind of fine-grained control that appeals to brands already committed to a serious multilingual strategy, not a single-language showcase site.

Mazette.co-s take

Let-s be direct: this is the kind of update that doesn-t make headlines, but solves a real agency problem. At Mazette.co, we work with brands rolling out their sites across multiple markets, and keeping brand voice consistent internationally is an ongoing battle. Until now, fixing a tone that fell flat or a mismatched formality level often meant going back and forth with a human translator, or manually reworking each item in the CMS.

Being able to set these parameters upfront, language by language, is a real game-changer when setting up a multilingual site. It also fits well with Webflow Localize-s overall philosophy: giving as much editorial control as possible without sacrificing the speed of automation.

The real win isn-t just saving time -- it-s no longer sacrificing your brand-s personality on the altar of machine translation.

Our only reservation: this level of nuance remains limited to Advanced Localize and Enterprise plans. Understandable from a business standpoint, but it leaves smaller teams behind -- teams who also have a brand voice worth defending internationally. We hope to see this fine-grained control gradually trickle down to more accessible plans.

If you-re preparing a redesign or a multilingual launch and want your brand to keep the same personality in every language, now is a good time to review your Localize setup with an expert eye. Our Webflow expertise covers exactly this kind of trade-off between automation and editorial standards.