EpisodeReel

Serial work: what each tool documents about continuity

What Google Flow gives you for a whole season

Google Flow's help centre states that the same images for a character and key objects can be used consistently from one clip to the next through ingredients, and lists aspect ratio, model and generation length as preferences selected before a clip is made. As of 2026-09-22.

Steps each tool documentsFilled where the tool publishes a mechanism for that step, hollow where it publishes nothing on it.Steps each tool documentsWhat the vendor publishesWhat the vendorpublishesKind of evidenceCross-episode castCross-episode cast — What the vendor publishes: Ingredients, the same images reused for a character and key objects from one clip to the nextCross-episode cast — Kind of evidence: DocumentedScript to episodesScript to episodes — What the vendor publishes: Nothing publishedScript to episodes — Kind of evidence: -Assembling an episodeAssembling an episode — What the vendor publishes: Nothing publishedAssembling an episode — Kind of evidence: -
Fig. 1 Filled where the tool publishes a mechanism for that step, hollow where it publishes nothing on it.
The three season-scale steps, for Google Flow. Read from the vendor's help centre article on 2026-09-22.
StepWhat the vendor publishesKind of evidence
Cross-episode castIngredients, the same images reused for a character and key objects from one clip to the nextDocumented
Script to episodesNothing published-
Assembling an episodeNothing published-

Inclusion rule. The same three steps are recorded for every tool here. A step the vendor does not publish is recorded as nothing published rather than inferred from the interface. Order. Fixed step order, identical on every tool page.

1The same step, across every tool here

Cross-episode cast: who publishes a mechanismOne step at a time, every tool side by side, Google Flow marked. Hollow means the vendor publishes nothing on that step, not that the tool cannot do it. Wording in the rows below. Rows read between 2026-09-12 and 2026-09-22.Cross-episode cast: who publishes a mechanismCross-episode castAI Drama Generator — Cross-episode cast: Consistent characters listed among the outputs, with no mechanism namedAI Drama GeneratorAI Dramas — Cross-episode cast: Each character saved with a name, a face and a voice style, then called by name in every scriptAI DramasAnijam — Cross-episode cast: Locking characters' faces across every episode stated as an action the tool performsAnijamArcloop — Cross-episode cast: Locking a face, outfit, personality and visual identity listed as a step, with no object namedArcloopcharacter.app — Cross-episode cast: A recurring Cast and World described as objects the series is built oncharacter.appCrano AI — Cross-episode cast: The same identity stated to hold across episodes, with stable appearance and emotional presenceCrano AIDramaSo — Cross-episode cast: Consistent characters listed among the outputs, with no mechanism namedDramaSoDramily — Cross-episode cast: Character dynamics, scenes and props turned into reusable assetsDramilyGenra — Cross-episode cast: Cast cards holding a face and a voice, stated to carry across every sceneGenraGoogle Flow — Cross-episode cast: Ingredients, the same images reused for a character and key objects from one clip to the nextGoogle Flowinvideo AI — Cross-episode cast: Project memory holds character sheets and locationsinvideo AIKling AI — Cross-episode cast: Elements carry appearance and voice between generationsKling AILTX Studio — Cross-episode cast: Elements are reusable across projectsLTX StudioLuma Agents — Cross-episode cast: Characters, products and brand elements defined once and preserved across named operationsLuma AgentsMedeo — Cross-episode cast: Consistency attributed to the video model the product runs onMedeoNovi AI — Cross-episode cast: A character created in the product, whose appearance the system locks for the whole projectNovi AIOpenArt — Cross-episode cast: Leads stated to stay the same across every episode, face, wardrobe and chemistryOpenArtPexo — Cross-episode cast: Hyperframe, named as what locks a face, wardrobe and voice across every episodePexoPopShort AI — Cross-episode cast: Characters, scenes and props stored as reusable production assets, from Episode 1 to Episode 50PopShort AISceneMixer — Cross-episode cast: Reference sheet per character, crops injected into every segmentSceneMixerShowrunner Studio — Cross-episode cast: Sets, characters and canon stated to persist across the whole seriesShowrunner StudioStoryShort — Cross-episode cast: Casting consistent characters listed as a step, with no mechanism namedStoryShortTopview — Cross-episode cast: Characters and scenes stated to be built before video generation, to help continuityTopviewTrendShort — Cross-episode cast: Locking identity, wardrobe, face and emotional range listed as a stepTrendShortVidu — Cross-episode cast: One to seven reference images supplied per callVidu
Fig. 2 One step at a time, every tool side by side, Google Flow marked. Hollow means the vendor publishes nothing on that step, not that the tool cannot do it. Wording in the rows below. Rows read between 2026-09-12 and 2026-09-22.
Every tool on one step, with Google Flow marked. Rows read between 2026-09-12 and 2026-09-22.
ToolCross-episode 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. Tools whose public pages describe at least one of the three season-scale steps. A tool silent on this particular step keeps its row, marked hollow. Order. Alphabetical by tool name.

