Reference Glossary
Master file
The unedited, highest-resolution version of a digital asset, stored once and never overwritten, from which every resized, cropped, or reformatted copy is generated.
Why it matters in a DAM
A DAM without a locked master file eventually loses the original: someone edits a derivative JPEG and re-uploads it as the new 'best' version, and the true source resolution or unedited color data is gone for good. Print production, re-cropping for a new channel, and future format conversions all depend on that untouched original still existing.
A worked example
Common mistake
Teams upload an already-compressed JPEG as the 'master' because that's the file a photographer emailed over, then discover a year later there's no way to produce a clean print file or a properly cropped square version without visible artifacts.
A master file is the reference copy of an asset: the camera RAW, the layered design file, the uncompressed export straight out of production, before anything has been resized for a website or converted to CMYK for a printer. It carries the maximum resolution, the full color gamut, and none of the compression artifacts that later renditions will pick up. Everything else stored against that asset in the DAM is downstream of it.
Treating it as a master in practice means locking it: read-only permissions for everyone except a small group of admins, a checksum or hash recorded on ingest so any later corruption or accidental overwrite is detectable, and a naming or metadata convention that makes it unambiguous which file in a record is the master versus a derivative. Storage cost is the usual objection — a RAW or layered TIFF can be a hundred times the size of the JPEG everyone actually downloads — but that cost buys the ability to regenerate any output format later without reshooting or recreating the file.
The failure mode shows up slowly. A team without a disciplined master starts substituting whatever the highest-quality copy they can currently find, and each substitution quietly lowers the ceiling: a screen-resolution export becomes the de facto master, then someone needs a billboard crop and there’s no path back to source quality.
Frequently asked
What exactly counts as a master file in a DAM?
It's the highest-resolution, unedited version of an asset — the camera RAW, the layered design file, or the uncompressed export straight out of production — before any resizing, cropping, or format conversion. Everything else in the record, from web JPEGs to CMYK print files, is a derivative generated from it.
Why lock the master file as read-only?
Locking it to a small group of admins prevents someone from editing a derivative and re-uploading it as the 'new' master, which would quietly replace the true source resolution and unedited color data. A recorded checksum on ingest makes accidental corruption or overwrites detectable too.
What's the risk of uploading an already-compressed JPEG as the master?
A year later there's no way to produce a clean print file or a properly cropped square version without visible artifacts, because the highest-quality source was never actually captured. This usually happens simply because that's the file a photographer emailed over.
Isn't storing a huge RAW file next to a tiny web JPEG wasteful?
The storage cost is real — a master can be a hundred times the size of the derivative people actually download — but it buys the ability to regenerate any output format later without reshooting or recreating the file.
How does a DAM signal which file in a record is the master versus a derivative?
Through a naming or metadata convention that makes it unambiguous, combined with the master being locked to admin-only editing so it can't be casually replaced by a derivative.
What's the slow failure mode when master-file discipline breaks down?
Each unauthorized substitution quietly lowers the ceiling: a screen-resolution export becomes the de facto master, and later, when someone needs a billboard crop, there's no path back to source quality.