Reference Glossary
Derivative asset
Any resized, cropped, reformatted, watermarked, or color-converted copy generated from a master file for a specific use, channel, or output requirement.
Why it matters in a DAM
Derivatives are what people actually download and use — a marketer never touches the 400MB TIFF, they grab the pre-made 1080×1080 square crop. Without generation rules tied back to the master, teams end up hand-exporting the same image dozens of times with slightly different crops and compressions, none of them traceable to which master they came from if the source gets replaced.
A worked example
Common mistake
Derivatives get edited directly and re-uploaded as standalone assets with no link back to the master, so when the product is reshot, the old derivatives keep circulating in decks and emails because nobody knows they need replacing.
Most of what a DAM’s users touch day to day is derivatives, not masters. A well-configured system generates them automatically on ingest or on demand from a set of presets — a specific crop ratio and file size for Instagram, a CMYK conversion at print resolution, a compressed thumbnail for the search grid — rather than requiring someone to open the master in an editor and export it by hand each time a size is needed.
The value of a derivative depends entirely on staying linked to its master. That link is what lets the system regenerate every derivative automatically when the master is corrected — a color grade fixed, a logo updated — instead of leaving stale copies in circulation indefinitely. It also means rights and usage restrictions attached to the master (a stock license limited to digital use, say) can be checked before a print-resolution derivative is even generated.
Presets matter more than they look like they should: the fewer times a human has to manually export a one-off size, the fewer untracked copies end up living outside the DAM in someone’s local export folder.
Frequently asked
How does a derivative asset differ from a master file?
A derivative is any resized, cropped, reformatted, watermarked, or color-converted copy generated from a master for a specific use — like an 800x800 sRGB web JPEG made from a 4000x4000 CMYK master. It's what most DAM users actually touch day to day, not the master itself.
Why should derivatives be generated from presets rather than exported by hand?
Presets — a fixed crop ratio and size for Instagram, a CMYK conversion at print resolution — mean fewer one-off manual exports, which means fewer untracked copies ending up outside the DAM in someone's local export folder.
What breaks when a derivative loses its link back to the master?
The system can no longer regenerate it automatically when the master is corrected, so if a color grade is fixed or a logo updated, stale derivatives keep circulating instead of being refreshed.
What happens if a derivative is edited directly and re-uploaded as a standalone asset?
It loses its traceability to the master. When the product is reshot later, the old derivative keeps circulating in decks and emails because nobody knows it needs replacing.
Can rights restrictions on a master affect what derivatives get made?
Yes — a stock license limited to digital use, for example, can be checked against the master's rights record before a print-resolution derivative is even generated, provided the derivative stays linked to that master.
Why does a preset library matter for controlling asset sprawl?
The fewer times someone has to manually open a master and export a new size, the fewer slightly different, untracked copies get created and scattered outside the DAM.