EpisodeReel

Serial work: what each tool documents about continuity

Ingredients, documented in a help centre and scoped to the next clip

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 a named input called ingredients. The scope in that sentence is a clip and its successor, not an episode and certainly not a season. As of 2026-09-22.

The distance a support article commits toOne clip and its successor is the scope stated beside the named input. A season is forty instalments and a different order of magnitude.What is statedWhat is notDistanceOne clip to the nextAnything at episode scaleWho supplies itThe user, each generationNo stored, named objectCoverageA character and key objectsTwo characters at onceWritten to stop a support ticket, not to close a sale
Fig. 1 Reading clip-to-clip as episode-to-episode is the mistake this reading exists to prevent.
Google Flow on the cross-episode cast, in the wording the page uses. Read 2026-09-22.
PointWhat the vendor's page statesHow this file reads it
The sentenceThe same images reused for a character from one clip to the nextDocumented, in support material rather than marketing
What it namesIngredients, as an input the user suppliesA named slot, with the images owned by the user
What it leaves outAnything at the scale of an episode or a seriesA reader planning forty episodes extrapolates at their own risk

Inclusion rule. Three points per reading: the sentence as the vendor published it, the thing that sentence names, and what it declines to settle. Nothing here is inferred from an interface or a demo. Order. From the published sentence, to what it names, to what it leaves open.

1Where a sentence is published tells you what it was written for

A help-centre article exists to stop a support ticket, so it describes the next thing a user will try. A product page exists to close a sale, so it describes the furthest thing the product might achieve. The first genre tends to be narrower and more accurate.

This column therefore records the genre as well as the words. An ingredient explained in support material is stronger evidence than a season promised in a headline, and it is also a smaller claim.

2Clip to clip is the honest unit here

Nothing in the article addresses what happens on the fortieth reuse, whether the images can be stored under a name, or whether two characters can be held at once without bleeding into each other. A production would find all three out by doing it.

Treating clip-to-clip as if it meant episode-to-episode is the specific mistake this reading exists to prevent. The sentence is good; it is just about a shorter distance.

3Where this sits in the column

What the vendor publishes on the cast, entry by entryEvery entry on the cast column, with this one marked.What the vendor publishes on the cast, entry by entryWhat the vendor publishes on the castAI Drama Generator — What the vendor publishes on the cast: Consistent characters listed among the outputs, with no mechanism namedAI Drama GeneratorAI Dramas — What the vendor publishes on the cast: Each character saved with a name, a face and a voice style, then called by name in every scriptAI DramasAnijam — What the vendor publishes on the cast: Locking characters' faces across every episode stated as an action the tool performsAnijamArcloop — What the vendor publishes on the cast: Locking a face, outfit, personality and visual identity listed as a step, with no object namedArcloopcharacter.app — What the vendor publishes on the cast: A recurring Cast and World described as objects the series is built oncharacter.appCrano AI — What the vendor publishes on the cast: The same identity stated to hold across episodes, with stable appearance and emotional presenceCrano AIDramaSo — What the vendor publishes on the cast: Consistent characters listed among the outputs, with no mechanism namedDramaSoDramily — What the vendor publishes on the cast: Character dynamics, scenes and props turned into reusable assetsDramilyGenra — What the vendor publishes on the cast: Cast cards holding a face and a voice, stated to carry across every sceneGenraGoogle Flow — What the vendor publishes on the cast: Ingredients, the same images reused for a character and key objects from one clip to the nextGoogle Flowinvideo AI — What the vendor publishes on the cast: Project memory holds character sheets and locationsinvideo AIKling AI — What the vendor publishes on the cast: Elements carry appearance and voice between generationsKling AILTX Studio — What the vendor publishes on the cast: Elements are reusable across projectsLTX StudioLuma Agents — What the vendor publishes on the cast: Characters, products and brand elements defined once and preserved across named operationsLuma AgentsMedeo — What the vendor publishes on the cast: Consistency attributed to the video model the product runs onMedeoNovi AI — What the vendor publishes on the cast: A character created in the product, whose appearance the system locks for the whole projectNovi AIOpenArt — What the vendor publishes on the cast: Leads stated to stay the same across every episode, face, wardrobe and chemistryOpenArtPexo — What the vendor publishes on the cast: Hyperframe, named as what locks a face, wardrobe and voice across every episodePexoPopShort AI — What the vendor publishes on the cast: Characters, scenes and props stored as reusable production assets, from Episode 1 to Episode 50PopShort AISceneMixer — What the vendor publishes on the cast: Reference sheet per character, crops injected into every segmentSceneMixerShowrunner Studio — What the vendor publishes on the cast: Sets, characters and canon stated to persist across the whole seriesShowrunner StudioStoryShort — What the vendor publishes on the cast: Casting consistent characters listed as a step, with no mechanism namedStoryShortTopview — What the vendor publishes on the cast: Characters and scenes stated to be built before video generation, to help continuityTopviewTrendShort — What the vendor publishes on the cast: Locking identity, wardrobe, face and emotional range listed as a stepTrendShortVidu — What the vendor publishes on the cast: One to seven reference images supplied per callVidu
Fig. 2 Every entry on the cast column, with this one marked.
The cross-episode cast column with Google Flow marked. Rows read between 2026-09-12 and 2026-09-22.
ToolWhat the vendor publishes on the cast
AI Drama GeneratorConsistent characters listed among the outputs, with no mechanism named
AI DramasEach character saved with a name, a face and a voice style, then called by name in every script
AnijamLocking characters' faces across every episode stated as an action the tool performs
ArcloopLocking a face, outfit, personality and visual identity listed as a step, with no object named
character.appA recurring Cast and World described as objects the series is built on
Crano AIThe same identity stated to hold across episodes, with stable appearance and emotional presence
DramaSoConsistent characters listed among the outputs, with no mechanism named
DramilyCharacter dynamics, scenes and props turned into reusable assets
GenraCast cards holding a face and a voice, stated to carry across every scene
Google FlowIngredients, the same images reused for a character and key objects from one clip to the next
invideo AIProject memory holds character sheets and locations
Kling AIElements carry appearance and voice between generations
LTX StudioElements are reusable across projects
Luma AgentsCharacters, products and brand elements defined once and preserved across named operations
MedeoConsistency attributed to the video model the product runs on
Novi AIA character created in the product, whose appearance the system locks for the whole project
OpenArtLeads stated to stay the same across every episode, face, wardrobe and chemistry
PexoHyperframe, named as what locks a face, wardrobe and voice across every episode
PopShort AICharacters, scenes and props stored as reusable production assets, from Episode 1 to Episode 50
SceneMixerReference sheet per character, crops injected into every segment
Showrunner StudioSets, characters and canon stated to persist across the whole series
StoryShortCasting consistent characters listed as a step, with no mechanism named
TopviewCharacters and scenes stated to be built before video generation, to help continuity
TrendShortLocking identity, wardrobe, face and emotional range listed as a step
ViduOne to seven reference images supplied per call

Inclusion rule. Every entry on this file appears in the column below, including the ones whose vendor says nothing on this step. The marked row is the entry this page is about. Order. Alphabetical by tool name.

4The wording itself

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

5Sources

Read from the help centre article at support.google.com, checked 2026-09-22. The whole column is on cross-episode cast and this vendor on every column is on Google Flow; where the line falls between documented, claimed and absent is under how read. This vendor's other readings: the shape of the deliverable. Other readings of the same column: Showrunner Studio, LTX Studio.