Short answer
A rendition is a derived version of an asset in a specific format, size or crop for a particular channel. DAMs generate renditions automatically from the master file. A rendition stays correct only while the DAM links it to its master, so replacing a master must regenerate every rendition that channels use.
How renditions work in a DAM
Renditions work through rendition profiles, which are presets that define how the DAM derives a file from its master. Each profile sets the output format, pixel dimensions, crop, colour space, compression and file name pattern.
A DAM produces renditions in one of two ways:
- Stored renditions: the DAM generates the file on ingest or on first request and keeps it in storage.
- Dynamic renditions: the DAM or an image CDN generates the file at delivery time from URL parameters.
Every rendition inherits metadata from its master. A well-configured DAM also writes selected fields, such as copyright and alt text, into the rendition file itself.
Worked example of a rendition profile set for a consumer brand:
| Profile | Format | Size | Use |
|---|---|---|---|
| Marketplace | WebP | 1200 by 1200 pixels | Retail partner listings |
| Web hero | JPEG | 2400 pixels wide | Brand website banners |
| Social portrait | JPEG | 1080 by 1350 pixels | Social feeds |
| TIFF, CMYK | Full resolution | Brochures and packaging proofs |
Example of a rendition
Worked example: a product photographer delivers one 50 megapixel TIFF master. The DAM creates a 1200 by 1200 pixel WebP of the product photo for a marketplace, plus web, social and print renditions from the same master.
Three months later, the studio reshoots the product. The editor replaces the master, and the DAM regenerates all four renditions. The marketplace feed picks up the new WebP through its existing link.
Rendition in a DAM selection
Renditions are defined at Checkpoint 2: Define, when the buyer lists every channel and its file specification. Vendors then prove rendition handling at Checkpoint 5: Test with your profiles and your masters.
Ask each vendor to show these points:
- Configure your channel profiles without vendor engineering.
- Replace a master and show every rendition update, including links already published.
- Apply a smart crop that keeps the product in frame for a square format.
- Keep embedded copyright, alt text and content credentials in the rendition.
- Show whether renditions are stored or generated on request, and how each option is priced.
DAMSelection assessment: storage, egress and AI credit consumption drive five-year DAM cost more than licence fees. Stored renditions multiply storage, so model them in the TCO calculator. Add your profiles to the requirements checklist.
Common rendition mistakes
The most common rendition mistake is exporting channel versions by hand and uploading them as separate assets. Other recurring errors:
- Renditions that lose embedded metadata, so copyright and alt text disappear downstream.
- No naming convention, so channel teams cannot tell renditions apart.
- Too many stored profiles that no channel uses.
Related terms: Transcoding, Dynamic media, Image CDN.
Frequently asked
What is the difference between a rendition and a master file?
A master file is the highest-quality original that the DAM stores and protects. A rendition is a derived file made from that master for one channel. Users edit or replace the master, and the DAM regenerates renditions from it.
Should a DAM store renditions or generate them on request?
A DAM should store renditions that channels request constantly and generate rare formats on request. Stored renditions cost storage, while on-request generation costs processing and depends on a CDN. Model both options with your real channel volumes before signing.