Extensible Metadata Platform

The defined XMP data model can be used to store any set of metadata properties. These can be simple name/value pairs, structured values or lists of values. The data can be nested as well. The XMP standard also defines particular namespaces for defined sets of core properties (e.g. a namespace for the Dublin Core Metadata Element Set). Custom namespaces can be used to extend the data model.

An instance of the XMP data model is called an XMP packet. Adding properties to a packet does not affect existing properties. Software to add or modify properties in an XMP packet should leave properties that are unknown to it untouched.

For example, it is useful for recording the history of a resource as it passes through multiple processing steps, from being photographed, scanned, or authored as text, through photo editing steps (such as cropping or color adjustment), to assemble into a final document. XMP allows each software program or device along the workflow to add its own information to a digital resource, which carries its metadata along. The prerequisite is that all involved editors either actively support XMP, or at least do not delete it from the resource. ^[2]

The abstract XMP data model needs a concrete representation when it is stored or embedded into a file. As serialization format, a subset of the W3C RDF/XML syntax is most commonly used. It is a syntax to express a Resource Description Framework graph in XML. There are various equivalent ways to serialize the same XMP packet in RDF/XML.

The most common metadata tags recorded in XMP data are those from the Dublin Core Metadata Initiative, which include things like title, description, creator, and so on. The standard is designed to be extensible, allowing users to add their own custom types of metadata into the XMP data. XMP generally does not allow binary data types to be embedded. This means that any binary data one wants to carry in XMP, such as thumbnail images, must be encoded in some XML-friendly format, such as Base64.

XMP metadata can describe a document as a whole (the "main" metadata), but can also describe parts of a document, such as pages or included images. This architecture makes it possible to retain authorship and rights information about, for example, images included in a published document. Similarly, it permits documents created from several smaller documents to retain the original metadata associated with the parts.^[2]

This is an example XML document for serialized XMP metadata in a JPEG photo:

<?xpacket begin="?" id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.4-c002 1.000000, 0000/00/00-00:00:00        ">
   <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
      <rdf:Description rdf:about=""
            xmlns:xmp="http://ns.adobe.com/xap/1.0/">
         <xmp:CreatorTool>Picasa</xmp:CreatorTool>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:mwg-rs="http://www.metadataworkinggroup.com/schemas/regions/"
            xmlns:stDim="http://ns.adobe.com/xap/1.0/sType/Dimensions#"
            xmlns:stArea="http://ns.adobe.com/xmp/sType/Area#">
         <mwg-rs:Regions rdf:parseType="Resource">
            <mwg-rs:AppliedToDimensions rdf:parseType="Resource">
               <stDim:w>912</stDim:w>
               <stDim:h>687</stDim:h>
               <stDim:unit>pixel</stDim:unit>
            </mwg-rs:AppliedToDimensions>
            <mwg-rs:RegionList>
               <rdf:Bag>
                  <rdf:li rdf:parseType="Resource">
                     <mwg-rs:Type></mwg-rs:Type>
                     <mwg-rs:Area rdf:parseType="Resource">
                        <stArea:x>0.680921052631579</stArea:x>
                        <stArea:y>0.3537117903930131</stArea:y>
                        <stArea:h>0.4264919941775837</stArea:h>
                        <stArea:w>0.32127192982456143</stArea:w>
                        <stArea:unit>normalized</stArea:unit>
                     </mwg-rs:Area>
                  </rdf:li>
               </rdf:Bag>
            </mwg-rs:RegionList>
         </mwg-rs:Regions>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:exif="http://ns.adobe.com/exif/1.0/">
         <exif:PixelXDimension>912</exif:PixelXDimension>
         <exif:PixelYDimension>687</exif:PixelYDimension>
         <exif:ExifVersion>0220</exif:ExifVersion>
      </rdf:Description>
   </rdf:RDF>
</x:xmpmeta>

<!-- whitespace padding -->
				
<?xpacket end="w"?>

This metadata describes various properties of the image like the creator tool, image dimension or a face region^[3] within the image.

Embedding metadata in files allows easy sharing and transfer of files across products, vendors, platforms, without metadata getting lost. Embedding avoids a multitude of problems coming from proprietary vendor-specific metadata databases.

XMP can be used in several file formats such as PDF, JPEG, JPEG 2000, JPEG XR, JPEG XL, GIF, PNG, WebP, HTML, TIFF, Adobe Illustrator, PSD, MP3, MP4, Audio Video Interleave, WAV, RF64, Audio Interchange File Format, PostScript, Encapsulated PostScript, and proposed for DjVu. In a typical edited JPEG file, XMP information is typically included alongside Exif and IPTC Information Interchange Model data.

