Webflow | Localize Adds Tone and Formality Controls by Language
Webflow added language-specific tone and formality controls to Localize on July 22, 2026. Website teams can now define how AI-translated content should sound in each target language, helping brand voice and forms of address remain more consistent across multilingual pages.
Webflow gives localized websites more control over their voice
AI translation normally attempts to infer writing style from the source content. This can become unreliable when the original language does not express information required by the target language, such as the difference between formal and informal forms of address.
Tone can also become less distinctive during translation as phrasing moves toward a neutral style. Webflow's new controls let teams replace that automatic interpretation with fixed language settings, making it easier to preserve the intended personality of product pages, editorial content, interfaces, and other website copy.
Tone and formality can be configured independently
Formality controls vocabulary, sentence structure, directness, and forms of address. Teams can leave it on Auto or select Casual, Neutral, or Formal. This is particularly relevant when translating into languages such as French, German, Japanese, Korean, or Spanish, where the relationship between the website and its reader may affect word choice.
Tone describes the broader voice of the translation. Available settings include Auto, Warm, Confident, Playful, and Serious. A brand can therefore keep a friendly tone while choosing a more respectful register, or use a confident voice without forcing every language to copy the original wording literally.
Bulk controls and previews support multilingual publishing
Designers and content teams can configure one target language or select several languages and apply the same settings in bulk. Target languages can also be prepared before their related site locales are added, allowing translation preferences to be organized earlier in the localization workflow.
The translation preview panel accepts sample text and shows how the selected settings affect the result. This gives editors a practical way to compare registers and voices before translating more website content, especially when several markets share the same brand guidelines but require different linguistic treatment.
Existing translations and complex language registers still need review
Changing a target language setting only affects translations created afterward. Existing localized content is not translated again automatically, so teams must review or update older pages separately if they want the new tone and formality rules applied throughout the site.
The available presets also simplify languages with more than two formality levels. Japanese and Korean, for example, are mapped to the closest supported setting. Previewing results and asking a fluent editor to review important marketing, support, legal, or transactional content remains necessary before publication.
IMPORTANT: Target language settings require the Localize Advanced add-on or an Enterprise plan with Localize. They apply only to future translations and do not automatically update existing localized content.{alertWarning}
Daisuki's Take: What This Means for Web Designers
This update treats localization as part of a website's editorial design rather than a simple word replacement process. Voice affects how a navigation label, call to action, product explanation, or support message feels, so controlling it by language can strengthen the consistency of a multilingual experience.
We would use the presets as a clear starting point instead of assuming one setting can solve every content situation. A playful marketing page and a serious account notice may need different treatment even when they belong to the same language and website.
For template creators and international web teams, the most useful workflow is to define language preferences, test representative content in the preview, and document the choices for future editors. Human review remains the final step when cultural context, trust, or precise wording affects the visitor's experience.
Sources and Recommended Links
- Set tone and formality for each target language | Webflow Official Updates
- Target language settings for translations | Webflow Official Help Center
