Digital Asset Management (DAM) is the practice - and the software - of storing, organising, enriching, controlling and distributing an organisation's digital media assets from a single trusted source. An "asset" is more than a file: it is the media essence (the image, video, audio, document or 3D model) plus the metadata that describes it, the rights that govern it, and the derivatives generated from it. DAM sits at the intersection of librarianship, records management and IT infrastructure.

DAM overlaps with, but is distinct from, an Electronic Document and Records Management System (EDRMS) and a Content Management System (CMS). A DAM optimises for rich media reuse and brand or collection control; an EDRMS optimises for evidential recordkeeping and disposition under ISO 15489; a web CMS optimises for page publishing. Mature institutions run all three and integrate them.

What counts as an asset

  • Essence plus metadata: the binary object and its descriptive, technical, administrative and rights metadata travel together.
  • Master and derivatives: a preservation master (e.g. TIFF, WAV, uncompressed video) plus access copies generated on demand.
  • Relationships: versions, renditions, collections and links to related records or authorities.

Why organisations adopt DAM

The business case is usually a mix of findability, reuse, rights control and cost avoidance - staff stop re-shooting or re-scanning material that already exists, and legal exposure from misused licences drops. In GLAM (Gallery, Library, Archive, Museum) settings, DAM also underpins public access, IIIF-based image delivery and integration with catalogue standards such as Dublin Core, EAD and Spectrum.

In practice. Before procuring a DAM, run a small asset audit: sample where media currently lives (shared drives, inboxes, phones, agency portals), estimate volume and growth, and record who needs to find and reuse what. That evidence shapes requirements far better than a generic vendor feature matrix.

Where DAM fits the standards landscape

A well-run DAM aligns with recognised frameworks rather than reinventing them: OAIS (ISO 14721) for the ingest-to-access reference model, PREMIS for preservation metadata, ISO 27001 for information security, and ISO 15489 where assets are also records. Treating DAM as part of this ecosystem - not a silo - is what separates a durable system from an expensive shared drive.

Key takeaways

  • An asset is media essence plus its metadata, rights and derivatives - managed as one unit.
  • DAM is distinct from EDRMS and CMS but should integrate with both.
  • Anchor DAM to OAIS, PREMIS, ISO 15489 and ISO 27001 rather than treating it as a standalone silo.

Check your understanding

Last modified: Saturday, 1 August 2026, 10:37 AM