Skip to content

Glossary Digital asset management (DAM)

What Is Digital Asset Management (DAM)?

Definition

Digital asset management (DAM) is the software and the practice an organization uses to keep its images, videos, audio, graphics and documents in one place, describe them with metadata, control who may use them and deliver each file in the right format to the store, website, marketplace or printer. It is not to be confused with digital assets in finance, such as cryptocurrencies.

A library of nine tiles (images, videos and documents) with one image in orange; orange lines lead from it to three frames in different formats, landscape, square and portrait, each holding a crop of the same orange image, on a dark blue ground.
On this page 15
  1. Origin of the term
  2. History and development
  3. How it works
  4. Types and variants
  5. Examples
  6. How to measure it
  7. Advantages and disadvantages
  8. How it differs from related concepts
  9. Tools
  10. Criticism and limits
  11. Legal framework
  12. How to apply it, step by step
  13. Best practices
  14. Common mistakes
  15. How this entry was made
In brief

A DAM system stores, describes and delivers images, videos and documents. IPTC metadata, images for the web, DAM vs PIM and CMS, and the main tools.

A library of nine tiles (images, videos and documents) with one image in orange; orange lines lead from it to three frames in different formats, landscape, square and portrait, each holding a crop of the same orange image, on a dark blue ground.

Origin of the term

A digital asset is any file a business uses and wants to reuse under control: a product photo, the logo, a campaign video, a presentation template, a product data sheet in PDF. The software is called a DAM system or DAM platform.

According to the German-language Wikipedia, the first systems were called image databases, because at first they only handled photos. In the English-language Google Books corpus, the frequency of the phrase "digital asset management" grew more than a hundredfold between 1995 and 2000, according to our own Ngram Viewer query.

Two variants have their own names: media asset management (MAM), when the focus is video and audio, and brand asset management (BAM) or brand portal, when the system serves logos and brand material to dealers and agencies.

History and development

  • Early 1990s. The IPTC (International Press Telecommunications Council) creates the IPTC-IIM schema, so that details such as creator, caption and rights travel inside the image file. Before that, every system had its own format.
  • 1992 to 1994. The first single-user programs appear, according to the German-language Wikipedia: Hasselblad's Pixolo, Canto Cumulus and, a little later, FotoStation from the Norwegian company FotoWare. They later become client-server systems.
  • 2000s. Systems move into the browser, with the data held on a central server.
  • 2012. XMP, the format developed by Adobe in which IPTC metadata is stored today, becomes the standard ISO 16684-1. The current second edition dates from 2019.
  • 2017 to 2021. The IPTC Photo Metadata Standard adds star ratings and a link to the usage rights (2017), image regions (2019) and an alt text field for accessibility (2021).
  • 2021. In December, version 1.0 of the C2PA specification is published. It is the technical basis of Content Credentials, which record where a file comes from and how it was edited.
  • 2022. In June, the IPTC creates the value trainedAlgorithmicMedia, now labelled "Created using Generative AI". In November, the "Product Shown in the Image" field, which already took a GTIN, gets a generic identifier.
  • 2023. In October, the IPTC adds the "Data Mining" field, which states whether data mining of the image is prohibited or permitted.
  • 2024. The EU adopts the Artificial Intelligence Act, Regulation (EU) 2024/1689. Its Article 50 requires synthetic content to be marked in a machine-readable way.
  • 2025. In November, IPTC 2025.1 adds four fields for AI-generated images: the prompt, its writer, the AI system used and its version.
  • 2026. Article 50 applies from 2 August. Providers whose systems were on the market before that date have until 2 December to add the marking. In October, C2PA 2.5 is published.

How it works

A DAM system takes in files, adds information to them, controls how they are used and delivers them in different versions. The path of one product photo shows how.

How many versions of your most used product photo are scattered around right now?

Intake. Files arrive by upload, bulk import or through an API from other systems: the photo studio, the design agency, the PIM or the CMS. The DAM keeps the full-resolution original and can flag duplicates.

