To clone your voice in other languages, plan on 1 clone per language, because the language is set when the clone is created and not switched afterward. You then type the script in that language yourself, since VocalLab doesn't translate text for speech. Those 2 facts shape everything else in this guide.
The Studio model reads text in 200+ languages, so the ceiling is high. What decides the result is the sample you give the clone, the quality of the translation you paste in, and how you handle names and numbers. We'll go through each, then cover the case where dubbing is the better route.
Multilingual voice cloning starts at creation
When you set up a clone you pick its language from a searchable list of 200+ options, or choose Auto-detect from sample and let the Studio work it out. 15 of those languages, including English, Spanish, Portuguese, French, German, Italian, Dutch, Arabic and Chinese, have a full voice catalogue behind them. The rest are marked Experimental: cloning works, but quality varies more from one sample to the next. Our clone voice in multiple languages page has the details on that list.
The practical rule is short. If you want your voice in Spanish, record 15 to 30 seconds of Spanish (30 is recommended), create the clone with Spanish as its language, and keep it separate from your English one. Two languages means 2 clones, three means 3. That's a real constraint on the Free and Lite plans, which each hold 1 clone at a time. Pro holds 10 and Max holds 200.
| Plan | Clones held | Languages you can keep live |
|---|---|---|
| Free | 1 (lifetime slot) | 1 |
| Lite, $9 a month | 1 | 1 at a time |
| Pro, $24 a month | 10 | Up to 10 |
| Max, $299 a month | 200 | Up to 200 |
Translate the script for the AI voice yourself
A cloned voice speaks the words you give it. Give it English and you get English; give it Spanish text and you get Spanish. VocalLab doesn't turn your English script into Spanish on the text-to-speech side, so you need a translation in hand before you generate anything.
How you get that translation is your call, and it's where quality is won or lost. A professional translator is the safest option for anything public. A machine translation that a native speaker has read through is the realistic middle path. A raw machine translation pasted straight in is the one we'd avoid, because the voice will read a stiff or wrong sentence just as confidently as a good one. Fluent nonsense is still nonsense.
Write for the ear, not the page. Use shorter sentences, no nested clauses, and the contractions and fillers a native speaker would use. A line that reads fine on paper can be a mouthful aloud, and you'll hear it on the first take.
A workable routine for a 1,000-word script, which runs about 7 minutes at 150 words a minute: translate it, have a native speaker read the translation aloud once, mark every sentence that made them stumble, and fix those before you generate. That review costs time, not points. Regenerating a bad 1,000-word script costs ⌈6,000 ÷ 17⌉ = 353 points each time you do it, assuming about 6 characters per word including spaces.
Accent carry-over is normal
Expect your clone to sound like you, and that includes how you sound. If your sample was English with a Dublin accent and you generate German from a clone made in English, you should expect traces of the Dublin in the German. The clone learned from 1 voice and 1 way of speaking, and it can't borrow a native speaker's habits it never heard.
The best fix is the one in the section above: make the clone from a sample in the target language, read by you in that language. If you don't speak it, the alternative is a library voice that does. The Spanish smooth, clear female voice is one example built for Spanish narration, and you'll hear the difference from an English-sample clone straight away.
You can also describe an accent instead of cloning one. The wording that moves it is covered in our guide to describing accents for AI voice, which is worth a read before you write a prompt. Note that Voice Design prompts are written in English, whatever accent you're after.
Don't over-promise. A light accent reads as authentic to many listeners, particularly in educational and explainer content. A heavy one on a localized ad is a different story, and a native listener should sign off before you publish.
Names, numbers and other things that go wrong
Names trip voices first. A brand name, a person's name or a place that sits outside the language you're generating in will often be read with the target language's rules. If your product is called a made-up word, test it alone, 3 or 4 times, before you build a script around it.
- Generate the name by itself. One short line with just the brand or person, listened to twice, tells you more than 10 minutes of the full script.
- Respell it if it's wrong. Write the name the way it sounds in the target language, with hyphens or accents where needed, and keep the original spelling in your captions.
- Write numbers out. Dates and prices are read differently in each language. Spell them in words in the script, in the target language.
- Keep a short glossary. A table of 10 or 20 names with their working respellings saves you the same fix on every later video.
What a script costs in another language
Points are charged from characters, as ⌈characters ÷ 17⌉ in the app. A 1,700-character script costs 100 points whatever the language. But the same message takes a different number of characters in each language, so the bill moves with it. If a message is 1,700 characters in English and 2,000 in German, the German version costs ⌈2,000 ÷ 17⌉ = 118 points. Scripts in languages that pack more meaning into fewer characters cost less.
The length of the finished audio won't follow the character count exactly either, so check the first generation rather than doing arithmetic in your head. Creating the clone itself costs no points on any plan.
When you have a video, dub it instead
If your end product is a video, skip the manual route. Dubbing in the Studio is the exception to the translate-it-yourself rule: it transcribes the video, produces a translated script fitted to each line's time slot, and lets you edit that text before anything is voiced. The target list is shorter than the full 200+, at 15 target languages for now, and any voice can speak them, including your own clone. So here you don't need 1 clone per language.
Dubbing is available on paid plans, uploading is free, and the price is shown before you analyze. The AI dubbing voice generator page walks through the steps. Use manual cloning plus your own translation for audio-only work, courses, audiobooks or any script you want to tune by hand.
Want to hear a multilingual voice before you commit to recording? Try the multilingual voice generator with a library voice, then compare your clone against it. Some library voices, such as the lucid male explainer, list English, Arabic and German side by side, which makes them a handy reference.
Frequently asked questions
Can one clone speak several languages?
The language is set when you create a clone, so the reliable approach is 1 clone per language, each made from a sample in that language. For video, dubbing lets any voice, including your clone, speak the target language.
Does VocalLab translate my script for me?
Not for text to speech. You supply the script in the language you want spoken. Video dubbing is the exception: it produces a translated script that you review and edit before voicing.
Will my clone keep my accent in another language?
Expect some carry-over. The clone learned how you speak, so traces of your accent can appear in other languages. Creating the clone from a sample in the target language gives the best result.
How many languages can I clone in?
The Studio model covers 200+ languages. Fifteen of them have a full voice catalogue and the rest are marked Experimental, so quality varies more. Auto-detect from sample is available when you're unsure.