For more details, the XMP Specification, Part 3 Storage in Files listed below has details on embedding in specific file formats.

• TIFF – Tag 700
• JPEG – Application segment 1 (0xFFE1) with segment header "http://ns.adobe.com/xap/1.0/\x00"
• JPEG 2000 – "uuid" atom with UID of 0xBE7ACFCB97A942E89C71999491E3AFAC
• JPEG XL – "xml " box type
• PNG – inside an "iTXt" text block with the keyword "XML:com.adobe.xmp"
• GIF – as an Application Extension with identifier "XMP Data" and authentication code "XMP"
• MP3 – inside the ID3 block as a "PRIV" frame with an owner identifier of "XMP".
• MP4 – top-level "UUID" box with the UUID 0xBE7ACFCB97A942E89C71999491E3AFAC (Same as JPEG 2000)
• MOV (QuickTime) – "XMP_" atom within a "udta" atom, within a top level "moov" atom.
• PDF – embedded in a metadata stream contained in a PDF object
• WebP – inside the file's XMP chunk
• For file formats that have no support for embedded XMP data, this data can be stored in external .xmp sidecar files.

The XMP Toolkit implements metadata handling in two libraries:

• XMPCore for creation and manipulation of metadata that follows the XMP Data Model.
• XMPFiles for embedding serialized metadata in files, and for retrieving embedded metadata.

Adobe provides the XMP Toolkit free of charge under a BSD license.^[4][2] The Toolkit includes specification and usage documents (PDFs), API documentation (doxygen/javadoc), C++ source code (XMPCore and XMPFiles) and Java source code (currently only XMPCore). XMPFiles is currently available as a C++/Java implementation in Windows, Mac OS, Unix/Linux.^{[citation needed]}

• Alfresco - open source CMS, DAM component can read/write XMP (Microsoft Windows, Linux)
• Calibre by Kovid Goyal, an ebook management system that can read and write XMP metadata from some file formats
• CC PDF Converter - A free open source (GPL) program to convert documents to PDF with embedded Creative-Commons license (Microsoft Windows).
• darktable - RAW developer, can read/write XMP in supported file formats (Linux, Mac OS X, Microsoft Windows, BSD)
• digiKam - open source (GPL) image tagger and organiser (Linux, Mac OS X, Microsoft Windows)
• ExifTool by Phil Harvey, open source Perl module or command line. Can read/write XMP, supports custom XMP schema (platform independent)
• F-Spot - Linux/GNOME photo manager and editor
• Geeqie - Lightweight Gtk+ based image manager (formerly GQView)
• GIMP - GNU Image Manipulation Program
• Gwenview - Linux/KDE photo manager and editor
• iText - Open Source Java library that can read and write XMP embedded in PDF files.
• Magic Lantern (firmware) - A firmware add-on for various Canon Digital single-lens reflex (DSLR) cameras, allowing writing of XMP sidecar files including exposure compensation information for post-deflicker.
• RawTherapee - Can read "rating" tags from embedded XMP, which are then shown in the File Browser/Filmstrip using RawTherapee's star rating system.
• Shotwell - Linux/GNOME photo manager, can read/write Exif, IPTC and XMP metadata
• TYPO3 - open source Enterprise CMS. DAM component reads XMP (PHP based)

