A rendition is a derived copy of an asset, generated from the original for a specific purpose: a thumbnail for browsing, a web-sized JPEG of a 2 GB layered design file, a low-resolution proxy of a video, or a PDF preview of a presentation. The original stays untouched; renditions are the working faces it shows the world.

Renditions are what make a mixed-format library usable. Most people who need an asset cannot open its source format — they don't have the design software, the codec, or the patience for a multi-gigabyte download. A DAM generates renditions automatically at ingestion, so every asset is browsable as an image in the grid and available in sensible delivery formats, regardless of what arrived. This is also a governance tool: audiences can be limited to specific renditions, so a reseller downloads a web-ready image while the layered source file stays with the design team.

The quality bar for renditions is coverage. A library where a tenth of the assets show a generic file icon instead of a preview trains people to distrust the browse view. Coverage across camera RAW formats, design files, office documents, video, and audio is what separates a real asset library from a file list.

In freedam, previews and renditions are generated for more than 138 file types, so RAW photos, layered design files, documents, and video all render as browsable previews in the library.

Related terms: Watermarking, Ingestion, Version Control