A hundred and twenty episodes per project, stated as a number
The page states that each project supports serialized dramas of up to a hundred and twenty episodes. It is the largest published figure in this column, and a figure is worth more than an adjective because a producer can schedule against it and can catch it being wrong. As of 2026-09-22.
| Point | What the vendor's page states | How this file reads it |
|---|---|---|
| The sentence | Up to a hundred and twenty episodes supported per project | Documented, as a stated ceiling |
| What it names | The project as the container, and its upper bound | A planning number, and a falsifiable one |
| What it leaves out | What the ceiling is a ceiling on | Storage, indexing, a plan limit: unstated, and they differ |
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.
1A ceiling tells you what the product was sized for
Nobody publishes a hundred and twenty episodes unless they have thought about the hundredth. The number is a statement about intended scale, and it separates this entry from pages whose vocabulary tops out at a pilot.
It is also the kind of claim that can be checked cheaply by a buyer with an account, which is more than most cells in this column offer.
2The meaning of the limit is the unstated half
A cap can come from a database column, from a plan tier, from an interface that stops paginating, or from the point where the vendor stopped testing. Each of those fails differently at episode one hundred and twenty-one.
The page does not say which, so the register carries the figure and the silence together. A reader planning a long run should ask, because the answer decides whether the number is a guarantee or a note about where confidence ends.
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
- Script to episodesEach project is stated to support serialized dramas of up to 120 episodeswith a stated ceiling
- Script to episodesA season of up to 60 episodes is described as plannable from a single premisewith a stated ceiling
5Sources
Read from the home page at dramily.com, checked 2026-09-22. The whole column is on script to episodes and this vendor on every column is on Dramily; 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: Novi AI, Arcloop.