Story setup and connected Scenes, named as stages of the work
The page names the stages as Cast plus World, story setup, scenes and film assembly. That is a description of how the product is arranged rather than of what it will achieve, and the connected Scenes are where the split into instalments actually sits. As of 2026-09-16.
| Point | What the vendor's page states | How this file reads it |
|---|---|---|
| The sentence | Cast and World, story setup, scenes, film assembly, named as stages | Documented, as an ordered pipeline |
| What it names | Four stages, in the order they are worked through | A pipeline a producer can map onto a schedule |
| What it leaves out | Where episode boundaries are decided | Scenes are named; the instalment is not |
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.
1Naming every stage is rarer than naming one feature
A page that lists its stages has told a reader what the product thinks the job consists of. That is checkable against how a production actually works, and mismatches show up immediately: a missing stage means work somebody will be doing elsewhere.
Here the four stages cover preparation, writing, shooting and assembly, which is a complete account of a short drama pipeline. Very few pages on this file get that far.
2Scenes are named and episodes are not, which leaves a gap
Connected Scenes suggests the scenes know about each other, which is the harder half of structure. What is missing is the level above: which scenes make an instalment, and what decides where one ends.
For a phone-first series that boundary is the product. Recording the gap here rather than assuming it is handled is the difference between reading a page and being sold by it.
3Where this sits in the column
| Tool | What the vendor publishes on the split |
|---|---|
| AI Drama Generator | The narrative stated to be structured automatically into episodes, scenes, dialogue and beats |
| AI Dramas | Nothing published on a script being split; scenes are written one at a time by the user |
| Anijam | Multi-episode short drama and one-to-two-minute micro drama both stated as supported |
| Arcloop | Recurring episodes with consistent characters given as the output |
| character.app | Story setup and connected Scenes named as stages |
| Crano AI | Repeatable episode structures described as something the user builds |
| DramaSo | A season of up to 60 episodes stated as plannable from one premise |
| Dramily | Episode scripts drafted from an idea, with a project stated to run to 120 episodes |
| Genra | Structured episode outlines and scene breakdowns, described on the vendor's blog |
| Google Flow | Nothing published |
| invideo AI | An agent plans a season episode by episode |
| Kling AI | Nothing published |
| LTX Studio | Organised per production, no episode structure |
| Luma Agents | Characters, story arcs and episode boards developed on the board, then a pilot |
| Medeo | Turning one story into numbered parts, recap clips and next-episode teasers |
| Novi AI | Serialized mini-dramas stated to be creatable from scripts, novels or story outlines |
| OpenArt | A director feature stated to structure a story into episodes and scenes |
| Pexo | An open loop at the end of one cut carries the cast into the next |
| PopShort AI | A script or novel uploaded into Drama Canvas, with characters, scenes and props extracted |
| SceneMixer | One upload analysed into characters, scenes, props and episodes |
| Showrunner Studio | A written scene stated to return an episode, and a show shaped into a season |
| StoryShort | Scene-by-scene writing and a named beat order: hook, escalation, reveal, cliffhanger |
| Topview | Nothing published |
| TrendShort | A script, draft or outline broken into shots, beats and visual prompts, one level below episodes |
| Vidu | Nothing published |
Inclusion rule. Every entry on this file appears below. A vendor stating that work is organised some other way is recorded as publishing something; silence is recorded as silence. Order. Alphabetical by tool name.
4The wording itself
- Assembling an episodeThe stages are named as Cast plus World, story setup, scenes and film assemblya named stage
- Script to episodesThe AI is described as writing the script scene by scene, casting consistent characters and storyboarding every shot as hook, escalation, reveal and cliffhangera named sequence
5Sources
Read from the vertical drama maker page at character.app, checked 2026-09-16. The whole column is on script to episodes and this vendor on every column is on character.app; where the line falls between documented, claimed and absent is under how read. This vendor's other readings: the cross-episode cast, the assembly step. Other readings of the same column: TrendShort, Luma Agents.