IPTC vs EXIF vs XMP: Check Photo Captions, Credits, and Rights

A photo's caption, creator credit, rights statement, and keywords can be stored separately from its camera settings. Use the IPTC viewer to read supported IIM fields in a JPEG, then check supported XMP with the full metadata viewer. An empty result in one section does not establish that the other is empty.

These five downloadable JPEGs contain the same generated illustration. Their metadata is invented: no real photographer, agency, camera capture, or private contact is represented. The combined example deliberately contains different creator and caption values in IIM and XMP.

IPTC, EXIF, and XMP: what to check

• EXIF: commonly holds camera Make/Model, exposure settings, and recorded capture dates. See the EXIF introduction and camera-identification examples.
• IPTC Photo Metadata: describes properties such as creator, caption, and rights. Some properties can be embedded using IIM or XMP.
• XMP: can carry IPTC properties and other metadata. An XMP-only caption is still editorial metadata, even when this IIM reader returns no fields.

The IPTC user guide explains the relationship and the need to synchronize overlapping fields. The table below maps four properties to their IIM and XMP representations; the last column shows our generated IIM example.

The slash in the caption above represents a line break. Three separate keyword records are displayed as garden, café, demonstration. The sample also records DateCreated as 2024-09-20, TimeCreated as 18:45:00 +05:30, a job reference of DEMO-2024-001, and the reserved demonstration contact editor@example.invalid. No timezone conversion is applied.

Download and inspect the examples step by step

1. Download the IIM-only JPEG. Open it in the IPTC viewer, or use Try Generated IPTC Sample to load the same file.
2. Check the 13 decoded fields. Search for Caption, Byline, CopyrightNotice, and Keywords. Categories and search filter the display; exports contain all decoded fields.
3. Select Export JSON and compare with the reference JSON. Export CSV if you need a readable table. Neither export rewrites the JPEG.
4. Download the XMP-only JPEG. The IIM viewer should show No Supported IPTC IIM Fields Decoded. Check creator, description, rights, and subject in the full viewer.
5. Compare the combined IIM/XMP JPEG. The IIM viewer reports Demo Studio A; the XMP creator records Demo Studio B. The caption and keyword list differ too. Confirm the intended values in your editing workflow before publication.
6. Try the EXIF-only JPEG and the untagged illustration. Neither yields supported IIM fields. The first still has the invented EXIF Make and Model shown in the full viewer.

The full viewer combines supported metadata for browsing; it does not reconcile IIM/XMP conflicts or guarantee namespace preservation. In the XMP-only example, description and rights can appear as structured text with language/value keys. The verification record includes a separate XMP read, IIM results, EXIF results, file hashes, and identical decoded-pixel hashes.

What empty results, read errors, and exports mean

This IPTC reader supports selected text datasets in JPEG Photoshop APP13 resources. Declared UTF-8 and ISO-8859-1 text are supported, as is undeclared ASCII. Other declarations, undeclared non-ASCII text, invalid UTF-8, and malformed resource lengths produce a read error. A read error is different from no supported fields being decoded. TIFF, PSD, XMP, binary datasets, and a full image-integrity check are outside this reader's scope.

Display values format date/time text and join repeated entries. JSON and CSV are readable field reports, not complete metadata backups. CSV uses UTF-8 with a byte-order mark and CRLF record endings; commas, quotes, and line breaks are escaped. Formula-like text is prefixed with an apostrophe. Import it as text when exact wording matters. JSON preserves the decoded text without that spreadsheet prefix. Read the photo-inventory guide for batch reporting and spreadsheet import details.

Review the copy you will actually publish

These fields are editable statements recorded in a file. Their presence does not establish ownership or permission; their absence does not establish that a photo is available to reuse. Compare the credit and rights wording with your publication requirements. Contact details and internal assignment IDs may also need review. Export and sharing workflows can change metadata, so inspect the exact delivered copy and keep the original.