Archive Triage: Deciding What Deserves Long-Term Storage
Most creator media libraries do not fail because of a single bad decision. They fail because files accumulate without a rule for what gets kept, what gets reviewed, and what gets quietly deleted. Before you think about folders, formats, or storage locations, it helps to decide what an archive is for. An archive is not a dumping ground for everything you have ever produced. It is a curated record that should serve a purpose you can name. This article takes a different angle from general filing advice: it focuses on triage, the step that happens before anything is stored, and on the questions that determine whether a file deserves a place in the archive at all.
Start with the purpose, not the storage
Every useful archive begins with a short statement of purpose. Write one or two sentences describing what the archive must let you do. For example, you might need to find a specific clip for a revisited topic, reuse an image in a new layout, or prove the date on which a piece of work was published. Each purpose implies different keeping rules. A reference archive needs strong descriptions and consistent names. A publishing archive needs final exports and the source files behind them. A personal record needs chronology above all else.
Without a purpose, every decision becomes a guess. You will keep files because they feel important, delete others because they look redundant, and then discover months later that the file you removed was the only surviving copy of something you needed. A written purpose gives you a test to apply to each file: does keeping this serve the stated purpose, and would losing it prevent the purpose from being met?
A triage method for incoming files
Triage is the act of sorting incoming material into three groups: keep in the archive, keep only in working storage for now, and discard. Apply it at the moment files arrive from a shoot, an edit session, or a publishing run, rather than months later when the context has faded. Work through a short sequence of questions for each file or batch. Is this the final version, a working draft, or a duplicate? Does it show something that is not captured elsewhere? Would someone searching for this later find it useful? Is there a reason it might need to be re-exported or re-cut in the future?
A practical checklist for this stage looks like this, written as plain steps you can repeat. First, separate finals from drafts so that a rough cut never masquerades as a finished piece. Second, check for duplicates by comparing file size, duration, and dimensions before comparing content. Third, confirm that each keeper has a readable name and a date. Fourth, move anything you are unsure about into a holding folder with a review date attached, rather than deciding under pressure. Fifth, record in one line why each kept item matters. This final line is the most neglected step and the most valuable one later, because it preserves the reasoning that the file alone cannot show.
Comparing keep, hold, and discard decisions
Keeping a file is not automatically better than discarding it, and discarding is not automatically tidy. Compare the costs honestly. Keeping everything inflates your archive, slows searches, and makes review tedious, which means the archive stops being used. Discarding aggressively can remove the source material you would need to rebuild a finished piece, or the context that explains why an earlier decision was made. A hold category sits between the two, and it is where most uncertain material belongs. Give holds an expiry, such as a review date three or six months out, so they do not become permanent clutter.
When comparing options for a specific file, ask what it costs to be wrong in each direction. If discarding a file would make a future project impossible to finish, lean toward holding it. If keeping a file would only add noise that no one will search for, lean toward discarding it, provided a final version exists elsewhere in the archive.
Questions to ask before you commit anything
Before any file enters the long-term archive, pause and answer a few questions in writing. Can I name what this file is and when it was made? Is there a clearly marked final version of the work it belongs to? Does the file depend on other files, such as fonts, linked assets, or source footage, and are those dependencies kept with it? Who else might need to find it, and will the name and description make sense to them without my memory of the project? Will I be able to open this file in the formats I use now, and what would I need to do to open it in five years?
These questions are not a test you pass once. They are a review habit. Revisit the triage decisions on a regular schedule, perhaps each quarter, and look specifically for holds that have passed their review date. Ask whether the purpose you wrote down still matches what you are actually doing. If it no longer does, update the purpose and reassess the archive against it rather than letting the old rules continue by default.
The outcome of good triage is not a perfect archive. It is an archive where every kept item has a reason, every uncertain item has a deadline, and every discarded item was discarded on purpose. That standard is achievable with a small amount of discipline applied at the moment of decision, and it makes every later task of finding, reusing, and reviewing your media considerably easier.