Reference Glossary
XMP
Adobe's Extensible Metadata Platform, an XML/RDF-based framework introduced in 2001 and standardized as ISO 16684-1, used to embed structured, custom metadata packets directly inside files like JPEG, TIFF, and PDF.
Why it matters in a DAM
XMP is what lets a DAM store metadata beyond a fixed field list — Lightroom ratings, custom project codes, or a proprietary rights-tracking schema can all live in a file's XMP packet, not just the standard IPTC or Exif fields. It's also the mechanism behind RAW sidecar files: since many RAW formats can't be safely edited in place, Camera Raw and Lightroom write develop settings and keywords to a .xmp file using the same XMP data model used for embedded metadata.
A worked example
Common mistake
Teams assume XMP field names are universal, but a custom XMP namespace defined by one DAM or agency won't be recognized by another system expecting Adobe's own namespace prefixes — after a migration, the data is technically still in the file, but the receiving system displays it as missing because it doesn't know the namespace to look in.
Adobe introduced XMP in April 2001 as a way to give metadata a consistent, extensible container across its own applications and, eventually, third-party software. Unlike Exif or the original IPTC-IIM format, which define a fixed set of binary tag numbers, XMP stores metadata as RDF/XML — a text-based, self-describing format that any application can extend with its own namespace without breaking compatibility with tools that don’t recognize those custom fields. That extensibility is the reason it became the carrier format for the modern IPTC Core/Extension schema rather than a competing standard.
XMP was submitted for international standardization and published as ISO 16684-1, with the current version dated 2019, defining both the abstract data model and its XML serialization. It’s supported across a wide range of formats — JPEG, TIFF, PNG, PDF, and Adobe’s native PSD and AI formats among them — either embedded in the file or, for formats that resist safe embedding, written to an external sidecar file with identical structure.
For DAM implementers, XMP is usually the layer used to carry anything the platform needs that isn’t already covered by IPTC or Exif — custom taxonomy codes, internal approval status, or licensing IDs — because it’s the one metadata format explicitly designed to be extended without a standards body’s sign-off.
Frequently asked
What is XMP and why was it created?
XMP is Adobe's Extensible Metadata Platform, an XML/RDF-based framework introduced in 2001 and standardized as ISO 16684-1. It lets structured, custom metadata packets be embedded directly inside files like JPEG, TIFF, and PDF, beyond what fixed field lists like IPTC or Exif allow.
How does XMP relate to sidecar files?
XMP is the data model behind RAW sidecar files — since many RAW formats can't be safely edited in place, tools like Camera Raw and Lightroom write develop settings and keywords to a .xmp sidecar file, using the same XMP structure that's also used for metadata embedded inside other file types.
What can XMP store that standard fields like IPTC can't?
Custom, structured metadata packets — Lightroom ratings, custom project codes, or a proprietary rights-tracking schema can all live in a file's XMP packet, going beyond the fixed field list of standard IPTC or Exif metadata.
What goes wrong when XMP data moves between different systems?
A custom XMP namespace defined by one DAM or agency won't be recognized by another system expecting Adobe's own namespace prefixes. After a migration, the data is technically still in the file, but the receiving system displays it as missing because it doesn't know which namespace to look in.
Is XMP field data always portable across DAM platforms?
Not reliably for custom fields — standard XMP namespaces tend to transfer cleanly, but organization-specific namespaces require both systems to agree on the same namespace definitions, or the values effectively become invisible after migration even though they're still physically present in the file.
Which file formats commonly carry XMP metadata?
JPEG, TIFF, and PDF are named formats that support embedded XMP packets, alongside many RAW formats that use XMP indirectly through a linked .xmp sidecar file rather than embedding it directly.
Sources
- Adobe introduced XMP in April 2001 checked 2026-08-07 — Metadata Standards Index, Extensible Metadata Platform (XMP)
- XMP is standardized as ISO 16684-1, with the current edition dated 2019 checked 2026-08-07 — ISO, ISO 16684-1:2019