Taking a cast from one project into the next

Four tools describe a character that can be used again, and they differ on where it can go. One scopes an element across projects. One copies a character, scene or item from any earlier project into a new one, carrying its images, voice and state images, with the original kept so the swap can be undone. As of 2026-10-13.

Inclusion rule. Tools whose pages describe a character object that can be reused. A tool that describes consistency within one video without a reusable object does not earn a row. Order. Alphabetical by tool.

1A shared object or a copy

Two arrangements are documented and they behave differently over time. An element shared across projects is one object: change it and every project using it sees the change. A copy is a new, separate entry: the guide for the copying route states that a later change in the source project does not reach the new one, and that there is no live link between them.

A shared object keeps every project in step; a copy keeps a finished season safe from edits made for the next one. Which is preferable depends on whether the earlier work is still being changed.

2What travels with the face

On the copying route, the whole entry moves: name, description, the main image and its face and half-body crops, the voice and every state image. The name is then written in wherever the old one stood in the project's storyboards and outlines, and the entry it replaced is kept so the swap can be undone.

That matters because the reference sheet is what holds the face. A copied sheet produces the same face for the same reason the original did.

3Across languages

One guide covers moving a cast into a project set to another language: the description, the voice description and the state names are translated on the way, and the character's name is not. It is the only page in the register that addresses a cast crossing a language boundary rather than a project boundary.

• Cross-episode cast
  Every character is described as saved with a name, a face and a voice style, then referenced by name in each script so the same face appears in every rendera saved object addressed by nameAI Dramas, home page / recorded 2026-09-22
• Cross-episode cast
  Characters defined as elements carry their appearance and voice between generationsper elementKling AI, model guide / recorded 2026-09-12
• Cross-episode cast
  Elements are reusable across projects rather than only within oneacross productionsLTX Studio, Elements / recorded 2026-09-12
• A cast in a second project
  Pick existing moves a character, scene or item from any of the user's projects into this one, with its name, description, images, voice and state images, at no chargeSceneMixer, reuse guide / recorded 2026-10-13
• Copy or shared object
  The replaced entry is kept and can be restored, and the copy has no live link to the project it came fromSceneMixer, reuse guide / recorded 2026-10-13
• A cast in another language
  Moving an entry into a project in another language translates its description and voice description and keeps its nameSceneMixer, reuse guide / recorded 2026-10-13
• Cross-episode cast
  A full-body reference sheet is generated per character at analysis time, and its face and body crops are injected into every segment featuring that charactera stated mechanismSceneMixer, how-to guide / recorded 2026-09-12

4The words this register uses

Terms with a page of their own, each recording what vendors publish about it, include segment and shot, reference image, character consistency, storyboard script, scene plate, novel to video, AI short drama and vertical micro-drama.

5Sources

Each cell above traces back to a vendor page named in the register, read 2026-10-13. Where the boundary sits between documented, claimed and absent is spelled out under how read. Also here: Several names, Across the join, Costume change.