Description. An image carries two layers of metadata. The first travels inside the file: the camera's technical EXIF data and IPTC fields such as creator, copyright holder, caption or alt text, stored in the XMP format. The second exists only in the DAM: campaign, SKU, approved channels, licence expiry date. A controlled vocabulary, a fixed list of terms, keeps everyone tagging the same way. Tags that an AI suggests from the image content save time, but someone has to check them.

Which of these does your product photography carry today, and where?

Versions and approval. Every change creates a new version and keeps the old one. A workflow sets who reviews and who approves before the file becomes available.

Rights. The DAM knows where each photo comes from, under which licence and until when. When a licence expires, it can pull the file from the channels or alert the owner.

Output. From one original, the DAM produces the versions each channel needs: a square crop for social media, a 1,200-pixel JPEG for the marketplace, WebP or AVIF in several sizes for the store. Delivery can run through a CDN, and every page uses the same URL for each image.

Archive. Files that are no longer in use move to an archive with their metadata instead of being deleted.

Images on the web. Google's image SEO guidelines, last updated in March 2026, list points a DAM can turn into fixed rules: If alt text is a required field in the DAM for each language, the store, the blog and the featured image of each article receive it ready-made.

  • Formats that Google Search supports: BMP, GIF, JPEG, PNG, WebP, SVG and AVIF, with a file extension that matches the file type.
  • Short, descriptive filenames instead of image1.jpg, translated when the image is localized.
  • Alt text that describes the image. Google uses it together with computer vision and the page content to understand what the image shows.
  • Several resolutions of the same file, served with the srcset attribute or the picture element, so a phone does not download the large version.

Types and variants

TypeFor whomExample according to the vendor
Cloud DAM (SaaS)Marketing teams that do not want to run serversBynder, Brandfolder
Open-source or self-hosted DAMOrganizations with their own IT teamResourceSpace, Pimcore
DAM inside a content suiteCompanies already using the same vendor's CMS or platformAdobe Experience Manager Assets, OpenText
DAM with media delivery and optimizationStores and websites with large numbers of images and videosCloudinary
Brand portal (BAM)Manufacturers and franchisors supplying dealers and agenciesBrandfolder, Frontify

Source: own compilation from vendor pages (accessed 08.11.2026). Media asset management for video and audio is covered under the differences.

Examples

Worked example, with no data from any company: an online kitchenware store with 3,000 products, six photos per product, three languages (English, Spanish and German) and four channels (store, marketplace, Google Shopping and social media).

The DAM holds 18,000 originals (3,000 times 6). If each original is delivered in four versions, that makes 72,000 derived files nobody uploads by hand. With one alt text per language, the store needs 54,000 texts (18,000 times 3). That is why the field is required at upload and not filled in later in the store.

One of those photos, a 28 cm frying pan on a white background, looks like this in the DAM:

  • Filename: nonstick-frying-pan-28-cm-front.jpg, with translated names for the Spanish and German versions.
  • IPTC fields inside the file: creator (the photo studio), copyright holder (the store), alt text in three languages.
  • DAM fields: product SKU and GTIN, the studio's licence with no end date, approved channels (all four), autumn campaign.
  • Versions: 2,000 pixels for the zoom view, 1,200 for the marketplace, 600 as WebP for the category page and a square crop for social media.

In the PIM, the pan's record stores the link to the DAM file by SKU. If the studio delivers a better photo, it is replaced once in the DAM, and the store, the marketplace and the feed show it after the next update.

How to measure it

MetricFormulaWhat it tells you
Metadata completenessAssets with all required fields / published assets × 100Whether files can be found and carry rights and alt text
Alt text coveragePublished images with alt text in the language / published images in that language × 100Accessibility and image SEO per language
Reuse rateAssets used in at least two channels / published assets × 100Whether the DAM prevents producing the same thing twice
Expired rights in usePublished assets with an expired licence / published assets × 100Legal risk; the target is 0
Time to approvalMedian days between upload and approvalBottlenecks in the workflow

Source: own formulas; no published benchmarks with a stated method exist.

