Sorting Mixed-Format Creator Files: Separating Masters, Previews, and Drafts
Creators who publish across several platforms often end up with a folder that holds everything at once: raw captures, edited exports, compressed previews, thumbnails, and half-finished drafts. The problem is rarely storage space. It is that nothing in the folder tells you which file is the version you intend to keep, which one is a copy made for a specific purpose, and which one can be deleted. This article describes a three-tier approach for mixed-format creator files that makes those roles visible from the file system itself. It is a general method you can apply to any media library, whatever tools you use to produce or share your work.
Why mixed formats cause confusion
A single piece of content can exist in many forms. A video might start as a camera original, become an edited master with color and sound adjustments, then be exported as a short vertical clip, a compressed preview, and a still thumbnail pulled from one frame. Each of these files looks similar at a glance, especially in a list sorted by date. Over time you lose track of which one is authoritative.
The confusion grows when filenames are generic, such as final, final2, or export_new. Without a rule, people guess, and guessing leads to re-exporting from the wrong source or deleting the only high-quality copy. A consistent structure removes the guesswork by stating each file's role in its location and name.
The three tiers: masters, deliverables, and working files
Separate your library into three top-level areas. The first is masters: the highest-quality version of each piece, including original captures and finished edits that you would use to make any other format. Masters should be treated as the source of truth and rarely modified after they are finalized.
The second tier is deliverables: files made for a specific destination, such as a compressed clip sized for a particular feed, a still image cropped for a profile preview, or a low-resolution copy for sharing. Every deliverable should be traceable back to a master. If you cannot say which master produced a deliverable, the deliverable is a candidate for review.
The third tier is working files: drafts, sketches, rough selects, and experimental cuts. These are expected to be messy and are the first candidates for cleanup. Keeping them in a clearly labeled folder prevents them from being mistaken for finished work.
A naming pattern that carries the role
Make the tier visible in the filename. A simple pattern is date, subject, tier, and version, written in a consistent order with no spaces, for example 2026-03-14_harbor-walk_master_v2 or 2026-03-14_harbor-walk_preview-720_v1. The date sorts chronologically, the subject groups related files, the tier tells you the role, and the version distinguishes revisions.
Use the same subject label across all tiers of one piece of work. When you search for harbor-walk, you should see its master, its deliverables, and any working files together. Avoid encoding resolution or platform names in the master file, since a master should stand on its own, while deliverables can carry those details because their purpose is specific.
A practical checklist for each new batch
Use this checklist whenever you finish a batch of files. First, confirm that the master is saved in its own folder and not overwritten by an edit. Second, record which master each deliverable came from, either in the filename or in a short plain-text note stored beside the folder. Third, move every draft and rough cut into the working files area, and mark any you no longer need for deletion review. Fourth, check that each deliverable's version number matches the master version it was made from.
Ask yourself several questions before you delete anything. Is there another copy at a higher quality? Could this file be regenerated from a master in a few minutes? Does it show a version that was published anywhere, and if so, do you need to keep it for reference? A file that fails all three questions is probably safe to remove. Keep a short log of deletions for large batches so you can recover your reasoning later if needed.
Finally, schedule a light review every few months. The goal is not perfection but a library where the role of every file is clear. A quick pass that moves stray files into the correct tier and checks a sample of deliverables against their masters will keep the structure from decaying as your output grows.