Translate a playlist or deal room
Translate a playlist or deal room
Overview
A playlist or deal room can be translated into additional languages so a buyer sees the hub — page copy, section text, button labels, entity names and descriptions, the Action Plan, and the player's own interface — in their own language. Walnut generates the translations with AI, you can review and edit them inline, and the viewer picks the language from a switcher in the share link.
Translations live alongside the source: switching a reader (or an editor) to another language overlays the translated text on top of the same hub, and anything not yet translated falls back to the source.
Snapshot 📸
Feature status: Generally available · AI generation of translations consumes AI credits Role access: Anyone who can edit the playlist or deal room Location: Playlist or deal room editor → language switcher in the top toolbar; viewer language picker on the share link Scope: The whole hub — pages, sections, text and button elements, entity names and descriptions, the Mutual Action Plan, and the player interface strings
What gets translated
Adding a language translates every text field of the hub into that language:
- Playlist or deal room title and description.
- Page names and the text on every page.
- Text elements inside sections (rich text, formatting preserved).
- Button labels.
- Entity names and descriptions — the content tiles on a page.
- Mutual Action Plan stage names, task names, and task descriptions.
- Player interface text — strings like "Back to playlist" that come from the player chrome itself, translated once per language and reused across every hub.
Images, embeds, and the structure of the hub are untouched — only text is translated.
Add a language
- Open the playlist or deal room in the editor.
- In the top toolbar, click the language switcher (shows the current language code and name).
- Click Add a language and pick one from the list.
- Walnut starts translating. A progress label on the switcher (for example, "FR: Translating… 24 of 86") shows the run as it goes, and the row's status updates automatically.
When the first run completes, viewers who load the hub in that language see the translated version. Until a language's first run is finished, it is marked Not translated yet.
Translate from AI Mode
When AI Mode is open, Add a language and the per-row Translate / Fix actions draft a prompt into the AI Mode composer instead of running the mutation directly. Send the prompt to kick off the translation from inside the conversation.
Change the source language
The source language is the language the hub is authored in — the one every other language is translated from. To change it:
- Open the language switcher.
- On the row of the current source, choose Change source language.
- Pick the new source from the list.
A language that is already added to the hub cannot be set as the source — remove it first.
Review and edit a translation inline
Pick an added language in the switcher to view the hub in that language. The canvas renders the translated text in place, and editing works exactly like editing the source:
- Click any translated string on the canvas to edit it. The change saves onto that language only; the source and other languages stay untouched.
- Formatting is limited to the formatting the source already uses, and only safe link schemes (
http,https,mailto) are accepted. - A banner reminds you: "Text you edit now changes this translation only. Switch back to the source language for anything else."
- Switch back to the source to edit structure, add or remove sections, or change styling.
Status markers
Each language row in the switcher shows how fresh the translation is:
- Up to date — every field matches its source.
- Out of date — source changed. Fields the author edited in the source language since the last run show the source text and a count of how many fields need re-translating.
- Failed. Fields the AI couldn't translate on the last run; they fall back to the source. Running again retries them.
Click Fix on a row to run just the out-of-date and failed fields. Click Translate on a never-translated row to run its first pass.
Right-to-left languages
A translation into a right-to-left language (such as Arabic or Hebrew) automatically mirrors the hub: each line's alignment and each section's alignment flips between left and right (center and justify stay). Editing an aligned line in the mirrored view saves the author's intended alignment on the source side.
Share with a language picker
When you copy a share link to a hub that has published languages, Walnut shows a language options popover beside the copy button:
- Language — pick which language the link opens in. The source is labelled "(original)".
- Let viewers change language — a switch. On, the viewer sees a language picker in the player top bar and can switch between every published language. Off, the link opens in the chosen language and no picker is shown.
The two settings are encoded as URL parameters on the copied link:
language=XX— the ISO code of the language the hub opens in. Omitted when the chosen language is the source.hideLanguagePicker=true— hides the viewer's language picker.
The viewer picker only appears when the hub has more than one published language.
Remove a language
Open the switcher, hover a language row, and choose Remove.
- A language that was never translated is simply taken off the hub.
- A language with saved translations prompts you to confirm: removing it deletes every translation stored for that language, and viewers can no longer switch to it. Translating it again later is a new AI run.
Removing the language a viewer is currently reading in sends the editor back to the source.
Publishing
Translations are only served from a published snapshot. After a translation run finishes, or after inline edits to a translation, publish the hub to make the change reach viewers. The share link's language options show only languages that are in the published snapshot — a language that is still translating, or that has never been published, is not offered.
AI credit cost
Generating translations with AI uses AI credits. Running the first pass on a new language charges for every translated field; a Fix run charges only for the fields that are out of date or failed. Manual edits to a translation do not consume credits.
Admins can review AI usage in the AI Control Center under company settings.
FAQs
Do I have to recreate the hub to add a language? No. Translations live on top of the source hub. Add a language and Walnut generates the translated version in place.
What does a viewer see for a field that isn't translated yet? The source text. Fall-back to the source is automatic, per field.
Can I edit a translated string without touching the source? Yes. Switch the editor to that language and edit the string on the canvas. The edit saves on that language only.
When I edit the source, what happens to translations? Fields whose source changed are marked out of date in every language. The old translation keeps showing until you re-run or edit it. Use Fix on the language row to re-translate just those fields.
Does the player interface get translated too? Yes. Strings like "Back to playlist" come from a built-in catalogue that Walnut translates once per language and reuses across every hub.
Which languages are supported? The same language list Walnut uses for guide and screen translations on your plan. There is a per-plan cap on how many languages a single hub can have.
Can I pick which language a share link opens in? Yes. When the hub has published languages, copying the link opens a Language picker and a Let viewers change language switch. The settings are encoded on the URL.