Advantages and disadvantages

Use caseAdvantageDisadvantage
Agency or marketing team with campaignsOne approved version of each asset, with its historyTags and workflows must be agreed before the first upload
Online store with product photosEvery photo is tied to its product and delivered at each channel's sizeNeeds a connection to the PIM or store; without it, the DAM is one more folder
Manufacturer with a dealer networkDealers download current material themselvesIf nobody removes old material, it keeps circulating
Publisher or production company with videoSearch across large archives and rights per itemVideo needs storage and transcoding, which drive up the cost

Source: own compilation.

How it differs from related concepts

ConceptWhat it managesDifference from DAM
PIMProduct data: attributes, descriptions, reference pricesThe PIM holds the data and links to the files; the DAM holds the files
MAMVideo, audio and stills in media productionA DAM specialized in media, with editing and broadcast functions
Brand portal (BAM)Logos, templates, brand guidelinesThe part of a DAM opened to outside partners
CMSWeb pages and their textThe CMS builds the pages; the DAM supplies the images
Cloud storage (Google Drive, SharePoint, OneDrive)Folders and filesStores files without business context: no rights, no approval, no versions per channel
Image databasePhotos with metadataThe earlier name for DAM, when it only handled photos

Source: own compilation; DAM per the Gartner glossary; cloud storage and MAM per the English-language Wikipedia.

Tools

In the Keyword Planner figures gathered for this entry (Google, November 2026), Bynder has about 6,600 brand searches a month in the United States and Brandfolder about 4,400, the highest among the DAM vendors checked. The table is alphabetical and is not a ranking.

ToolWhat the vendor says it offersNote
Adobe Experience Manager AssetsAI-powered DAM to manage, optimize and deliver contentPart of Adobe Experience Manager
AprimoDAM to centralize content and collaborate
BrandfolderBrand asset management
BynderSystem of record for digital assets, powered by AI
CantoDAM for images, videos and brand filesIts Cumulus is among the first programs of 1992 to 1994, per the German-language Wikipedia
CelumSingle source of truth for digital media assets
CloudinaryOrganize, optimize and deliver media, with generative AI features
FotoWareDAM with automation and governanceNorwegian company
FrontifyDAM with AI search, approvals and format adaptation for brands
OpenText Digital Asset ManagementStore and manage rich media across enterprise processes
PimcoreDAM within a platform with PIM, MDM and CMSHas a Community Edition
pixx.ioDAM developed in Germany
ResourceSpaceOpen-source DAM

Source: vendor pages, accessed 08.11.2026; alphabetical order.

Criticism and limits

A DAM organizes what it receives. Files that arrive with no creator, no licence or a name like IMG_4711.jpg get stored anyway, and filling in that information is still work for people, which can cost more than the licence.

The second limit is the boundary with other systems. If product photos can be uploaded to the DAM and also straight to the store or the PIM, two versions of the same image appear and nobody knows which one is right. Before rollout, decide which system leads for each kind of file.

Automatic tags make their own mistakes. An AI recognizes a frying pan but does not know whether it is the 24 cm or the 28 cm model, or whether the photo may be used in Germany. Metadata with legal or commercial consequences remains human work.

How to apply it, step by step

  • Count what you have: number of files, formats, where they sit and how many duplicates there are.
  • Define the metadata schema: which fields are required (creator, licence, expiry, alt text per language, SKU) and which controlled vocabularies apply.
  • Record the rights of each file before migrating it. Anything without a clear licence stays out of the channels.
  • Set a rule for filenames and folders, with descriptive words in the publishing language.
  • Start with one campaign or one product category as a pilot and measure completeness before and after.
  • Connect the DAM to the PIM, the CMS and the store so they pull images from it and not from local copies.
  • Check the metrics from the section above every month.

Best practices

  • Upload each photo once at full resolution and let the DAM create the versions.
  • Link product images by SKU or GTIN, not by filename.
  • Write alt text in every language you publish in, not only in English.
  • Store creator and rights inside the file as well (IPTC), so they travel with the image.
  • Keep provenance data and Content Credentials when exporting.

