What metadata actually means
The standard definition of metadata is "data about data." That phrase is accurate but unhelpful. To understand what metadata is, you first need to recognize that the word "data" has two distinct meanings in this context.
The first meaning refers to facts, figures, and statistics, the kind of information you collect before making a decision. The second meaning, prevalent since the rise of computers, refers to the files, symbols, characters, and quantities that a computer stores, transmits, and manipulates. Everything on your computer is data in this second sense.
Metadata, then, is descriptive information (data in the first sense) about a file (data in the second sense). When you take a photo at a birthday party and upload it to your computer, the photo itself is a data file. The information attached to that file, the upload date, file size, file name, and photographer, is metadata.
How metadata differs from keywords
Keywords and metadata are related but not interchangeable. Keywords are a specific type of metadata, not a synonym for it. Think of metadata as a cake and keywords as one of the ingredients. You would not serve guests a plate of sugar and eggs, but those ingredients are essential parts of the finished dessert.
Keywords are descriptive terms applied to files, either manually or automatically using artificial intelligence. They serve as the primary method for searching and retrieving specific files. When you type a search term into Google, you are using keywords. The same principle applies inside a digital asset management system. A photo tagged with the keyword "Work" can be found instantly by typing that term into the search bar.
In macOS, keywords are called "Tags." In Adobe Bridge, they appear in the Keywords panel. In many DAM platforms, they are stored in the IPTC Subject field. Regardless of the label, keywords function the same way: they make assets discoverable.
What metadata tagging and enrichment involve
Metadata tagging, sometimes called enrichment, is the process of adding metadata to a file. This can be done manually by a person or automatically using AI tools. For organizations managing thousands or millions of assets, enrichment is not a one-time activity but an ongoing discipline.
Effective enrichment requires clearly documented standards. These include a controlled vocabulary, a taxonomy, file naming conventions, and metadata mapping tables. Without these standards, different team members will tag the same asset in different ways, making search unreliable and workflows inconsistent.
For example, Adobe Bridge and PhotoMechanic are two desktop applications that allow manual metadata enrichment. Cloud platforms like Dropbox and Google Drive store some metadata but do not always support custom fields. Dedicated DAM platforms like Bynder, Acquia DAM, and MediaValet offer advanced metadata management, but they still require governance to ensure metadata is applied consistently.
Best practices for metadata management
Managing metadata well requires more than knowing what it is. It requires planning, documentation, and ongoing administration.
Map your metadata fields
Most DAM systems support the IPTC standard, developed by the International Press Telecommunications Council. IPTC defines a set of fields such as Headline, Caption, Copyright Notice, and Keywords. However, IPTC does not support custom fields. If your organization needs to track information that does not fit neatly into standard fields, you will need to map that information to existing fields and document the mapping in a reference table.
For example, you might store internal project codes in the Job Identifier field and campaign names in the Headline field. A metadata mapping table ensures everyone on your team knows where to find and how to enter this information.
Document your standards in two formats
Metadata standards should be documented in an editable format so they can be updated as your organization evolves. This might be a Google Doc or a wiki page. Once updates are finalized, export the standards into a permanent format, a PDF, a slide deck, or training materials, that can be distributed widely and referenced by anyone enriching or searching for assets.
Organizations change over time, and so do their metadata needs. Annual reviews of your standards keep them aligned with current goals, products, and strategies.
Embed metadata in the asset file
If metadata is only stored in the DAM platform and not embedded in the asset itself, you risk losing all that information if you migrate to a new system. Embedded metadata travels with the file, no matter where it is stored or shared.
To check whether your metadata is embedded, add a distinctive keyword to an asset inside your DAM, download the file, and inspect it using Adobe Bridge or PhotoMechanic. If the keyword appears, the metadata is embedded. If it does not, your metadata only exists in the DAM system and will not survive a migration. Stacks covers this topic in detail in their guide to metadata fundamentals.
Assign ownership for metadata administration
Metadata management is not a set-it-and-forget-it task. It requires ongoing administration, including updating standards, auditing the DAM for compliance, managing large-scale enrichment projects, and collaborating with marketing teams to align metadata with SEO strategy. Someone on your team should own this responsibility, whether that is a DAM manager, a metadata specialist, or a content operations lead.
Key takeaways
- Metadata is descriptive information about a file, such as upload date, file name, keywords, and authorship, that makes digital assets searchable and usable.
- Keywords are a specific type of metadata used primarily for search and retrieval, not a synonym for metadata itself.
- Effective metadata management requires documented standards, including controlled vocabularies, taxonomies, and metadata mapping tables.
- Embedding metadata in the asset file ensures it survives platform migrations and remains accessible outside the DAM system.
- Metadata standards should be reviewed and updated regularly to reflect organizational changes and evolving content strategies.