Archiving a Finished Edit So It Still Opens in Five Years

The call usually comes three or four years after delivery. A client wants a thirty second cutdown of the documentary, or a broadcaster needs the version without the music cue they lost the rights to. You find the drive, plug it in, open the project, and the timeline lights up red. Media offline. The title font has been swapped for Arial. A colour effect that came from a plugin you stopped paying for in 2023 now shows as a grey placeholder, and the editing application asks whether you would like to upgrade the project to the current version, which is a one way door.

None of that is bad luck. It is what happens when a finished edit gets stored as a working edit, with all the assumptions a working edit makes about the machine it lives on. I spent years receiving other people's archives as a subtitler and later as an archive lead, and I would guess fewer than one in five opened cleanly on the first try. The fix is not expensive. It is about forty minutes of deliberate work at the end of a job, done while you still remember what everything is.

Why a project that worked last month refuses to open later

An editing project file is mostly a list of instructions pointing at things stored elsewhere. Premiere Pro, DaVinci Resolve and Avid Media Composer all keep the footage, the music and the graphics outside the project, and they find those files by path. If the path was /Volumes/Job_Drive_04/Footage/Day2 and the drive now mounts as Untitled, every link breaks at once. Relinking is possible, but only if the file names survived, and camera cards love names like C0001.MP4 that repeat on every shoot day.

Then there are dependencies nobody wrote down. Third party effects, LUTs stored in a user library folder, fonts installed on one workstation, a sound effects pack the assistant downloaded to their own laptop. Each one lives outside the project and none of them travel with it unless you make them.

Software versions are the slowest problem. Resolve projects generally open forward but not backward, and Final Cut Pro libraries have to be updated when the application jumps a major version. Five years is long enough for at least two of those jumps. If your archive relies on one specific version of one application, you have built a museum piece that needs a museum.

The archive is not the project folder plus the drives

The common advice is simple: keep the project file, keep the drives, put them on a shelf. I understand why people say it, because it costs nothing on the day. It also leaves you with roughly four terabytes of raw footage you will never need and a project that cannot find any of it.

A useful archive has two layers with different jobs. The first layer is a finished master that plays anywhere without the editing software: a high quality file such as ProRes 422 HQ, plus the stems, plus caption files. The second layer is a trimmed, consolidated project that can be reopened for changes. Most re-edit requests can be handled from the first layer alone, which is why it matters more than the second.

If nobody can play your archive without the exact workstation you edited on, what you have is a backup of your desk, not an archive.

What goes into the folder

Here is the structure I hand to editors, with the reason for each part. The folder names are deliberately boring so that a stranger can guess the contents.

For the consolidated project, each application has its own tool. In Premiere it is Project Manager with "Collect Files and Copy to New Location", set to trim unused media with handles. I use 48 frames of handle, because 24 has bitten me when a client asked for a slightly longer shot. Resolve has File, Export Project Archive, which produces a .dra folder containing the project and its media. Final Cut Pro asks you to consolidate the library so the media sits inside it. In every case, open the result on a different machine before you call it done. If you only have one machine, rename the original job drive temporarily so the application cannot quietly reach it.

The caption folder deserves a note. If the delivery used burned in subtitles, archive the text files anyway, for the reasons covered in which caption formats survive re-uploads. A text file of subtitles is a few kilobytes and saves days of retranscription.

The README is the part people skip

I care about this file more than anything else in the folder, partly because it is the cheapest thing in it. Mine has the same headings every time: client and project name, delivery date, the editing application and exact version, the operating system, a list of plugins with versions, fonts used, where the music licences are, who edited and who coloured, and any known quirks. A typical quirk line reads something like "Scene 14 uses a speed ramp that renders differently after Resolve 18.5, check against the master."

Write it as if the reader is a freelancer you have never met, because that is often who opens it. Avoid internal shorthand. "The Tuesday cut" means nothing to anyone outside the edit suite that week.

If you already organise jobs with a consistent folder plan from day one, as described in organising an edit before the first cut, most of this README writes itself, because the structure is already labelled.

Where the archive should actually live

Two copies on different kinds of storage, one of them away from the building, is the minimum I would accept. For small studios that usually means one external hard drive kept on site and one copy in cloud storage or on a drive that lives at someone's home.

Hard drives fail in storage as well as in use. Backblaze, which publishes failure statistics for its data centre fleet, has reported annualised failure rates in the region of 1.4 to 1.7 percent in recent years, and those are drives that spin constantly in climate controlled racks. A drive sitting unpowered in a cupboard has its own risks. I plug archive drives in once a year, check that the folders open, and copy anything older than five years onto a fresh drive. It takes an afternoon in January.

Checksums help here. Tools such as Hedge or ShotPut Pro can write xxHash or MD5 values when you copy, and comparing them a year later tells you whether a file has silently changed. Without them you only find corruption when a frame glitches during the client call.

LTO tape is the serious option for studios with large volumes. An LTO-8 cartridge holds 12 TB natively and is rated for decades on a shelf, but the drives cost several thousand dollars and you need a working drive to read the tape later. For a freelancer with a dozen jobs a year, two hard drives and a cloud copy is the better trade. I have not seen a solo editor regret skipping tape, though my sample is small and skewed towards documentary work.

One job to do this week

Pick the most recent project you delivered, the one you still remember clearly. Export the master and stems into a new folder, write the README with the headings above, and run your application's consolidate tool on the project. Then open it on a second computer, or with the job drive renamed, and fix whatever breaks. Write down what broke in the README too. After one archive done properly, the next one takes half the time, and you will have a template for every job you finish in the video editing side of your work from now on.