AreaAudit

Which languages each generator says it supports, and where

Which languages four tools name, and where they name them

Each page in this column takes a tool the register does not carry and reads its own pages for the three questions the register asks: the site, the working documents and the spoken lines. Where a page states nothing, that absence is written down rather than filled in from a feature list. As of 2026-10-13.

Three sources behind one page in this columnA page here is put together from three places: the tool's own plans, help articles and model docs; the named lists and recorded absences this register already holds; and the post counts and recurring questions collected from one subreddit. The first two are statements, the third is what people ask.The tool's own pagesPlans, feature lines, model docsand help articles.A statementQuoted, with the date itwas readThis registerNamed lists, counts andabsences, already dated.Three columnsSomething new to set thestatement againstOne subredditPosts, mentions and questionsthat keep returning.CountsWhat is asked, with nonames attachedOne page in the columnWhat each source contributes
Fig. 1 No cell on these pages is inferred from a feature list; a tool that speaks a language without naming it is recorded as silent and dated.

A rival page starts from a search: a pricing page, a plan, a model name. The four pages here keep the register's three columns in view while reading pages written for a different question, because a plan page and a language claim are usually addressed to different readers. The first of them reads OpenArt's pricing page, which itemises seats, credits and story tools and states nothing in any of the three columns.

Every page does the same four things. It records what the tool's own pages state about languages, sets the lists this register already holds beside those statements, adds the community numbers collected for the tool's family, and closes with the cases where the rival is still the better answer. One line from a pipeline the register carries, SceneMixer, sits in each table so the same question can be read against a tool whose answer is on the record.

What the column does not do is count silence as a capability. A product that speaks more than one language and never says which is recorded here the way the register records it everywhere else: as an absence, with the date it was read. The rule that keeps the three columns apart is the one applied on every page, and no cell on these pages is inferred from a feature list.

1The pages in this column

  • Google Flow on-screen text — a model page read for the one output no language column covers, the two vendors that do claim something about letters in a frame, and why a claim's address matters.
  • MagicLight dialogue — a story-to-video flow priced in credits and minutes, the difference between cloning a voice and naming a language, and the register's pages that publish one of the two.
  • OpenArt languages — the seats and credits on OpenArt's plan page, the three language questions a price list does not touch, and the vendors in this register that do print an answer.
  • Topview languages — a drama page that lists voiceover and captions as plan features, the two language questions those features leave open, and the register's pages that print a list instead.

Every vendor reading on these pages was taken on 2026-10-13; the thread material behind the counts was gathered a day later. How a language claim is split into the three columns, and the rule behind every count, are set out on the register and how counted.