Skip to main content

Translate text variables per language

Turn on Translate this value for a text variable so AI translates its default and preset values into each of the demo's languages, override it per value, and edit a translation by hand.

Updated Nov 12, 2026

Translate text variables per language

Overview​

For templates that are published in more than one language, Walnut can translate a text variable's value with AI, so one demo serves every language on the template without you maintaining a separate value per language.

Walnut already translates everything your product captured on screen (see Translate captured screen text across languages) and your guide steps (see Translate guides). Variable translation covers the dynamic text you inserted, such as an industry label or a role title.

Translation is an opt-in per variable, and only applies to text variables. Date, image, and color variables are not translated.


Why this matters​

A variable like {{industry}} with the value "Healthcare" would otherwise render the same way for every viewer, even on a German demo. With Translate this value turned on, a German viewer sees the German translation instead.

The checkbox is off by default on every text variable. That is usually what you want for names and brands, such as the prospect's company name or a product name, which normally shouldn't be translated. Turn it on for values that are ordinary words.


How it works​

  • Walnut translates the variable's default value and the values set on presets.
  • Values supplied at demo time from a connected CRM, URL parameter, or lead form are shown as typed in every language.
  • A machine translation never overwrites a value you edited by hand for a specific language.
  • When the source value changes, the stored machine translation is refreshed the next time the demo is published or the language is re-added. A translation you edited by hand is not refreshed.

Turn on translation for a text variable​

  1. Open the text variable in the editor.
  2. Tick the Translate this value checkbox. The description reads "AI translates it into each of the demo's languages."
  3. Use the Preview panel on the right to switch between the template's languages and check how the default value reads in each one.
  4. Click Done to save.

If a language cannot be translated, the preview falls back to the value as typed and shows "Couldn't translate. The value shows as typed."

When you turn the checkbox off again, the stored machine translations for that variable are dropped. Manual translations you wrote by hand are kept.


Override translation on a specific value​

When you create a demo or build a preset, each text value for a translatable variable carries its own Translate with AI into the demo's languages checkbox, so you can opt one value out without changing the variable itself.

  • If the value you entered matches the variable's default, Walnut shows "Default is translated into the demo's languages" instead of the checkbox. The default's translations are already in use.
  • Untick the checkbox on a specific value to keep it as typed in every language. Walnut drops any machine translations it had stored for that value.
  • Tick it to translate that value into every language on the template.

Edit a translation by hand​

Switch the Preview language in the variable editor (or on a preset or demo value) to review the AI translation and, if needed, type your own version in that language. A hand-edited translation is pinned: later AI runs leave it alone, and it is not refreshed when the source value changes.


FAQs​

Is translation on for my existing text variables?​

No. Translate this value is off by default on every text variable. Turn it on for each variable you want translated.

Can I translate image variables too?​

No. Only text variables can be translated. Date, image, and color variables stay the same across every language.

What about values that come from my CRM, a URL parameter, or a lead form?​

They are shown exactly as typed in every language. Only the default value and preset values are translated.

What happens if I change the source value?​

The stored machine translation is refreshed the next time the demo is published or the language is re-added. Translations you edited by hand stay as you wrote them.


Was this helpful?