Guide · Languages
Published September 12, 2026

| Layer | What it covers | Where you set it |
|---|---|---|
| Interface | Menus, buttons, wizard steps, error messages, emails — 15 languages | Language menu in the top bar; first visit follows your browser |
| Working documents | Script analysis, episode outlines, storyboard scripts, character and scene descriptions | Follows the interface language automatically; edits you make in your language sync back to the production script |
| Spoken dialogue | The lines the cast says out loud in the generated clips | Step 1 of the project wizard, "Dialogue language", before the script is parsed |
Most questions about "multilingual AI video" are really about the third layer. A translated interface is table stakes; a translated storyboard is convenient; what sells a series in a new market is a cast that speaks the audience's language natively, with the timing and mouth shapes of that language, not a voice track glued on top of an English performance.
| Language | Dialogue quality | Notes |
|---|---|---|
| English, Chinese | Baseline | The production languages; every sample series on this site uses one of them |
| Portuguese, Korean, Spanish, Japanese, Indonesian | Native-level | Verified with native speakers on multi-line scenes |
| Russian, French, Italian, Dutch, Turkish, Cantonese | Native-level | Cantonese is available for dialogue only; the interface uses the Chinese dictionary |
| Arabic | Good | Occasional single-word pronunciation flaws; regenerate the segment if one lands on a key line |
| German, Ukrainian | Good, with a caveat | Long sentences can produce a mispronounced verb ending or past-tense form; the storyboard prompt already keeps lines short for these two, and a flagged segment can be regenerated on its own |
These are working observations from SceneMixer's own test scenes, not vendor claims. When a line comes out wrong, the fix is local: rewrite that segment's script or simply regenerate it, and you pay only for that segment.
A script written for one market often needs more than translation. SceneMixer's target-region setting adapts the cast's names and ethnicity, the street scenes and props, and the language of any on-screen text to a Western, East Asian, Southeast Asian, Latin American or Central Asian audience during script analysis, so the Korean-dialogue version of your story is not a Western cast reading Korean. See how to choose the dialogue language and localize the cast for the workflow, and native dialogue vs. dubbing for why the performance is generated rather than dubbed.
The cast speaks it. The video model generates picture and audio together with the line already in the chosen language, so pacing and mouth movement match that language. There is no dubbing pass and no separate voice track to align.
Any of the 15 interface languages — English, Chinese, Portuguese, Korean, Spanish, Japanese, Indonesian, Russian, French, Italian, Dutch, Arabic, Turkish, German and Ukrainian — plus Cantonese as a dialogue-only option. The language is set per project in Step 1, before the script is parsed.
No. A segment costs the same in any language, and the translated storyboards and descriptions you read in your interface language are free. You only ever pay per generated segment.
Yes. A producer working in German can make a series whose cast speaks Indonesian: the interface and the working documents follow the interface language, the spoken dialogue follows the project setting.
Rewrite that segment's script or regenerate the segment; only that segment is charged again. German and Ukrainian are the two languages where an occasional mispronounced word ending shows up on long sentences, so keep lines short there.
Pick the dialogue language in Step 1; the storyboards you read follow your interface language; the cast performs the lines natively.
Sign up freeLanguage list and per-language notes reflect SceneMixer's language registry and test scenes as of 2026-09-12; quality notes are working observations, not vendor guarantees.
Pricing·Novel to Video·Guides·Samples·Support·Privacy·Terms·Legal·Contact·© 2026 SceneMixer