EpisodeReel

Serial work: what each tool documents about continuity

How a cast survives from episode to episode

Fourteen tools name the object that keeps a character the same, and they differ in how wide its scope runs: a canon persisting across a series, stored assets a later episode reuses, an element scoped wider than one production, a sheet cropped into each segment, a card, a name in a script, and images that live for one call. As of 2026-09-22.

Documented mechanisms, arranged by how widely the reusable object reachesFourteen tools document a way of keeping a character the same, and they sit at four different scopes. One reusable element outlives the project it was made in. Others stop at the project boundary: a canon, a stored library of production assets, a card, a sheet cropped into each segment, a character the script calls by name. At the far end, reference images are supplied on every call and nothing is stored between them.Widest scope firstAcross productionsThe reusable object outlives the project it was made in, so arecurring cast belongs to the company.Within a productionAn element, a canon, a stored asset library or a card: real, andstopping at the project boundary.Per segmentA sheet injected into every generation. Automatic, and visible:you can look at what was sent.Per call, stored nowhereReference images supplied every time, with nothing kept betweencalls.Injecting per segment has a visible failure mode, which is the point of it
Fig. 1 Scope is what separates these, and it is the field a studio with a recurring cast cares about most. Wider scope means the cast is a company asset rather than a project file, or in one case nothing at all after the call returns.
What each tool documents as the object that keeps a character consistent. Recorded 2026-09-22.
ToolWhat is publishedDetail
LTX StudioElement reusable across productionsScoped wider than a project
Showrunner StudioSets, characters and canon held as the show worldStated to persist across the whole series
PopShort AICharacters, scenes and props stored as production assetsReused from Episode 1 to Episode 50
PexoHyperframe, locking face, wardrobe and voiceStated for every episode
DramilyCharacter dynamics, scenes and props as reusable assetsCarried into each new episode
character.appA recurring Cast and a WorldThe series is built on them
Luma AgentsCharacters, products and brand elements defined oncePreserved across variations, generation and localisation
Novi AIA character created in the productAppearance locked for the whole project
Kling AIElement carrying appearance and voiceReused within a production
SceneMixerReference sheet per characterInjected per segment
GenraA cast card holding a face and a voiceStated across every scene
AI DramasA character saved with a name, a face and a voice styleResolved wherever the name appears in a script
Google FlowIngredients, the same images for a characterFrom one clip to the next
ViduOne to seven reference imagesPer call, with nothing stored

Inclusion rule. Mechanisms documented on the vendor's own pages. A vendor describing consistency without naming a mechanism is recorded as claiming rather than documenting. Order. By how wide the reusable object's scope is, widest first.

1A sheet and an element solve the same problem from opposite ends

A reference sheet is an image supplied to each generation; an element is an object the system resolves on your behalf. The first is visible and checkable, the second is less work and harder to inspect when something drifts.

Both are documented mechanisms rather than claims, which is what separates this table from the eleven entries that describe memory, locking or consistency without naming anything that does it.

2Scope is the field that separates the two element systems

One element system is reusable across productions rather than inside one. For a studio making several series with a shared cast that is a materially different arrangement, and it is the sort of detail a feature comparison usually flattens.

The register keeps scope in the row because it determines whether a cast is a project asset or a company asset.

3Injecting per segment has a visible failure mode

If the sheet is supplied to every segment, a segment generated without it is identifiable afterwards. That makes drift traceable, which is not true of a system that resolves references internally.

Nothing published says which approach produces better consistency. The register records the mechanism and leaves output judgements out.

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

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-09-22. Where the boundary sits between documented, claimed and absent is spelled out under how read. Also here: Splitting a script, Assembly, Claimed vs shown.