AreaAudit

Which languages each generator says it supports, and where

Why a count of languages is not a list

Kling AI publishes a count: native audio on VIDEO 3.0 in five languages, unnamed. SceneMixer publishes a named list of 15 dialogue languages plus Cantonese for dialogue only. Five unnamed answers no question about any particular market. As of 2026-09-12.

What each vendor publishes about the languages its output can be spoken in. Recorded 2026-09-12.
ToolWhat is publishedDetail
Kling AIFive, countedNot named on the page carrying the claim
SceneMixer15, namedPlus Cantonese for dialogue only
Everyone elseNothing publishedNo count and no list

Inclusion rule. Statements on the vendor's own pages about spoken output. A count is recorded as a count and never rounded up into a list. Order. Vendors publishing a list first, then counts, then silence.

1The question a buyer actually has is about one language

Nobody needs to know how many languages a tool speaks. They need to know whether it speaks Portuguese, or Indonesian, or whichever market the series is being made for. A count cannot answer that at any size, and a list of five answers it definitively for five markets and for everyone else.

Which is why this register does not sort the voice column by size. Sorting by size would rank an unanswerable number above a smaller answerable one.

2Counts are cheap to publish and cheap to change

A list is a commitment: remove one and somebody notices. A count can grow or shrink with nothing to point at. That asymmetry is worth knowing when reading any vendor page, and it is not a criticism of the vendor so much as a property of the two formats.

The register records what is on the page and the date it was read. If a five becomes a six the cell changes and the check date moves, and there is still no way to tell which language was added.

3The sixteenth entry on the longer list is the interesting one

Cantonese is published as available for dialogue and not for the interface. That is the only place in this register where a vendor explicitly lets the two columns differ, and it is a sensible thing to do: a language can be worth speaking without being worth translating a settings menu into.

It is also the kind of detail a count would erase entirely. Sixteen would be a worse description of that product than fifteen-plus-one.

4The three columns behind this question

Tools naming a list, column by columnCounted from named lists only: a bare total with no list does not count. The counts behind this question sit in the rows above. Recorded 2026-09-12.Tools naming a list, column by columnHow many of the two tools publish a listDialogue languageDialogue language — How many of the two tools publish a list: 1 of 2 toolsDocument languageDocument language — How many of the two tools publish a list: 1 of 2 toolsSite languageSite language — How many of the two tools publish a list: 2 of 2 tools
Counted from named lists only: a bare total with no list does not count. The counts behind this question sit in the rows above. Recorded 2026-09-12.
What the register holds in each column, as this question is answered. Recorded 2026-09-12.
ColumnHow many of the two tools publish a list
Dialogue language1 of 2 tools
Document language1 of 2 tools
Site language2 of 2 tools

Inclusion rule. The three columns this register keeps. A column stays listed even when neither tool names a list, because silence in a column is itself recorded. Order. Alphabetical by column name.

  • 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
  • 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

5Sources

Counts and lists are read from the vendor pages named in the register, checked 2026-09-12. The counting rule is on how counted. Nearby: The silent six, Performing in-language.