Supported languages
Tavus supports 43 languages for spoken interaction. By default,tavus-auto intelligently routes each conversation to the best TTS provider for that language.
Language availability also depends on your selected STT model. Some models support a subset of these languages. See the STT layer configuration for per-model language breakdowns.
- English (en)
- French (fr)
- German (de)
- Spanish (es)
- Portuguese (pt)
- Chinese (zh)
- Japanese (ja)
- Hindi (hi)
- Italian (it)
- Korean (ko)
- Dutch (nl)
- Polish (pl)
- Russian (ru)
- Swedish (sv)
- Turkish (tr)
- Tagalog (tl)
- Bulgarian (bg)
- Romanian (ro)
- Arabic (ar)
- Czech (cs)
- Greek (el)
- Finnish (fi)
- Croatian (hr)
- Malay (ms)
- Slovak (sk)
- Danish (da)
- Tamil (ta)
- Ukrainian (uk)
- Hungarian (hu)
- Norwegian (no)
- Vietnamese (vi)
- Bengali (bn)
- Thai (th)
- Hebrew (he)
- Georgian (ka)
- Indonesian (id)
- Telugu (te)
- Gujarati (gu)
- Kannada (kn)
- Malayalam (ml)
- Marathi (mr)
- Punjabi (pa)
- Swahili (sw)
Cartesia
ElevenLabs
By default, Tavus uses the
tavus-auto TTS engine. It intelligently routes the conversation to the best TTS provider for that language. Only set tts_engine explicitly when you need a specific provider.Setting the Conversation Language
To specify a language, use theproperties.language parameter in the Create Conversation. You must use the full language name, not a language code.
cURL
Language names must match exactly with those supported by the selected TTS engine.
Smart Language Detection
To automatically detect the participant’s spoken language throughout the conversation, setlanguage to multilingual when creating the conversation:
cURL
For the highest accuracy, we recommend setting a specific language rather than using
multilingual. Smart Language Detection works best as a fallback when the participant’s language is unknown ahead of time.Additional language support via Azure
There may be additional language support via Azure if you need a language that is not covered above. Use Azure only as a fallback in that case - prefer the defaulttavus-auto routing whenever your language is already supported.
For the latest supported languages, check Azure Speech TTS language support.
Unlike Cartesia and ElevenLabs (which Tavus hosts for you), Azure requires you to bring your own Azure Speech API key:
- Set
tts_enginetoazureexplicitly on the PAL’s TTS layer. - Provide your own Azure Speech resource
api_key. The resource must be in the East US region (Tavus synthesizes viaeastus; a key from another region returns an authentication error). Setexternal_voice_idto any standard Azure neural voice available in East US (for examplede-DE-KatjaNeural); Custom Neural Voices must be deployed in that same resource.
Any Azure voice can speak any supported language, carrying the voice’s own accent. For a natural accent, pick a voice whose locale matches your target language (e.g. a
de-DE-* voice for German), or use one of Azure’s *MultilingualNeural voices.
