Content operations
Dynamic media and image CDNs: delivering assets at scale
Quick answer
Dynamic media is the capability to generate image and video renditions on request from one master file, resizing, cropping, compressing and converting formats per device. An image CDN caches those renditions at edge locations close to users. Together they remove pre-made derivative files, speed up page loads and keep every channel tied to the approved asset in the DAM.
Key takeaways
- Images appear on 99.9% of web pages and are the Largest Contentful Paint element on 68% of mobile pages (HTTP Archive Web Almanac 2024).
- AVIF made up only 1.0% of image requests on mobile in 2024, while browsers covering over 96% of global usage support it, so automatic format negotiation is a fast performance gain.
- Three delivery architectures exist: DAM-native dynamic media, a standalone image CDN in front of the DAM, and a general CDN with image processing at the edge.
- Bandwidth, rendition volume and cache purges are the main cost drivers; model them on monthly page views before signing a contract.
Dynamic media and image CDNs let a DAM deliver one master asset in hundreds of sizes and formats without anyone exporting derivatives by hand. The DAM keeps the approved original; the delivery layer generates the right rendition for each device on request and caches it at the network edge. For e-commerce and content-heavy sites, this layer has a direct effect on page speed, search visibility and rights control.
What dynamic media and an image CDN do
Dynamic media is rendition-on-request: a URL carries parameters for size, crop, quality and format, and the service generates that variant from the master file. An image CDN (content delivery network) caches each generated variant at edge locations, so the second request for the same variant is served in milliseconds. The two are often sold as one product. The practical result is that teams stop storing ten or twenty pre-cut versions of every image, and a new crop for a new channel becomes a simple URL change.
Why image delivery performance matters: the 2024 numbers
Images dominate page weight and the most visible loading metric, so delivery is a performance decision first. According to the HTTP Archive Web Almanac 2024, 99.9% of pages request at least one image, and an image is the Largest Contentful Paint (LCP) element on 68% of mobile pages. The median mobile homepage loads 900 KB of images, against a median total page weight of 2,311 KB. Format adoption lags browser support: AVIF accounted for 1.0% and WebP for 12% of mobile image requests, while Can I use reports AVIF support across over 96% of global browser usage. The so what: automatic AVIF and WebP negotiation is one of the cheapest performance gains available, and it also supports image SEO.
Core dynamic media capabilities to require
A dynamic media layer needs six capabilities, and each maps to a measurable outcome. Use the table as a checklist in vendor demos.
| Capability | What it does | Why it matters |
|---|---|---|
| On-the-fly resizing and cropping | Generates any size from the master via URL parameters | Removes manual derivative exports |
| Smart or focal-point cropping | Keeps the subject in frame across aspect ratios | Prevents cut-off products on mobile |
| Format negotiation | Serves AVIF or WebP to supporting browsers, JPEG or PNG otherwise | Smaller files, faster LCP |
| Responsive breakpoints | Supplies srcset widths matched to layouts | Prevents oversized images on small screens |
| Video adaptive streaming | Delivers HLS or DASH renditions by bandwidth | Smooth playback (see managing video in DAM) |
| Cache purge API | Removes renditions on expiry or replacement | Enforces rights and brand updates |
Three delivery architectures for European teams
Every setup falls into one of three architectures, and the right choice depends on how many channels you serve and who owns the front end.
- DAM-native dynamic media. The DAM includes rendition and CDN services, as in Adobe Experience Manager Assets with Dynamic Media. One contract and built-in rights control, at the cost of vendor dependency.
- Standalone image CDN in front of the DAM. A media API such as Cloudinary or Scaleflex pulls masters from the DAM. This suits composable stacks and multiple DAM or PIM sources.
- General CDN with edge image processing. The existing web CDN resizes and converts images at the edge. This is the cheapest option for simple sites, with the weakest link to DAM metadata and rights.
European buyers should confirm where originals and cached renditions are stored and processed; EU data residency for DAM covers the contractual checks.
Cost drivers and governance for image delivery
Image delivery cost scales with traffic, so model it on your own page views before signing. The main drivers are bandwidth (GB delivered per month), rendition volume (unique variants generated) and storage of cached derivatives. Many vendors bundle these into credits or tiers; typical overage risk appears during seasonal peaks such as Black Friday (practitioner observation). Governance matters equally: tie cache purges to DAM expiry webhooks and limit URL parameters to approved presets, so nobody can generate an off-brand crop. Compare credit models in DAM pricing explained.
What to do next
- Pull field LCP data for your top 20 templates and record image weight per page.
- Decide which of the three delivery architectures fits your channel count and front-end ownership.
- Test format negotiation, focal-point cropping and purge time in a proof of concept.
- Model bandwidth and rendition volume at peak traffic and negotiate overage caps.
- Define approved rendition presets and connect expiry webhooks to the CDN purge API.
Frequently asked questions
What is the difference between a DAM and an image CDN?
A DAM stores, organises and governs master assets with their metadata and rights. An image CDN takes a master file, generates optimised renditions on request and caches them at edge locations for fast delivery. Many DAMs now include an image CDN, and others integrate with a standalone one.
Does an image CDN improve Core Web Vitals?
An image CDN usually improves Largest Contentful Paint, because the LCP element is an image on most mobile pages and smaller, modern-format files load faster. Gains depend on correct implementation, including responsive sizes and never lazy-loading the hero image. Measure before and after with field data from real users.
How do you remove an expired asset from an image CDN?
Configure the DAM to fire a webhook when an asset expires or is withdrawn, and have that event call the CDN purge API for every rendition of the asset. Without this, cached renditions can stay publicly available until their cache lifetime ends. Test the purge time during the proof of concept.