Which languages the dialogue is spoken in

Nine of the 18 tools publish something about spoken language, and the split inside those nine is the finding: five print a named set a buyer can search, from 143 rows at Synthesia down to 15 at SceneMixer, while four print only a number, from 140+ at Vidnoz down to five at Kling AI. As of 2026-09-22.

Inclusion rule. All 18 tools in the register, grouped where the published answer is identical. A count without a list is recorded as a count, never rounded up into a list. Order. Named lists first, then counts, then the tools publishing neither.

1A count and a list answer different questions

Five languages and fifteen named languages are not two points on the same scale. A production asking whether Portuguese is covered gets an answer from one of them and no answer from the other, however large the number. This register records a count as a count for that reason, and does not treat the absence of a list as evidence either way.

The sixteenth entry on the longer list is worth noting because of its shape rather than its size: Cantonese is published as available for dialogue and not for the interface, which is the only place in this register where the two columns are explicitly allowed to differ.

2Per project rather than per generation

Where the language is set changes what a series has to manage. Set per project, it is decided once and applies to everything generated underneath, so an episode cannot quietly come out in a different language from the one before it. Set per call, it is a parameter someone has to get right every time.

Only one vendor here publishes where the setting lives. Four of the nine that publish anything give a number and no location at all, and a dubbing list implies a third shape again: the decision is made per file, after footage exists, rather than being a property of the production.

3What the vendor claims follows from generating in-language

One published sentence goes further than the list. It puts the language inside the render itself: the spoken line is produced as the shot is produced, with no dubbing pass and no lip-sync repair afterwards. That is a claim about method, and this register records it as one.

Whether the result satisfies a native speaker is a judgement about output, which is outside what a register of published statements can settle. What it does settle is where the language decision sits in the pipeline, and that is a scheduling fact rather than a quality one: a production that plans a dubbing pass is planning for a different tool than a production that does not.

4Sources

The dialogue list and the in-language claim are from the languages guide on scenemixer.com; the voice count is from the Kling AI model guide. Both checked 2026-09-12. Every tool side by side is in the register, and the written side is on document languages.

5This column against the other two

Inclusion rule. The three columns this register keeps apart on purpose. A column is listed even when no vendor publishes anything in it. Order. Alphabetical by column name.

• Voice languages
  Spoken dialogue is set per project to any of the 15, with Cantonese a 16th option for dialogue onlyset per projectSceneMixer, languages guide / recorded 2026-09-12
• How the dialogue language is applied
  The vendor states the video model performs the line in the chosen language while it renders the shot, with no separate dubbing step and no lip-sync patch afterwardsSceneMixer, languages guide / recorded 2026-09-12
• Voice languages
  Native audio on VIDEO 3.0 in five languages, with voices bound to elementscount published without a listKling AI, model guide / recorded 2026-09-12