Script to episodes: who publishes a mechanismOne step at a time, every tool side by side, Google Flow marked. Hollow means the vendor publishes nothing on that step, not that the tool cannot do it. Wording in the rows below. Rows read between 2026-09-12 and 2026-09-22.Script to episodes: who publishes a mechanismScript to episodesAI Drama Generator — Script to episodes: The narrative stated to be structured automatically into episodes, scenes, dialogue and beatsAI Drama GeneratorAI Dramas — Script to episodes: Nothing published on a script being split; scenes are written one at a time by the userAI DramasAnijam — Script to episodes: Multi-episode short drama and one-to-two-minute micro drama both stated as supportedAnijamArcloop — Script to episodes: Recurring episodes with consistent characters given as the outputArcloopcharacter.app — Script to episodes: Story setup and connected Scenes named as stagescharacter.appCrano AI — Script to episodes: Repeatable episode structures described as something the user buildsCrano AIDramaSo — Script to episodes: A season of up to 60 episodes stated as plannable from one premiseDramaSoDramily — Script to episodes: Episode scripts drafted from an idea, with a project stated to run to 120 episodesDramilyGenra — Script to episodes: Structured episode outlines and scene breakdowns, described on the vendor's blogGenraGoogle Flow — Script to episodes: Nothing publishedGoogle Flowinvideo AI — Script to episodes: An agent plans a season episode by episodeinvideo AIKling AI — Script to episodes: Nothing publishedKling AILTX Studio — Script to episodes: Organised per production, no episode structureLTX StudioLuma Agents — Script to episodes: Characters, story arcs and episode boards developed on the board, then a pilotLuma AgentsMedeo — Script to episodes: Turning one story into numbered parts, recap clips and next-episode teasersMedeoNovi AI — Script to episodes: Serialized mini-dramas stated to be creatable from scripts, novels or story outlinesNovi AIOpenArt — Script to episodes: A director feature stated to structure a story into episodes and scenesOpenArtPexo — Script to episodes: An open loop at the end of one cut carries the cast into the nextPexoPopShort AI — Script to episodes: A script or novel uploaded into Drama Canvas, with characters, scenes and props extractedPopShort AISceneMixer — Script to episodes: One upload analysed into characters, scenes, props and episodesSceneMixerShowrunner Studio — Script to episodes: A written scene stated to return an episode, and a show shaped into a seasonShowrunner StudioStoryShort — Script to episodes: Scene-by-scene writing and a named beat order: hook, escalation, reveal, cliffhangerStoryShortTopview — Script to episodes: Nothing publishedTopviewTrendShort — Script to episodes: A script, draft or outline broken into shots, beats and visual prompts, one level below episodesTrendShortVidu — Script to episodes: Nothing publishedVidu
Fig. 3 One step at a time, every tool side by side, Google Flow marked. Hollow means the vendor publishes nothing on that step, not that the tool cannot do it. Wording in the rows below. Rows read between 2026-09-12 and 2026-09-22.
Every tool on one step, with Google Flow marked. Rows read between 2026-09-12 and 2026-09-22.
ToolScript to episodes
AI Drama GeneratorThe narrative stated to be structured automatically into episodes, scenes, dialogue and beats
AI DramasNothing published on a script being split; scenes are written one at a time by the user
AnijamMulti-episode short drama and one-to-two-minute micro drama both stated as supported
ArcloopRecurring episodes with consistent characters given as the output
character.appStory setup and connected Scenes named as stages
Crano AIRepeatable episode structures described as something the user builds
DramaSoA season of up to 60 episodes stated as plannable from one premise
DramilyEpisode scripts drafted from an idea, with a project stated to run to 120 episodes
GenraStructured episode outlines and scene breakdowns, described on the vendor's blog
Google FlowNothing published
invideo AIAn agent plans a season episode by episode
Kling AINothing published
LTX StudioOrganised per production, no episode structure
Luma AgentsCharacters, story arcs and episode boards developed on the board, then a pilot
MedeoTurning one story into numbered parts, recap clips and next-episode teasers
Novi AISerialized mini-dramas stated to be creatable from scripts, novels or story outlines
OpenArtA director feature stated to structure a story into episodes and scenes
PexoAn open loop at the end of one cut carries the cast into the next
PopShort AIA script or novel uploaded into Drama Canvas, with characters, scenes and props extracted
SceneMixerOne upload analysed into characters, scenes, props and episodes
Showrunner StudioA written scene stated to return an episode, and a show shaped into a season
StoryShortScene-by-scene writing and a named beat order: hook, escalation, reveal, cliffhanger
TopviewNothing published
TrendShortA script, draft or outline broken into shots, beats and visual prompts, one level below episodes
ViduNothing published

