Cross-episode cast, the column explained

This column records what a vendor names as the thing that holds a face between generations. Fourteen entries name a mechanism, among them a reference sheet cropped per segment, two element systems, Hyperframe, cast cards, ingredients, stored production assets and a canon. Eleven describe the result and leave the mechanism unnamed. As of 2026-09-22.

Inclusion rule. Every tool with a page on this file appears, including those whose vendor says nothing on this step. The cell carries the vendor's own noun where one exists and the promise where it does not. Order. Alphabetical by tool name.

1The field asks what does the holding, not whether it holds

Every entry is put the same first question, and it is not whether characters stay recognisable. It is what the vendor names as the thing doing the work: a sheet, an element, a saved cast, a bundle of images handed over on each call. Naming an object tells a producer where to look on the morning episode nine comes back with a stranger playing the lead. Promising consistency tells them nothing they can act on that morning.

So the middle cell carries the vendor's own noun wherever a noun exists, and carries the promise wherever it does not. The evidence cell then says which of the two was read. Several pages in this file sit in the second group not because the footage is worse but because the writing stops one sentence before the part a production needs.

2A stored object and a per-call input break in different places

Two vendors resolve an element on your behalf, which is less work per generation and much harder to inspect when it slips. One of the two scopes its elements wider than a single production, so a studio running a second series with the same lead is describing a different arrangement from a studio that rebuilds the character each time. Others keep the artefact in plain sight instead: a full-body sheet made while the script is analysed and cropped into each segment where that character appears, a stored production asset a later episode is told to reuse, a card a user opens, a character the script calls by name.

At the far end sits the API that stores nothing: between one and seven reference images travel with every call and the platform forgets them afterwards, which makes continuity across forty episodes a filing job on the caller's side. None of these arrangements is superior in the abstract. They differ in who keeps the artefact, and that decides whose afternoon goes on repairing a drift.

3What a filled cell still does not promise

A named mechanism is not a measurement. Nothing in this column says how near the ninth episode's face lands to the first, because answering that needs a production run, a shot list nobody has published and a ruling on how near counts as near enough. The cell records what a vendor has put in writing, which is the part a reader can check before paying for anything.

The column is also silent about money. Holding a cast tends to mean extra generations, retries and stored artefacts, and no page read for this file prices the gap between a series with a locked lead and one without. Where a vendor does publish a rate it stays on that vendor's own entry rather than being folded in here.

4What the vendors say, in their own words

• 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
• Cross-episode cast
  One to seven reference images per call, used so the model generates a video with consistent subjectsper call rather than per characterVidu, reference-to-video API reference / recorded 2026-09-12
• Cross-episode cast
  No reusable character or element stored between calls is documentedwhat the documentation does not describeVidu, reference-to-video API reference / recorded 2026-09-12
• Cross-episode cast
  The product is described as building a recurring Cast, World and connected Scenes behind a phone-first seriesnamed reusable objectscharacter.app, vertical drama maker page / recorded 2026-09-16
• Cross-episode cast
  Leads are described as staying the same people across every episode, with the same face, wardrobe and chemistryan outcome without a mechanismOpenArt, drama generator page / recorded 2026-09-16
• Cross-episode cast
  Characters and scenes are described as built before video generation, which the page says helps improve visual continuityan outcome with a stage namedTopview, drama studio page / recorded 2026-09-16
• Cross-episode cast
  The page describes locking characters' faces across every episode, syncing dialogue to lip movement and assembling everything on a timelinean action without a stored objectAnijam, drama generator page / recorded 2026-09-16
• Cross-episode cast
  Character consistency is attributed to the underlying video model rather than to the productattributed to a modelMedeo, short drama page / recorded 2026-09-16
• Cross-episode cast
  Character sheets and locations are described as held in agent project memoryvendor claiminvideo AI, microdrama page / recorded 2026-09-12
• Cross-episode cast
  Hyperframe is named as what locks a character's face, wardrobe and voice across every episode, and the identity of a product or brand in every shota named mechanismPexo, micro drama page / recorded 2026-09-22
• Cross-episode cast
  Characters, scenes and props are stated to be stored as reusable production assets, reusable throughout the series to help maintain consistency from Episode 1 to Episode 50stored assets with a stated spanPopShort AI, home page / recorded 2026-09-22
• Cross-episode cast
  The sets, characters and canon are stated to persist across the whole series, held in the product as the show's worldpersistence stated for a seriesShowrunner Studio, home page / recorded 2026-09-22
• Cross-episode cast
  The help centre states that the same images for a character and key objects can be used consistently from one clip to the next through ingredientsa named input in documentationGoogle Flow, help centre / recorded 2026-09-22
