Rendition is an automatically generated copy of a master asset — resized, cropped, converted to a different format, or compressed for a specific use — created by the DAM itself rather than exported and saved manually by a person.
In plain English
Every team needs the same photo in different shapes: a full-resolution TIFF for print, a compressed JPEG for a website, a square crop for a social post, a tiny thumbnail for a grid view. Without renditions, someone manually exports each size and saves it as its own file, which means four or five near-duplicate copies of the same asset scattered across folders — and if the original gets replaced, all of those manual exports are now out of date and nobody notices.
A rendition solves this by generating those variants automatically from a single master, on request or on upload, rather than as separate stored files someone has to remember to update. Request the web-optimized version and the system creates (or serves a cached copy of) exactly that size and format, always derived from the current master, so there's never a stale manual export sitting around.
This is also what makes a version control question interesting: when a master gets replaced with a new version, well-built rendition systems regenerate every derived copy automatically, rather than leaving old thumbnails and web copies pointing at content that no longer matches the current master.
Why it matters in a DAM
Renditions are what let one master asset serve every channel without a library multiplying into dozens of manually managed near-duplicates. They matter most at scale: a tool that only stores one file per asset and expects people to export copies by hand will accumulate exactly the kind of duplicate-file mess a DAM is supposed to prevent, the moment more than one team needs the same photo in a different size or format.
Buyer’s test: ask a vendor to replace a master asset that already has several renditions in use, then check whether the existing web and thumbnail copies update automatically or keep serving the old version. Some tools only regenerate renditions on the next manual request, which can mean stale images sit live on a website for longer than expected.
Related terms
See it in action
Cloudinary is built almost entirely around on-the-fly rendition generation via API — see it discussed in our best AI DAM software ranking. For a more traditional catalog-based approach to renditions and exports, see our main DAM software ranking.