Inclusion rule. Tools whose public pages describe at least one of the three season-scale steps. A tool silent on this particular step keeps its row, marked hollow. Order. Alphabetical by tool name.

Assembling an episode: who publishes a mechanismOne step at a time, every tool side by side, Google Flow marked. Hollow means the vendor publishes nothing on that step, not that the tool cannot do it. Wording in the rows below. Rows read between 2026-09-12 and 2026-09-22.Assembling an episode: who publishes a mechanismAssembling an episodeAI Drama Generator — Assembling an episode: Nothing publishedAI Drama GeneratorAI Dramas — Assembling an episode: Clips of 4 to 15 seconds chained into an episode, with a draft rate and an episode-cut rateAI DramasAnijam — Assembling an episode: Assembling everything on a timeline stated as part of the flowAnijamArcloop — Assembling an episode: Nothing publishedArcloopcharacter.app — Assembling an episode: Film assembly named as a stagecharacter.appCrano AI — Assembling an episode: Nothing publishedCrano AIDramaSo — Assembling an episode: A captioned episode stated as the exportDramaSoDramily — Assembling an episode: Export-ready episodes listed among the outputs of one workspaceDramilyGenra — Assembling an episode: Export stated at 1080p; nothing published about joining shotsGenraGoogle Flow — Assembling an episode: Nothing publishedGoogle Flowinvideo AI — Assembling an episode: Nothing publishedinvideo AIKling AI — Assembling an episode: Nothing publishedKling AILTX Studio — Assembling an episode: Nothing publishedLTX StudioLuma Agents — Assembling an episode: Nothing publishedLuma AgentsMedeo — Assembling an episode: Nothing publishedMedeoNovi AI — Assembling an episode: Nothing publishedNovi AIOpenArt — Assembling an episode: Each vertical episode stated as exportable ready to publishOpenArtPexo — Assembling an episode: Nothing publishedPexoPopShort AI — Assembling an episode: Nothing publishedPopShort AISceneMixer — Assembling an episode: Composited from segments, 1 credit per second of outputSceneMixerShowrunner Studio — Assembling an episode: Publishing straight from the product named as a stepShowrunner StudioStoryShort — Assembling an episode: Clips stated as assembled into one vertical episodeStoryShortTopview — Assembling an episode: Nothing publishedTopviewTrendShort — Assembling an episode: A 9:16 vertical cut with captions and voiceover named as the export targetTrendShortVidu — Assembling an episode: Nothing publishedVidu
Fig. 4 One step at a time, every tool side by side, Google Flow marked. Hollow means the vendor publishes nothing on that step, not that the tool cannot do it. Wording in the rows below. Rows read between 2026-09-12 and 2026-09-22.
Every tool on one step, with Google Flow marked. Rows read between 2026-09-12 and 2026-09-22.
ToolAssembling an episode
AI Drama GeneratorNothing published
AI DramasClips of 4 to 15 seconds chained into an episode, with a draft rate and an episode-cut rate
AnijamAssembling everything on a timeline stated as part of the flow
ArcloopNothing published
character.appFilm assembly named as a stage
Crano AINothing published
DramaSoA captioned episode stated as the export
DramilyExport-ready episodes listed among the outputs of one workspace
GenraExport stated at 1080p; nothing published about joining shots
Google FlowNothing published
invideo AINothing published
Kling AINothing published
LTX StudioNothing published
Luma AgentsNothing published
MedeoNothing published
Novi AINothing published
OpenArtEach vertical episode stated as exportable ready to publish
PexoNothing published
PopShort AINothing published
SceneMixerComposited from segments, 1 credit per second of output
Showrunner StudioPublishing straight from the product named as a step
StoryShortClips stated as assembled into one vertical episode
TopviewNothing published
TrendShortA 9:16 vertical cut with captions and voiceover named as the export target
ViduNothing published

