Short answer
IPTC metadata is a set of standard fields for describing images, defined by the International Press Telecommunications Council. The IPTC Photo Metadata Standard stores its fields mostly as XMP and covers caption, creator, copyright notice and usage terms. A DAM should map those fields on ingest whenever photos arrive from agencies, photographers or stock libraries.
How IPTC metadata works in a DAM
IPTC metadata gives every image a shared set of descriptive and rights fields that any compliant tool can read. The IPTC Photo Metadata Standard groups them in two schemas:
- IPTC Core: caption, keywords, creator, credit line, copyright notice, rights usage terms and alt text.
- IPTC Extension: richer fields such as model release status, licensor, location shown, web statement of rights and digital source type.
Most current software writes these fields as XMP properties. Older files may also carry the legacy IPTC IIM header, so a DAM needs a rule for which source wins when both exist.
On ingest, the DAM maps IPTC fields to its own metadata schema. On export, a well-configured DAM writes the approved values back, so creator credit and copyright stay with the file.
Example of IPTC metadata
Worked example: a brand licenses 50 images from a photo agency. Each file arrives with creator, credit line, copyright notice and a web statement of rights in IPTC fields.
The DAM maps those values to its rights fields, links the agency licence, and sets an expiry date for the usage rights. When a web editor downloads an image, the credit line and copyright notice remain inside the file.
IPTC metadata in a DAM selection
IPTC metadata belongs at checkpoint 2, Define, where the buyer decides which IPTC fields map to which DAM fields. The metadata model builder helps list the fields and owners.
Test these four behaviours at checkpoint 5, Test:
- Ingest a buyer file with IPTC Core and Extension fields, and show every mapped value.
- Ingest a file with both a legacy IIM header and XMP, and show which value wins.
- Edit the alt text in the DAM and confirm it is written into the IPTC alt text field on download.
- Show how model release status from IPTC links to the DAM's release records.
DAMSelection assessment: map rights fields before descriptive fields, because missing copyright and licence data carries legal risk and missing keywords only hurts search. The rights management guide covers the full rights model.
Common mistakes with IPTC metadata
IPTC projects go wrong through four common mistakes.
- Treating IPTC and XMP as competing standards. IPTC defines the fields and XMP usually stores them.
- Mapping only caption and keywords and dropping creator, credit and usage terms.
- Overwriting the photographer's copyright notice with the brand's own notice on export.
- Ignoring newer Core fields such as alt text, which the alt text guide treats as an accessibility requirement.
Frequently asked
Is IPTC metadata the same as EXIF?
IPTC metadata and EXIF cover different information. IPTC describes content and rights, such as caption, creator and copyright. EXIF records technical capture data, such as camera model, exposure and date. A DAM reads both on ingest and maps them to separate field groups.
Which IPTC fields should a DAM map first?
DAMSelection rule of thumb: map creator, credit line, copyright notice, rights usage terms and alt text first. Add caption, keywords and location next, through the controlled vocabulary. Map Extension fields such as model release status when the library contains people.