Timeline term: version history
A version history keeps every earlier generation of a unit, so a replaced result can be restored. Eight editors say they keep one. From 8 source pages, read 2026-09-25; no maker pays to be listed.
The history is useful only if a version can be made active again; several editors describe switching or saving an older version back into the cut.
An undo history is narrower: it reverses edits in a session rather than storing every generation.
1How editors use it
| Editor | What the pages say | Behaviour |
|---|---|---|
| Crreo AI | Each regeneration returns three variations to choose from; past work stays in Tool History | Versions |
| DomoAI | A scene is generated, reviewed, and the best version carried into the next episode | Versions |
| Frameo | A lesson on timeline versions is part of the guide; pipelines are described with versioning | Versions |
| Google Flow | Editing keeps the original; the History panel holds every previous version and its prompt | Versions |
| HeyGen | Several takes of a shot are generated, swapped and the best one kept | Versions |
| Higgsfield | Scenes, versions and deliverables are kept in subfolders; past takes can be reused as references | Versions |
| LTX Studio | Projects keep assets, versions and decisions for one concept together | Versions |
| M Studio | Each frame keeps versions, with one marked as the active version | Versions |
Inclusion rule. Editors whose logged statements use the term or its usual equivalent; one line each. Order. Alphabetical by tool name.
Each regeneration provides three variations — select your favorite and confirm with Replace with Selected Image.
Crreo, video maker tutorial
generate a 4-30 second scene, review the faces and lip sync, then remix the best version into your next episode.
DomoAI, AI drama generator page
- Step 4, thumbnail and visualsEach regeneration returns three variations to choose from; past work stays in Tool History
- How to make an AI dramaA scene is generated, reviewed, and the best version carried into the next episode
- Guide, going furtherA lesson on timeline versions is part of the guide; pipelines are described with versioning
- Edit your video clipsEditing keeps the original; the History panel holds every previous version and its prompt
- FAQ, turnaroundSeveral takes of a shot are generated, swapped and the best one kept
- SubfolderingScenes, versions and deliverables are kept in subfolders; past takes can be reused as references
- ProjectsProjects keep assets, versions and decisions for one concept together
- API, framesEach frame keeps versions, with one marked as the active version
2How one pipeline handles it
The episode pipeline SceneMixer documents has its own answer to “Version history”; two lines from its pages:
The second trim replaces the first trimmed version; the generated clip stays in Version History.
SceneMixer, Trim a Clip: Cut the Start or the End Without Regenerating — “Can I trim the same clip twice?” (read 2026-10-13)
Downloads and the asset library follow your Music switch; a shared link always plays the version with the episode’s music.
SceneMixer, Background Music in an AI Short Drama: The Built-in Score — “Does the music carry into downloads, the library and shared links?” (read 2026-10-13)