Inclusion rule. Tools whose public pages describe at least one of the three season-scale steps. A tool silent on this particular step keeps its row, marked hollow. Order. Alphabetical by tool name.

2A help centre is the strongest kind of page in this file

Most cast sentences recorded here sit on pages written to sell. This one sits in support documentation, next to the click path that uses it, which is written to be correct rather than to be persuasive. The mechanism is named, the object is named, and the moment it applies is the prompt for the next clip.

The scope is also stated plainly, and it is a clip. Consistency from one clip to the next is a sentence about two generations, not about episode nineteen, and nothing in the article extends it. That is a narrower promise than the short-drama products here make and a better documented one.

Documented at the clip, silent above itThe help centre names ingredients and the scope they cover, which is one clip to the next. Nothing in the article addresses a script arriving whole, an episode as an object, or finishing with one file, so the two upper layers of season work are unrecorded here.Nothing publishedA seasonNo episode object, no ordered run, nothing on assembling onefile.A sceneNo split from a script; the page starts from a prompt for aclip.Two clipsIngredients carry a character and key objects from one clip tothe next.One clipAspect ratio, model and generation length chosen beforegenerating.Documented in the help centre
Fig. 5 A support article is the strongest kind of page in this file and it is also the one least likely to promise anything above its own scope.

3Everything above the clip is somewhere else

Neither of the other two steps appears in the article. There is no object that means an episode, nothing about a script arriving whole, and nothing about ending with one file. A filmmaking tool built around clips has no reason to publish any of that, and this file records the silence rather than inferring capability from the product's reputation.

What the article does publish is the control panel: aspect ratio, number of outputs, model, generation length. Those are per-generation settings rather than a stated shape for a deliverable, which is why the serial-format field records this entry as a preference and that field page keeps a control apart from a commitment. Luma Agents answers the same question the same way, as something done to a finished clip rather than decided before one.

4This page, read column by column

Each reading below takes one column, quotes the sentence this vendor published on it, and says what the sentence declines to settle.

  • 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.
  • Google Flow on the shape — Aspect ratio, output count, model and generation length are listed as preferences chosen before generating, which puts the shape at clip scale.

5Sources

Read from the help centre article at support.google.com, checked 2026-09-22. Every tool on the same three steps is in the register; what counts as published is on how read.

  • 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
  • Serial format
    Aspect ratio, number of outputs, model and generation length are listed as the video preferences selected before generatingexposed as a preferenceGoogle Flow, help centre / recorded 2026-09-22