• Cross-episode cast
  Characters, products, logos and brand elements are described as definable, with the agent instructed to preserve them across variations, video generation, localisation and iterationsdefined objects and where they are preservedLuma Agents, product page / recorded 2026-09-22
• Cross-episode cast
  Cast cards are described as holding a face and a voice so characters keep their look and speak in their own voice across every scenea named card objectGenra, home page / recorded 2026-09-22
• 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
  The page states that when a character is created the system locks their appearance, and that consistency is maintained across the entire projectlocked at creationNovi AI, drama generator page / recorded 2026-09-22
• Cross-episode cast
  Character dynamics, scenes and props are described as turned into reusable assets so a new episode keeps the visual continuitynamed reusable assetsDramily, home page / recorded 2026-09-22
• Cross-episode cast
  Locking each character's face, outfit, personality and visual identity is named as a step, with locations and style kept consistent from one scene to the nextan action with no stored objectArcloop, drama generator page / recorded 2026-09-22
• Cross-episode cast
  The same character identity is stated to hold across episodes, with stable appearance, personality and emotional presencea result across episodesCrano AI, drama generator page / recorded 2026-09-22
• Cross-episode cast
  Locking identity, wardrobe, face and emotional range is listed as a step in the workflowa listed instructionTrendShort, home page / recorded 2026-09-22

5Every entry on this column, one at a time

The table above reads across. These read down: one vendor, this column, the sentence and the gap in it.

• AI Dramas on the cast — Each character is saved with a name, a face and a voice style, then referenced by name in the script, so the resolution happens wherever the name appears.
• Anijam on the cast — Faces are said to be locked across every episode, dialogue synced to lip movement and everything assembled on a timeline, all as actions the tool performs.
• Arcloop on the cast — Face, outfit, personality and visual identity are listed as locked, with locations and style held scene to scene, and no object named.
• character.app on the cast — Two capitalised objects, a recurring Cast and a World, are presented as the things the series rests on rather than as results the model achieves.
• Crano AI on the cast — Stable appearance, personality and emotional presence are stated to hold across episodes, which is a claim about the outcome with no step behind it.
• Dramily on the cast — The reusable assets described here include character dynamics rather than only appearances, which is a claim about relationships as well as faces.
• Genra on the cast — Cast cards are said to hold a face and a voice so characters keep their look and speak in their own voice, scoped to every scene.
• Google Flow on the cast — The help centre describes reusing the same images for a character from one clip to the next, which is a smaller promise than one about a season.
• invideo AI on the cast — Character sheets and locations are said to be held in agent project memory, which names a place without describing what is kept there or for how long.
• Kling AI on the cast — Characters defined as elements carry their appearance and their voice between generations, which puts audio inside the same object as picture.
• LTX Studio on the cast — Elements are called reusable across projects rather than only within one, which turns a character from a project asset into a company one.
• Luma Agents on the cast — Characters, products and brand elements can be defined, with the agent told to preserve them through generation, localisation and iteration.
• Medeo on the cast — Character consistency is attributed to the underlying video model rather than to the product, which moves the answer outside the thing being bought.
• Novi AI on the cast — The lock is placed at creation time and the span given is the entire project, which makes the moment of the lock the interesting part of the sentence.
• OpenArt on the cast — Leads are said to stay the same across every episode down to face, wardrobe and chemistry: a specific promise, and still only a promise.
• Pexo on the cast — Hyperframe is given a name and a job: a face, a wardrobe and a voice held across every episode, and the identity of a product or brand held in every shot.
• PopShort AI on the cast — Characters, scenes and props are called reusable production assets, and the span is given in episode numbers rather than as an adjective.
• SceneMixer on the cast — The sheet is made while the script is read, and its face and body crops travel into every segment using that character, so a missing sheet shows up later.
• Showrunner Studio on the cast — Persistence is claimed for sets, characters and canon together, held in the product as the show's world, which is a wider object than a cast list.
• Topview on the cast — Characters and scenes are described as built before video generation, which the page says helps improve visual continuity, with no artefact named.
• TrendShort on the cast — Locking identity, wardrobe, face and emotional range appears as one item in a numbered workflow, which places the work without describing it.
• Vidu on the cast — The API reference takes up to seven reference images per request and documents no stored character, so the filing of a cast sits with the caller.

6Sources

Every cell traces back to a vendor page named on the register and read 2026-09-12, 2026-09-16 and 2026-09-22; where the line sits between documented, claimed and absent is set out under how read. The other fields: script to episodes, assembling an episode, serial format. All four are listed on the fields page.