> For clean Markdown of any page, append `.md` to the page URL.
> For a complete documentation index, see https://docs.sarvam.ai/llms.txt.
> For full documentation content in one file, see https://docs.sarvam.ai/llms-full.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.sarvam.ai/_mcp/server.

# How to clone across languages

> Cross-lingual voice cloning with the Sarvam AI Voice Cloning API. Clone a voice in one language and have it speak any of the 13 supported Indian languages.

Sarvam's voice cloning model is cross-lingual: the language of the reference clip does not have to match the language of the synthesized output. You can clone an English voice and have it speak Hindi, or a Tamil reference drive Bengali output - the model preserves the speaker's timbre and identity while applying the phonetics and prosody of the target language.

## How it works

There is no source-language parameter. The model infers the speaker's characteristics from `ref_audio` alone, and `language_code` decides only the language of the output:

```bash
# English reference clip, Hindi output
curl -s -X POST "https://api.sarvam.ai/voices/clone" \
  -H "api-subscription-key: $SARVAM_API_KEY" \
  -F "text=नमस्ते, मैं आपकी कैसे मदद कर सकता हूँ?" \
  -F "language_code=hi-IN" \
  -F "ref_audio=@english_speaker.wav" \
  -F "ref_text=Hello, this is a sample reference recording."
```

The reference clip's language is never declared, so the same clip can drive outputs in every supported language. See [Supported Languages](/api/api-guides-tutorials/voice-cloning/supported-languages) for the full list.

## Why `ref_text` matters more here

`ref_text` is optional - when omitted, the API transcribes the reference clip automatically. But for cross-lingual generation, providing the actual transcript improves alignment and naturalness of the cloned output, especially when the reference and target languages differ.

```bash
# The transcript should match what is actually spoken in the clip
curl -s -X POST "https://api.sarvam.ai/voices/clone" \
  -H "api-subscription-key: $SARVAM_API_KEY" \
  -F "text=नमस्ते, मैं आपकी कैसे मदद कर सकता हूँ?" \
  -F "language_code=hi-IN" \
  -F "ref_audio=@english_speaker.wav" \
  -F "ref_text=Hello, this is a sample reference recording."
```

## Tips for cross-lingual cloning

#### Speaker accent transfers

A speaker with a strong regional accent in the reference will retain a hint of that accent in the cloned output. This is usually desirable - it preserves the speaker's identity. If you want a more neutral target-language accent, pick a reference clip from a speaker with less pronounced source-language inflection.

#### Script differences don't matter

The `text` field accepts native scripts (Devanagari, Tamil, Bengali, etc.) or code-mixed text. Always prefer the native script for the most accurate pronunciation. See [Supported Languages](/api/api-guides-tutorials/voice-cloning/supported-languages).

#### Reference language doesn't need to be English

Cross-lingual cloning works in any direction. A Tamil reference clip can drive Hindi, Bengali, or English generations equally well.

#### Longer references help cross-lingual quality

For cross-lingual generation, reference clips at the upper end of the recommended range (closer to 15 seconds than 10) give the model more speaker data to separate timbre from source-language phonetics.

## Next steps

#### [Prepare Reference Audio](/api/api-guides-tutorials/voice-cloning/how-to/prepare-reference-audio)

What makes a good reference clip.

#### [Supported Languages](/api/api-guides-tutorials/voice-cloning/supported-languages)

All language codes and native-script guidance.