Version control in editorial usually means a folder of dated project copies and a prayer that you saved the right moment. Somebody duplicates the project "just in case," the copies drift, and when a director asks to see yesterday's cut, you're hunting through v2_final folders instead of watching it.
Sequence records edit history as part of the project itself. Every change is captured continuously, with no manual saving, and because the history is shared, anyone in the project can scrub back through it. Time Travel gives you a slider across a timeline's whole history — so you can jump to how it looked hours or days ago and either restore that state or branch a new timeline from it. See Browse history with Time Travel.
Unlike undo and redo, which step through changes one at a time, Time Travel lets you jump straight to any earlier point. Scrub the slider and the timeline below updates live — you watch clips move and trim back to where they were. When you find the state you want, you have two clean options.
Two ways to use the past#
Branch a new timeline — non-destructive
- Scrub to the state you want and click Duplicate Timeline in the Time Travel bar
- Sequence creates a new "Copy of" timeline at that exact point and leaves your current one untouched
- Ideal for exploring an alternate cut without disturbing the main one, or comparing two directions
Revert the timeline
- Scrub to the state you want to return to and click Revert Timeline, then confirm
- Sequence replaces the current timeline's contents with that past version
- The revert is itself recorded in history, so you can move forward again and recover the newer state
History is shared
Time Travel reflects the edits everyone has made, because history is part of the shared, multiplayer project — not a local save on one machine. See Edit together in real time.
Enter Time Travel from the Sequence menu under Project History > Time Travel, or press ⌘ ⇧ H (Windows: Ctrl ⇧ H). It works on the timeline you have selected, affecting only that timeline's history.
Fits your finishing workflow#
Because branching is free and non-destructive, you can duplicate a locked cut before you start a conform pass, keep the original pristine, and hand the branch off downstream. The edit round-trips out to the finishing tools you already run — AAF for Pro Tools, FCP7 XML, and OpenTimelineIO for Resolve, Flame, and beyond — so a version you saved in Sequence isn't trapped there.
Who it's for#
- Editors exploring multiple cuts without spawning a folder of project copies
- Directors and producers who want to compare yesterday's cut against today's
- Assistant editors branching a clean version before a conform or delivery pass
- Distributed teams who need one shared, recoverable history instead of scattered saves