IPTC Photo Metadata
IPTC Photo Metadata defines descriptive and contextual photo properties whose meanings remain distinct from their XMP, legacy or other storage representations.
IPTC Photo Metadata supplies defined meanings for photographic descriptions and context. The reference here is IPTC Photo Metadata Standard 2025.1.
Those meanings are useful for personal photo collections as well as professional image workflows.
Describe one photograph with several roles
For an invented railway-platform photograph:
| Property role | Example information |
|---|---|
| Title/name | Platform at dawn |
| Headline | First departure after the storm |
| Description | An account of the depicted scene |
| Keywords | Railway, dawn, platform |
| Creator credit | The photographer's identity |
| Location information | The appropriate created or depicted location |
The title is a concise name, while a description can provide more context. Keywords provide additional discovery labels; they should not automatically replace a complete caption.
Creator, credit and rights-related properties also have distinct semantic roles. Keeping them in their defined fields retains more useful meaning than concatenating all text into one description.
Created location and shown location can differ
A photographer standing on one bank can photograph a landmark on the opposite bank. The camera location and the depicted landmark location then describe different places.
IPTC distinguishes Location Created from Location Shown in the Image. A GPS capture position can be relevant to the first relationship without fully naming every location shown.
This distinction can matter for browsing a travel collection. A person interested in pictures of the landmark need not be searching for the exact place where the camera stood.
A semantic field is separate from its storage mapping
For Emby, the relevant boundary is which defined properties the applicable reader imports and how they map to the library's fields. A standard defining a property does not establish that every property has a product mapping. XMP explains the packet and structured-value side of that relationship.
IPTC properties have specified representation mappings, including XMP and legacy IIM relationships where applicable. “IPTC data” should not be treated as one independent photo-file extension.
An image can carry descriptive properties in a metadata packet, and supported workflows can also use associated records. Different storage representations need coherent values where they express the same property.
A conversion that preserves visible pixels can omit those descriptions. Conversely, copying a packet onto another image can retain valid syntax while assigning the wrong description to that image.