• ACDSee Pro can read and write XMP information for DNG, GIF, JPEG, PNG and TIFF files (Microsoft Windows, Mac OS X).
• Acrobat - can read and write XMP in PDF files (Microsoft Windows, Mac OS X, partially Linux).
• Aperture - Image management application and RAW developer. Reads/writes XMP sidecar files to (batch) import/export image metadata (Mac OS X).
• Bibble5 can read/write XMP information for RAW, JPG and TIFF files (Microsoft Windows, Mac OS X, Linux).
• Bridge - can read/write and batch edit XMP metadata (Microsoft Windows, Mac OS X)
• Capture One - Photo editing and management software. Reads and writes XMP for all supported image formats (Microsoft Windows, Mac OS X).
• Corel AfterShot Pro - RAW processor (Bibble successor), reads/writes XMP, uses XMP sidecar files for non-destructive image processing (Microsoft Windows, Mac OS X, Linux).
• Cumulus - DAM software, can read/write XMP for all supported image formats, InDesign and PDF files (Microsoft Windows, Mac OS X, Linux)
• DBGallery - Can read/write XMP for JPEG, PSD, RAW, TIFF, DNG, PNG, GIF, JP2, PJX, MPG, MP4, MPEG, MOV (Microsoft Windows). Multi-user, central database system.
• FastPictureViewer - Image viewer (Windows) with XMP embedding and/or sidecar files creation (xmp:Rating, xmp:Label, photoshop:Urgency) (Microsoft Windows)
• FrameMaker - publishing tool. Stores document metadata in XMP since version 7.0 (Microsoft Windows)
• Illustrator - illustration software, writes document metadata in XMP (Microsoft Windows, Mac OS X)
• Indesign - page layout software, can pass through XMP in placed objects, writes extensive XMP about document contents in layout documents and exported PDF (Microsoft Windows, Mac OS X)
• iOS Photos app - Saves edits made to photos on an iPhone/iPad losslessly as XMP embedded in the original JPEG.^[5]
• Lightroom - Image management application and RAW developer. Uses XMP for non-destructive image manipulation and import/export of metadata (Microsoft Windows, Mac OS X)
• Microsoft Windows Vista - Photo Gallery saves tags to XMP (Microsoft Windows)
• Photo Mechanic - Reads and writes XMP directly into image files or into XMP sidecar files.
• Photoshop - can read/write XMP in supported images. Allows embedding of non standard XMP data through 'custom XMP panels' (Microsoft Windows, Mac OS X)
• PicaJet - Can read XMP for JPG, TIFF and DNG formats (Microsoft Windows).
• Picasa - Image organizer/viewer, uses XMP for face tagging (Microsoft Windows, Mac OS X, Linux)
• PixelPeeper - can read Exif and XMP metadata from JPG files. Also, it can turn XMP metadata into Lightroom-compatible presets.
• Portfolio - DAM software, can read/write XMP in supported file formats (Microsoft Windows, Mac OS X)
• Stibo STEP - DAM component reads/writes XMP for all supported formats
• Windows Imaging Component - Microsoft library for working with and processing digital images and image metadata (Microsoft Windows)
• Windows Live Photo Gallery - a photo management and sharing application released as a part of Microsoft's Windows Live initiative. It is an upgraded version of Windows Photo Gallery, which is a part of Windows Vista.
• XnView - can read/write Exif, IPTC and XMP information.
• Zoner Photo Studio - can read/write Exif, IPTC and XMP information for DNG, JPEG, TIFF, HDP and various RAW files (Microsoft Windows).

The mainstream IPTC Information Interchange Model editing tools also support editing of XMP data.

XMP is a registered trademark of Adobe Systems Incorporated. The XMP specification became an ISO standard and is not proprietary anymore.

Initially, Adobe released source code for the XMP SDK under a license called the ADOBE SYSTEMS INCORPORATED — OPEN SOURCE LICENSE. The compatibility of this license with the GNU General Public License has been questioned.^[6] The license is not listed on the list maintained by the Open Source Initiative and is different from the licenses for most of their open source software.^[7]

On May 14, 2007, Adobe released the XMP Toolkit SDK under a standard BSD license.^[4][2]

On August 28, 2008, Adobe posted a public patent license for the XMP.^[8]As of November 2016,^[update] Adobe continues to distribute these documents under the XMP Specification Public Patent License.^[2]

XMP was first introduced by Adobe in April 2001 as part of the Adobe Acrobat 5.0 software product.^[9] Before that, it was called XAP (Extensible Authoring and Publishing) as internal code name.^[10]

On June 21, 2004, Adobe announced its collaboration with the International Press Telecommunications Council. In July 2004, a working group led by Adobe Systems' Gunar Penikis and IPTC's Michael Steidl was set up, and volunteers were recruited from AFP (Agence France-Presse), Associated Press, ControlledVocabulary.com, IDEAlliance, Mainichi Shimbun, Reuters, and others, to develop the new schema.^{[citation needed]}

The "IPTC Core Schema for XMP" version 1.0 specification was released publicly on March 21, 2005. A set of custom panels for Adobe Photoshop CS can be downloaded from the IPTC. The package includes a User's Guide, example photos with embedded XMP information, the specification document, and an implementation guide for developers.^{[citation needed]} The "User's Guide to the IPTC Core" goes into detail about how each of the fields should be used and is also available directly as a PDF.^[11] The next version of the Adobe Creative Suite (CS2) included these custom panels as part of its default set.^{[citation needed]}

The Windows Photo Gallery, released with Windows Vista, offers support for the XMP standard, the first time Microsoft has released metadata compatibility beyond Exif.^[12]

• IPTC Information Interchange Model
• Resource Description Framework (RDF)
• Astronomy Visualization Metadata (AVM)
• Exchangeable Image File Format (Exif)