Choosing Between Source Masters and Public Previews in Creator Media Libraries

Jessica Irving editorial ·

Aufbau von Blitzanlage und Zubehör.
Illustrative image. Christoph Braun · CC0 · Cropped and resized. Image source

Creators who publish work under a name like Jessica Irving often end up with two versions of nearly every file: the full-resolution original kept on a working drive, and a lighter copy used for public profiles and posts. Mixing these up causes wasted storage, accidental publication of unfinished cuts, and confusion when someone asks which version is the real one. This article lays out a method for keeping masters and public copies apart, using plain questions and a simple checklist that works regardless of which tools you use.

Define what a master actually is

A master is the most complete version of a file you are willing to keep. For a photo it is usually the unedited or minimally edited raw capture; for a video it is the highest-quality export before compression for a specific platform. The master is the file you return to when you need to make a new crop, a new export, or a new edit.

Before organizing anything, write one sentence that defines the master for each media type you produce. If you cannot write that sentence, you do not yet have a consistent archive, and any folder structure you build will drift over time.

Treat public previews as derived copies

A public preview is anything generated from a master for an audience: a compressed video, a resized image, a watermarked still, or a short clip cut for a feed. Previews should always be traceable back to their source. A useful habit is to store the preview's source filename and export settings in the file name or in a simple text log beside it.

Derived copies are disposable in the sense that you can regenerate them. Masters are not. Keeping that distinction clear tells you which files deserve backup attention and which can be recreated when needed.

A checklist for separating the two

Work through these questions for each batch of files before you move them into storage. Question one: is this the highest-quality version of the content that still exists? If yes, it is a candidate master. Question two: was this produced for a specific destination such as a feed, a profile banner, or a thumbnail? If yes, it is a preview. Question three: can you recreate this file exactly from another file in your collection? If yes, it is derived and need not be kept as a separate master. Question four: does this file contain unreleased material, unfinished edits, or private notes in its metadata? If yes, keep it out of any folder that syncs to public or shared locations.

Record your answers in a short log. Even a plain spreadsheet with columns for filename, type, source, destination, and notes will prevent most confusion later.

Keep naming consistent across both copies

When a master and its preview share a stem name, a reader can see the relationship at a glance. For example, a master called session-014-raw and a preview called session-014-feed-square make the link obvious. Avoid naming previews with vague words like final or new, because those labels become misleading once a second revision appears.

Consistent naming also helps when you audit your archive. A quick scan can reveal previews that have no matching master, which often signals that the master was deleted by mistake or never saved in the first place.

Review the split on a regular schedule

Set a recurring time, perhaps once a month or after each batch of new work, to check that the separation still holds. Look for public previews stored in master folders, masters that were accidentally compressed, and duplicate files that differ only by export settings. Resolve these by moving files to the correct location and updating your log.

The goal is not a perfect system on the first attempt. It is a system you can read quickly, trust, and maintain without rebuilding it every time your output grows.