DAM fundamentals
Managing video in DAM: transcoding, streaming and the MAM overlap
Quick answer
Managing video in a DAM means storing high-resolution masters once, transcoding them automatically into web, social and proxy renditions, streaming them with adaptive bitrate (HLS or MPEG-DASH), and managing captions, rights and versions. Marketing teams fit a DAM; broadcast-scale production with proxy editing and heavy weekly ingest usually needs a media asset management (MAM) system.
Key takeaways
- Store one high-quality master and generate every rendition from it; a rendition matrix of 6 to 10 outputs covers most marketing channels.
- Adaptive bitrate streaming via HLS (RFC 8216) or MPEG-DASH (ISO/IEC 23009-1) is the default for web delivery; progressive MP4 download suits short clips only.
- Under the European Accessibility Act, in-scope services must meet EN 301 549, which references WCAG 2.1 AA captions and audio description.
- A MAM becomes the better fit when editors need proxy workflows inside editing software or ingest exceeds several terabytes per week (editorial estimate).
Video changes DAM requirements in four ways: file size, renditions, delivery and accessibility. A DAM handles marketing video well when it stores one master, transcodes automatically, streams with adaptive bitrate and manages captions as assets. When the workload shifts to production, with editors working on proxies and terabytes arriving each week, a media asset management (MAM) system takes over.
What video adds to DAM requirements
Video multiplies storage, processing and bandwidth compared with images. A 10-minute 4K master in a mezzanine format such as ProRes easily exceeds 50 GB, and a single campaign can generate 30 to 60 cut-downs and formats. As a typical range, hot cloud object storage costs around EUR 20 to 25 per TB per month at list price, while archive tiers cost a fraction of that (editorial estimate).
Bandwidth matters as much as storage. A 2-minute video streamed at 5 Mbps transfers about 75 MB per view, so 100,000 views move roughly 7.5 TB. The so what: check how your DAM vendor prices storage and egress before committing, as covered in DAM pricing explained.
Transcoding and renditions: build a rendition matrix
A rendition matrix defines every output the DAM generates from one master. Fixing it up front prevents designers from exporting the same video by hand for each channel.
| Rendition | Typical specification | Use |
|---|---|---|
| Master | ProRes or high-bitrate H.264 or H.265, original resolution | Archive and re-editing |
| Web MP4 | H.264, 1080p, 4 to 8 Mbps | Universal playback, downloads |
| Streaming ladder | 4 to 6 bitrates from 360p to 1080p or 4K, H.264, H.265 or AV1 | Adaptive streaming on websites |
| Social vertical | 9:16, 1080 x 1920, H.264 | Reels, Shorts, TikTok |
| Social square and portrait | 1:1 and 4:5 | Feed posts |
| Proxy | Low-bitrate H.264, burnt-in timecode | Review and approval |
AV1, the royalty-free codec from the Alliance for Open Media, reduces bitrate compared with H.264 at similar quality, with 30 to 50 percent commonly cited as a typical range. Keep H.264 in the matrix for compatibility, because older devices still lack AV1 hardware decoding. Smart cropping for vertical formats is now common in DAM and video platforms, but review crops of people and products manually.
Streaming and delivery: HLS, MPEG-DASH and video CDNs
Adaptive bitrate streaming is the default for any video longer than about 30 seconds on a public website. HLS, published as RFC 8216 in 2017, and MPEG-DASH, standardised as ISO/IEC 23009-1, both split video into short segments at several bitrates so the player adjusts to the viewer's connection. Progressive MP4 suits short loops and downloads.
Delivery options range from DAM-native players to integrated media platforms such as Cloudinary and Scaleflex. European buyers should check where video is cached and whether the player sets cookies that require consent under ePrivacy rules. The dynamic media and image CDN guide covers delivery architecture in more depth.
Captions, transcripts and the European Accessibility Act
Accessibility law makes captions a requirement for many European brands. The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025 to in-scope consumer services, including e-commerce, and the harmonised standard EN 301 549 references WCAG 2.1 Level AA. That level includes captions for prerecorded video (success criterion 1.2.2) and audio description (1.2.5).
Treat caption files (WebVTT or SRT) and transcripts as linked assets with their own language metadata. AI speech-to-text produces a usable first draft in most European languages, but brand names and product terms need human review. See the European Accessibility Act guide for scope and exemptions.
DAM vs MAM: where the overlap ends
DAM and MAM overlap on storage, metadata and search, and diverge on production. A MAM adds camera-card ingest, proxy editing inside tools such as Adobe Premiere Pro or Avid Media Composer, frame-accurate timecode, archive tiering and playout integration. Cloud MAM products such as iconik and video-focused archives such as Imagen sit in this space.
As a practitioner rule of thumb, consider a MAM or a MAM plus DAM architecture when editors need proxy workflows, when ingest exceeds several terabytes per week, or when video is the product itself, as in media and sport. For other cases, a DAM with strong video support is simpler and cheaper.
What to do next
- Measure annual video volume, average master size and expected streaming views.
- Define your rendition matrix and test it with a real master in each vendor demo.
- Confirm storage, egress and transcoding pricing in writing.
- Add caption, transcript and audio description handling to your requirements.
- Decide whether editors need proxy workflows, which points to a MAM.
Frequently asked questions
What is the difference between DAM and MAM?
A DAM manages finished marketing and brand assets of all types for wide reuse and distribution. A media asset management (MAM) system manages video production: camera ingest, proxies for editing, timecode, archive tiers and playout. Many organisations connect the two, with finished video moving from MAM to DAM for distribution.
Can a DAM stream video?
Many DAM platforms generate streaming renditions and embed codes, either natively or through an integrated video CDN. Check whether the vendor supports adaptive bitrate (HLS or MPEG-DASH), caption tracks, player analytics and EU-hosted delivery before relying on it for public websites.
Which video formats should a DAM store?
Store the highest-quality master you receive, typically a ProRes or high-bitrate H.264 or H.265 file, plus caption files such as WebVTT or SRT. Generate delivery formats such as H.264 MP4 and streaming renditions automatically from that master, so no manually exported copies need storing.