How to Version a Video Edit So You Can Go Back
A producer wrote to me on a Thursday asking for the cut as it stood on Tuesday afternoon. Not a note, not a tweak: the whole sequence, because a legal reviewer had signed off on that version and the client had since changed their mind...

A producer wrote to me on a Thursday asking for the cut as it stood on Tuesday afternoon. Not a note, not a tweak: the whole sequence, because a legal reviewer had signed off on that version and the client had since changed their mind twice. The project file had been saved perhaps forty times since then. Autosave held the last nine hours. Tuesday afternoon was gone, and rebuilding it from memory took me most of a day that nobody paid for.
I now version edits the way I version subtitle deliveries for broadcasters, which is to say obsessively and with dates in the filename. It is not an elegant system. It has saved me four days of rework in the last two years, and twice it settled an argument about who approved what.
What Actually Disappears When You Save Over an Edit
Most editors assume the project file holds history. It holds state. When you drag a clip two frames left and save, the previous arrangement stops existing anywhere, unless something outside the editor kept a copy.
Autosave is not that something. Premiere writes autosaves into a folder with a cap, twenty files by default, at an interval often set to fifteen minutes. On a busy day that window covers five hours. Resolve keeps a live project database and a separate backup interval, and the backups also roll off. Final Cut's library snapshots are closer to real versioning, but a snapshot you never took is no help on Thursday.
The second thing that vanishes is the reasoning. Six weeks later I can see that a 14 second segment was removed. I cannot see that it was removed because the brand team flagged a logo on a coffee cup. That note lived in an email thread I no longer have access to. Metadata about why is worth more than people expect, which is the same argument I make about archiving a finished edit.
A Naming Rule That Still Sorts in Three Years
Two parts, and both matter. Start the filename with the project short code, then an ISO date, then a version number with a leading zero, then one or two words about the state. Something like ORBIT_2026-11-19_v04_legal-pass.prproj.
ISO dates sort correctly in every file browser on earth and never leave you guessing whether 11-09 was September or November. The leading zero keeps v09 ahead of v10 instead of after it. The trailing words are the part editors skip and later wish they had, because v04 means nothing in February while "legal-pass" means everything.
I use whole numbers only for versions a human outside the edit has seen. Internal fiddling stays in the same file. If I send a link to a producer, that becomes a numbered version and it does not get edited again, ever. A version someone approved is a record, and editing it quietly is how approval disputes start.
One rule that cost me a weekend to learn: never put the word final in a filename. A game studio I subtitled for had six files in the chain ending in final, final2, reallyfinal, and final-use-this. Two different people delivered two different ones to the same storefront. Dates and numbers do not lie about order.
Why Duplicating the Sequence Before Every Change Is the Wrong Habit
The advice you hear in editing forums is to duplicate the sequence inside the project each time you start work, so you can always step back. I did this for years. I think it is actively bad for most solo editors and small teams.
The problem is that in-project duplicates share one file. If the project file corrupts, which happens roughly once a year for me across maybe sixty projects, all forty duplicate sequences go at once. I lost an eleven minute corporate piece this way in 2024 and the forty sequences in that project were worth exactly nothing.
The other problem is cognitive. A bin with thirty sequences named Main_copy_copy_03 becomes unsearchable, and you stop trusting any of them, so you stop stepping back at all. The duplicate habit creates the feeling of safety without the thing itself.
What I do instead: one sequence in the project, and separate project files on disk for versions. Duplicate the whole project with Save As under the naming rule, then keep working. The file is small, usually 4 to 40 MB for a long edit, because media stays where it is. Forty project versions of a documentary cost me less disk than one minute of the camera original.
I will grant the counter-argument. In-project duplicates are faster to compare side by side, and if you are doing three variants of the same 30 second spot for an A/B test, keeping them in one project is correct. For linear progress through one edit, separate files win.
When to Snapshot, Not How Often
Interval-based versioning produces noise. Event-based versioning produces a usable trail. These are the moments that get a new numbered file in my work, with rough frequency from the last year of projects.
| Trigger | New version? | Why it matters later |
|---|---|---|
| Before sending any review link | Yes, always | Pins what the reviewer actually saw |
| After applying a round of notes | Yes | Lets you show what changed, note by note |
| Before a structural change, moving or cutting a whole act | Yes | The one change you cannot undo your way out of |
| Before relinking or remapping media | Yes | Bad matches are hard to unpick in place |
| Before starting the grade or the mix | Yes | Separates picture decisions from look decisions |
| Trimming, timing, caption tweaks | No | Autosave covers a same-day mistake |
| End of each working day | No, unless something shipped | Creates volume without information |
The relink line is there from experience. A wrong folder match can silently attach the wrong take to twenty cuts, and discovering it two days later is grim. Keeping a pre-relink project file means the fix is opening yesterday's file rather than auditing every edit point. The mechanics of doing it carefully are in relinking offline media.
Where the Files Live
Project versions go in a folder next to the media, not inside it. My layout is a project root with 01_media, 02_project, 03_exports and 04_delivery. Everything versioned sits in 02_project, which for a typical job is under 500 MB and therefore cheap to sync to cloud storage even when the media is far too large to.
That split is the whole point. Media is replaceable from camera cards or from the client. Project files are the only unique artefact you made, and they are small enough that there is no excuse for one copy. I keep the project folder in a synced drive and the media on a local SSD with one backup, which has felt like the right ratio of care to cost.
Exports get the same naming rule as projects, matching version numbers. When a client says the cut from the fourth review had the right music, I can go from the export filename to the project file without opening anything. That mapping is the detail that makes the whole scheme pay off, and it takes no extra work if you set the export preset filename once. More of this kind of housekeeping sits in the editing archive.
FAQ
Does version control software work for video projects?
Git handles the project file fine and handles media badly. Some teams run Git on the project folder only, with media excluded, and it works. For one or two people, dated Save As files are simpler and fail in ways you can predict.
How many versions should I keep after delivery?
I keep the approved delivery version, the last working version, and any version that a reviewer signed off on. Everything else goes about a month after final payment. That is usually three to five files out of twenty.
Will opening an old project version break my current one?
No, as long as they are separate files and you do not save over the current one. The risk is Resolve, where projects live in a database rather than loose files, so import the older project under a new name instead of restoring over the live one.
What about collaborative cloud projects?
Shared project systems log changes but they log them for the project, not for your approval trail. I still export a dated local copy before each review round, because a shared history is only useful while everyone keeps paying for the service.
More in Video Editing
Video Editing
Loudness Targets for Video and Why Platforms Turn It Down
A 42 minute interview film I mixed last spring came back from the client with one note: the music is louder than the people.
Video Editing
How to Build a Paper Edit From Interview Transcripts
Six hours of interviews came back from a shoot in Trieste and I had four weeks to turn them into a 24 minute film.
Video Editing
Relinking Offline Media Without Rebuilding Your Edit
You open a project you were cutting last week and the timeline is a wall of red frames with "Media Offline" stamped across...