EpisodeReel

Serial work: what each tool documents about continuity

Tools filed by what they document about a whole season

Each tool is filed against the same three questions. A demo answers none of them, because a demo is one clip and a season is a hundred of them that have to match. As of 2026-09-12.

The three steps a season needs and a clip does notA season needs a cast that survives being generated repeatedly, a script that becomes an ordered set of episodes, and an assembly step that produces a deliverable file. A single clip needs none of the three, which is why a strong demo predicts nothing about serial work.A cast that holdsThe same face in episode oneand episode nine, by amechanism the vendordocuments.FeedsScript to episodesA full script in, an orderedepisode structure out, ratherthan a prompt and a clip.FeedsAssemblyShots in order, audio acrossthe cut, a file that can bedelivered.
Fig. 1 Every entry on file is read against these three steps, including the entries that document only one of them.

Cross-episode cast is the first question and the one nearly every vendor answers. A character who looks like the reference in episode one and like a cousin in episode nine is a continuity failure that no amount of prompt craft repairs after the fact.

Script to episodes is the second. A tool that takes a full script and returns an episode structure is doing production work; a tool that takes a paragraph and returns a clip is doing something else, and the two are sold with similar language.

Assembly is the third. Somebody has to put the shots in order, hold the audio across the cut and deliver a file. Where the vendor documents that step it is recorded; where the vendor leaves it to an editor, that is recorded too, because it is a staffing decision rather than a feature gap.

1The entries

  • character.app — What character.app publishes for a whole season: a Cast and a World named as the things a series is built on.
  • DramaSo — What DramaSo publishes for a whole season: a stated ceiling of sixty episodes from one premise.
  • StoryShort — What StoryShort publishes for a whole season: a named beat order, and a cast that is only an adjective.
  • OpenArt — What OpenArt publishes for a whole season: face, wardrobe and chemistry promised, no mechanism given.
  • Topview — What Topview publishes for a whole season: characters built before generation, and nothing said about what survives.
  • Anijam — What Anijam publishes for a whole season: locking named as an action rather than an object.
  • Medeo — What Medeo publishes for a whole season: consistency attributed to the model it runs on.
  • AI Drama Generator — What AI Drama Generator publishes for a whole season: an episode count exposed as a form field.
  • Vidu — What Vidu publishes for a whole season: reference images per call, no stored character.
  • invideo AI — What invideo AI publishes for a whole season: a season planner described in prose.
  • Kling AI — What Kling AI publishes for a whole season: a cast system with no season around it.
  • LTX Studio — What LTX Studio publishes for a whole season: characters that outlive the production.
  • SceneMixer — What SceneMixer publishes for a whole season: three documented steps with a rate on the assembly.
  • AI Dramas — What AI Dramas publishes for a whole season: a character called by name in the script, and two rates for one episode.
  • Arcloop — What Arcloop publishes for a whole season: outfit and personality inside the lock sentence, and no object behind it.
  • Crano AI — What Crano AI publishes for a whole season: a publishing schedule offered where others offer an episode count.
  • Dramily — What Dramily publishes for a whole season: 120 episodes per project, and a review gate before credits are spent.
  • Genra — What Genra publishes for a whole season: a cast card holding a face and a voice, with the episode claim on a blog.
  • Google Flow — What Google Flow publishes for a whole season: ingredients, documented in a help centre, scoped to the next clip.
  • Luma Agents — What Luma Agents publishes for a whole season: definitions preserved through localisation, and a pilot rather than a season.
  • Novi AI — What Novi AI publishes for a whole season: appearance locked at the moment a character is created.
  • Pexo — What Pexo publishes for a whole season: Hyperframe, plus three frames and a length range for the deliverable.
  • PopShort AI — What PopShort AI publishes for a whole season: stored production assets, Episode 1 to Episode 50.
  • Showrunner Studio — What Showrunner Studio publishes for a whole season: sets, characters and canon persisting, and publishing in the product.
  • TrendShort — What TrendShort publishes for a whole season: a script broken to shots, and an export target with captions.

An entry is opened when a vendor publishes something about at least one of the three steps. Silence on all three keeps a tool off the file.

Also filed here: Season, Stages, Readings, Contrasts, Terms, Questions, Learn, Data. What earns an entry is set out under how read.