Translate into other languages
One script in, validated audio out in every target language — translation, voices, and export in a single run.
One script, many languages: a Translator node turns each line into your target languages, and the Generator voices each one. One run delivers per-language audio — the pattern behind dubbing, localized courses, and multi-region ads.
1. Set the target languages
Edit the workflow’s Translator node (read → modify → write back):
Up to 30 targets per Translator (BCP-47 codes). No Translator in your workflow yet? Add one between Script and Generator on the canvas, or clone a template that has one.
2. Give each language a voice
Every target language needs an entry in the Generator’s voice_map. Two ways:
- Empty list — auto-route picks the best model for that language from Onepin’s benchmarks.
- Explicit assignment — you pick the voice and model; see Browse voices.
A target language with no voice_map entry fails at run start with a clear error — coverage is checked before anything is billed.
3. Run and collect
Run as usual — the export ZIP has one folder per language:
Validators score every language’s lines the same way — a Korean line that fails the accuracy bar is retried just like an English one.
Related
- Auto-route — how Onepin picks a model per language
- Translator — the node’s config
- Run a workflow — start, watch, download

