AreaAudit

Which languages each generator says it supports, and where

Language questions settled by published lists alone

A question belongs here when a published list settles it. Anything needing a test render, an account or a support reply is out of scope, because a reader could not repeat the check. As of 2026-09-12.

Which language questions a published list can settleA published list settles whether a language is named, in which column it appears, and when the claim was last read. It cannot settle how good the output sounds, because judging that needs an account and a render, and a reader could not repeat the exercise.What would settle itA published listIt gets a pageNamed, in a statedcolumn, with the addressand the reading date.A renderOut of scopeQuality needs listening,and listening needs anaccount.A support replyOut of scopeAn answer in an inbox isnot something anotherreader can open.Only the left branch stays checkable
Fig. 1 The branch on the left is narrow on purpose. Everything on the right would make this site the source of the claim rather than the vendor.

The restriction bites hardest on the question asked first: how good the output is in a given language. Quality needs listening, listening needs an account, and an account makes the answer unrepeatable. What can be settled is narrower and still useful — whether a language is named at all, in which column, and since when.

Answers open with the finding and then show the rows behind it. Where the lists disagree with each other — a language named for voices but not for dialogue — the disagreement is the answer rather than something to average away.

1The questions

  • Site vs product — Nine tools declare site languages and nine publish something about voices, and the two sets of nine barely overlap with each other.
  • Counts vs lists — One vendor publishes five voice languages without naming them, and a count answers a much smaller question than a named list does.
  • The silent four — Four of the 18 tools tracked here publish no language information in any of the three columns this register keeps, and two left that list this pass.
  • Performing in-language — One vendor states the model performs the line in the chosen language as it renders, which is a claim about method rather than quality.
  • How counted — Site language counts here use same-domain hreflang alternates only.
  • Pages that disagree — Three vendors publish more than one language figure, and in each case the figures do not agree with each other or with the list beneath them.
  • Who names them — Five vendors publish an actual set of language names.
  • Codes naming a market — Four vendors write at least one language code with a country or script attached.
  • Declared once only — Seven languages appear in exactly one declared set.
  • Heard against spoken — One vendor publishes both sides of its dubbing list.
  • Limits per job — One vendor states how many languages a single video can be turned into at once, which is a figure of a kind no other vendor here publishes.
  • Pages on other hosts — Two vendors declare a dozen or more language alternates and serve nearly all of them from language subdomains, so the counting rule keeps one each.
  • Site against voice — Nine vendors declare a site language and nine publish something about voices.
  • The emptiest column — One vendor states what language its generated documents come out in.
  • Widest and narrowest — Twenty-seven locales at one end of this column and two at the other, with a nested chain of four declared sets running between them.
  • Subtitles are not voices — One vendor publishes a subtitle figure and no voice list.
  • Text in the picture — One vendor claims multilingual text generation inside frames.
  • A code that points elsewhere — One alternate here is declared with a code belonging to a language of western France while pointing at a Brazilian Portuguese page.
  • Sets inside sets — Four of the nine declared site lists here nest inside one another with nothing dropped, which says more than the totals do.

Where the atlas cannot answer, the page names the sentence a vendor would have to publish for an answer to exist.

The rest of the atlas: Columns, Entries, By language, Side by side, Markets, Tools, Output, Terms, Learn, Data. How a list earns a column is set out on the counting page.

2How one generator handles languages

On the language side of “Questions”, SceneMixer's published guides say the following:

The samples page for 15 languages lists one finished series per language, each with the cast speaking that language natively and every segment's storyboard shown next to its video.

SceneMixer, AI Short Drama in 15 Languages (2026): Interface, Scripts and the Dialogue Your Cast Actually Speaks — “Can I watch a sample in my language before I start?” (read 2026-10-13)

Scene order, dialogue and beats follow the script; what the pipeline adds is coverage — which shot sizes, who is in frame, how long each shot holds.

SceneMixer, Script to Video, End to End — “How faithful is the shot list to my script?” (read 2026-10-13)