2 translation models are available:
base: Fast, cover most use casesenhanced: Slower, but higher quality and with context awareness
Quickstart
To enable translation, settranslation to true on your request, and add a translation_config object :
Translation configuration fields
string[]
Target language codes for translation output. See the list of supported
language codes in >Supported
Languages.
enum["base", "enhanced"]
default:"base"
Specifies the translation model to be used.
boolean
default:true
Keep translated segments aligned with source segmentation. Use
true for subtitles/dubbing; set false for a more natural flow in the target language.- When true, the system attempts to match the translated segments (utterances, sentences) to the timing and structure of the original detected speech segments.
- When false, the translation might be more fluid or natural-sounding in the target language but could deviate from the original utterance segmentation.
boolean
default:true
Controls alignment with visual cues, specifically lip movements. When enabled
(default), uses an advanced lip synchronization algorithm that aligns
translated output with speaker’s lip movements using timestamps from lip
activity. \ This enhances viewing experience for dubbed content but may
occasionally merge distinct words into single objects to achieve better visual
sync. Set to
false if strict word-for-word mapping is required over visual
timing synchronization.boolean
default:true
Enable context-aware translation. When
true, the model leverages extra
context and style preferences for better accuracy. Turn off for purely literal
translations.string
Additional context to improve terminology, proper nouns, or disambiguation.
Effective with
Example:
context_adaptation: true. Example:
"Medical consultation between doctor and patient discussing cardiology"boolean
default:false
Prefer informal register when available; useful for chatty UX or youth
audiences. Especially relevant for languages with formal/informal distinctions
(e.g., French “tu/vous”, German “du/Sie”, Spanish “tú/usted”, Dutch “U/jij”).
Result
The transcription result will contain a"translation" key with the output of the model:
Best practices
- Set
target_languagesto only the languages you need. - Use
enhancedwithcontext_adaptationfor high-accuracy, domain-heavy content. - Provide a meaningful
contextto improve terminology and named entities. - Keep
match_original_utterances: truefor subtitles; set tofalsefor a more natural flow. - Pair with language detection and code switching when source language may vary.