Common mistakes

  • Accepting AI-suggested tags without review.
  • Recording rights only in the filename or in a separate spreadsheet.
  • Uploading the same image in five sizes instead of generating versions from one original.
  • Leaving alt text until the end and typing it into the store, outside the DAM.
  • Migrating the whole old archive unfiltered and filling the system with duplicates.

How this entry was made

This entry was written in November 2026 with the help of AI. It started from an analysis of the top ten search results in the United States, Spain and Germany and of the answers from four AI assistants, to cover what they leave out: the IPTC and XMP metadata standards, images for the web, content provenance with C2PA and the link to the PIM. Every fact was checked against the original source.

Manuel Riveiro Rodriguez CEO & Digital Strategist

A technical audit covers this and everything else in one pass.

Request an audit

Frequently asked

What is DAM software?

DAM software is the application where a business stores its photos, videos and documents, tags them with metadata, manages approvals and usage rights, and sends each file to its channels in the required format. It can run in the cloud as a subscription or be installed on the company's own servers.

What is an example of a DAM system?

Adobe Experience Manager Assets, Bynder, Brandfolder, Canto and Cloudinary are DAM systems, and ResourceSpace is an open-source one. One use is an online store that keeps every product photo in the DAM and delivers it to the store, marketplaces and social media in the right size.

What is the difference between DAM and PIM?

A PIM holds product data such as attributes, descriptions and GTINs. A DAM holds the files, such as photos, videos and manuals. They work together: the PIM record links to the DAM photos by the product's SKU.

Is there open-source DAM software?

Yes. ResourceSpace is open-source DAM software, and Pimcore offers a Community Edition with a DAM module. Both need a technical team to install, run and adapt them.

What does a digital asset manager do?

A digital asset manager runs the DAM within a company. The role sets the metadata schema and naming rules, checks rights and expiry dates, trains users and tracks metrics such as metadata completeness.

Sources

  1. Gartner, Digital Asset Management (DAM), Gartner glossary. Definition.
  2. Digital-Asset-Management, Wikipedia (German). Image databases and first programs 1992 to 1994.
  3. Digital asset management, Wikipedia. MAM and types of systems.
  4. Google Books Ngram Viewer, "digital asset management", English corpus 2019. Own query.
  5. IPTC, IPTC Photo Metadata Standard. Origin of IPTC-IIM and changes in versions 2017.1 to 2025.1.
  6. IPTC, IPTC Photo Metadata Standard 2025.1, specification. Data Mining field, added in version 2023.1.
  7. IPTC, Digital Source Type NewsCodes. Value trainedAlgorithmicMedia, created 14.06.2022.
  8. ISO 16684-1:2019, Extensible metadata platform (XMP), Part 1. Replaces the 2012 edition.
  9. C2PA, Content Credentials: C2PA Technical Specification 2.5. Version history from 1.0 in December 2021.
  10. Google Search Central, Image SEO Best Practices, updated 02.03.2026. Formats, filenames, alt text, srcset.
  11. Adobe, Adobe Experience Manager Assets.
  12. Aprimo, Aprimo DAM.
  13. Brandfolder.
  14. Bynder, Digital Asset Management.
  15. Canto, Digital Asset Management (DAM): What It Is and How It Works.
  16. Celum, High-End Digital Asset Management.
  17. Cloudinary, Intelligent Digital Asset Management.
  18. Fotoware.
  19. Frontify, Digital Asset Management Software for Brands.
  20. OpenText, Digital Asset Management Software for the Enterprise.
  21. Pimcore, Digital Asset Management (DAM).
  22. pixx.io, German Digital Asset Management System.
  23. ResourceSpace, Open Source Digital Asset Management (DAM) Software.
  24. Directive (EU) 2019/790 on copyright in the Digital Single Market, Article 4, EUR-Lex.
  25. Regulation (EU) 2024/1689 (AI Act), consolidated version of 27.07.2026, Articles 50 and 111, EUR-Lex.