Short answer
Dynamic media is the on-request generation of renditions, crops and formats from a master asset at delivery time. One master can serve many sizes through URL parameters, so the library stores fewer derivative files. Dynamic media pays off when a catalogue publishes the same image to 3 or more channels, screen sizes or formats.
How dynamic media works in a DAM
Dynamic media generates a rendition at the moment a website, app or feed requests it. The request URL names the asset and the operations, such as width, crop ratio, quality and output format.
The delivery chain runs in four steps:
- A channel requests an image URL with parameters or a named preset.
- The dynamic media service fetches the master from DAM storage.
- The service resizes, crops, sharpens or converts the file and returns the result.
- An image CDN caches the result at the edge, so the next request skips processing.
Named presets lock approved sizes and crops for brand use. Free parameters give developers flexibility but let any page request any crop. Format negotiation uses the browser's Accept header, defined in HTTP semantics, to serve WebP or AVIF where supported.
Example of dynamic media
Worked example: a retailer holds 20,000 product masters and publishes 8 fixed sizes per image. Stored renditions would mean 160,000 derivative files to generate, store and refresh after every retouch.
With dynamic media, the retailer stores 20,000 masters. A product page requests a 600 pixel square crop in automatic format, and the CDN caches it. When the studio replaces a master, the DAM purges the cache and every size updates on the next request.
Dynamic media in a DAM selection
Dynamic media belongs at checkpoint 2, Define, where the buyer lists channels, sizes and formats. Cost belongs at checkpoint 6, Score. DAMSelection assessment: storage, egress and processing volume drive five-year DAM cost more than licence fees.
Test these four behaviours at checkpoint 5, Test:
- Request three crops of a buyer asset through URLs and show the results.
- Replace the master and show how fast the new version reaches the cached URLs.
- Show how presets restrict crops for brand-controlled channels.
- Show the usage metric the vendor bills on, with a sample monthly report.
Model the delivery volume in the TCO calculator and compare pricing metrics with the DAM pricing guide. Ask every vendor for the billing unit in writing before scoring.
Common mistakes with dynamic media
Dynamic media projects fail through four common mistakes.
- Opening free parameters to every developer, which produces off-brand crops on live pages.
- Skipping cache purge rules, so replaced or expired images stay live at the edge.
- Leaving request and bandwidth volume out of the total cost model.
- Expecting dynamic media to cover print. Print and packaging still need fixed, approved files.
Related terms: Rendition, Image CDN.
Frequently asked
Is dynamic media the same as an image CDN?
Dynamic media and an image CDN are two layers of one delivery chain. Dynamic media generates the rendition from the master. The image CDN caches and serves that rendition close to the user. Some platforms bundle both, and others pair a DAM with a separate CDN.
How is dynamic media priced?
DAMSelection assessment: vendors price dynamic media on delivered bandwidth, request volume, processing units or a bundle inside a platform tier. Ask for the billing unit, the overage rate and a sample report, then model three years of traffic growth in the cost comparison.