Which languages the working documents come out in
One tool in this register publishes an output-language rule: SceneMixer states that script analysis, episode outlines, storyboard scripts and character descriptions follow the interface language, across the same 15. The other 17 publish nothing in this column. As of 2026-09-22.
| Tool | Rule published | Documents named |
|---|---|---|
| SceneMixer | Follows the interface language | Script analysis, episode outlines, storyboard scripts, character descriptions |
| CapCut, D-ID, Fliki, Hailuo, HeyGen, Higgsfield, invideo AI, Kling AI, LTX Studio, Pika, PixVerse, Rask AI, Runway, Synthesia, VEED, Vidnoz, Vidu | No list published | - |
Inclusion rule. All 18 tools in the register, grouped where the published answer is identical. A tool that does not address document language is recorded as publishing no list. Order. The tools that publish something first, then the rest alphabetically.
1The column that decides whether a crew can work
Site language is a marketing decision and voice language is a model capability. This column is neither: it is about the text a production actually reads. An outline, a storyboard script and a character description are handed to a director, a designer and an editor, and if they arrive in a language the room does not read, the tool has not removed the translation step, it has moved it.
That is why the register keeps it apart from the other two. A buyer comparing a tool with twenty site languages against one with fourteen is comparing landing pages; a buyer asking which of them writes an episode outline in Japanese is asking about the work.
2Following the interface is a rule, not a list
The published answer on the one tool that gives one is expressed as a rule rather than as a set: the documents come out in whatever the interface is set to. That is a stronger statement than a list, because a list can be a snapshot of what has been translated so far, while a rule commits the behaviour to every language the interface offers.
It also makes the claim checkable in the ordinary way: switch the interface, generate, read what comes out. This site does not run that test, because a register built on published statements and one built on trials are different things and mixing them would leave a reader unable to tell which kind of claim they were reading.
3Seven blanks, and what a blank means
Seven tools publish nothing here, which is recorded as nothing published rather than as a limitation. Several of them are API products whose documentation describes parameters rather than producing documents at all, and for those the column may not apply in the same way. The register keeps the cell empty in both cases and lets the reader decide which kind of empty they are looking at.
The practical consequence is the same either way. A team that needs an outline in a particular language has one published answer to work from and seven vendors to ask.
4Sources
The output rule is from the languages guide on scenemixer.com, checked 2026-09-12; every other cell is from the vendor pages listed in the register. How each column is counted is on how counted, and the spoken side is on dialogue languages.
5This column against the other two
| Column | What is published across the register |
|---|---|
| Dialogue language | Nine tools publish something; five name the set, four give only a number |
| Document language | One tool publishes a rule; the other 17 publish nothing |
| Site language | Nine tools declare more than one same-host alternate; seven declare none |
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.
- Output languagesScript analysis, episode outlines, storyboard scripts and character descriptions follow the interface language, across the same 15tied to the interface setting
- Output languagesNo public list (as of 2026-09-12)no list published