Inside an episode: how many versions are kept
15 of the 28 editors say something about how many versions are kept. Among those, the reading given most often is “History kept”, for 8. Each row carries the first statement logged; the full wording is on each editor's page. As of 2026-09-25.
| Editor | Reading | What the pages say |
|---|---|---|
| Character App | Pick from a set | Each take is kept or sent back with new direction; only kept takes become Clips |
| Crreo AI | Pick from a set | Each regeneration returns three variations to choose from; past work stays in Tool History |
| DirectStudio AI | None said | None said |
| DomoAI | Pick from a set | A scene is generated, reviewed, and the best version carried into the next episode |
| Filmora | None said | None said |
| Frameo | History kept | A lesson on timeline versions is part of the guide; pipelines are described with versioning |
| Genra | None said | None said |
| Google Flow | History kept | Editing keeps the original; the History panel holds every previous version and its prompt |
| HeyGen | Pick from a set | Several takes of a shot are generated, swapped and the best one kept |
| Higgsfield | History kept | Scenes, versions and deliverables are kept in subfolders; past takes can be reused as references |
| ImagineArt | None said | None said |
| LTX Studio | History kept | Projects keep assets, versions and decisions for one concept together |
| M Studio | History kept | Each frame keeps versions, with one marked as the active version |
| MagicLight | Pick from a set | Generating several versions and choosing the best is the suggested fix for inconsistency |
| Novi AI | None said | None said |
| OiiOii | None said | None said |
| Pexo | None said | None said |
| Pippit | None said | None said |
| PopShort AI | None said | None said |
| Revid AI | Undo history | Editing is not destructive; the editor keeps a full undo and redo history |
| SceneMixer | History kept | Every generation of a segment is kept, and the history control switches between them |
| Scenes AI | None said | None said |
| Story.com | None said | None said |
| StoryShort | None said | None said |
| Toonkit | History kept | Past generation history is kept and can be checked in the inventory |
| Topview Drama Studio | History kept | Generated video versions stay connected in the project with the storyboards and assets |
| TrendShort | None said | None said |
| Vivideo | Pick from a set | The same shot is run through several models and the best take kept |
Inclusion rule. All 28 editors on the register; an editor whose pages skip this behaviour shows not said. Order. Alphabetical by tool name.
1About this behaviour
Versions records whether earlier generations of a unit survive a redo. Eight editors keep a history the user can go back to; six return a set of results to pick from; one keeps an undo history in its editor. Thirteen say nothing.
A kept version is what lets a redo be tried without risk: if the new take is worse, the old one is still there. Picking from a set solves a different problem, choosing among alternatives made at the same time.
2Readings on this behaviour
- History kept: 8 editors
- Pick from a set: 6 editors
- Undo history: 1 editor
- None said: 13 editors
3Per-editor readings
- Character App — Pick from a set
- Crreo AI — Pick from a set
- DomoAI — Pick from a set
- Google Flow — History kept
- HeyGen — Pick from a set
- Topview Drama Studio — History kept
4The other behaviours
How an episode is built · Whether a redo is charged again · Whether a single shot can be redone · Who controls transitions · Whether a finished cut can be partly replaced