PicaJet

Reference Glossary

IPTC

A metadata field set — caption, keywords, credit, copyright — maintained by the International Press Telecommunications Council for photo rights, embedded via legacy IIM or modern IPTC Core/Extension in XMP.

Why it matters in a DAM

Press, stock, and editorial photo workflows are built around IPTC fields — a wire photo without a By-line, Credit, and Copyright Notice can't legally clear a newsroom's editorial checks. In a DAM handling licensed or editorial imagery, IPTC fields are usually the ones legal and licensing teams query first, because they're the fields the industry actually standardized on for who made an image and what can be done with it.

A worked example

By-line Jane Alvarez
Credit Line Alvarez Photography / Agency X
Copyright Notice © 2026 Alvarez Photography. All rights reserved.
Keywords editorial, portrait, studio

Common mistake

Software or workflows built only around the legacy binary IIM standard silently drop fields when reading a file whose metadata was written in the newer XMP-based IPTC Core/Extension schema (or vice versa), so a round trip through an older tool can quietly strip captions or credit that the newer tool wrote in.

The IPTC itself dates to 1965, founded to safeguard the telecommunications interests of the world press. Its photo metadata work began with the Information Interchange Model (IIM), developed jointly with the U.S. Newspaper Association of America and approved in 1991 as a binary format for embedding caption, byline, and copyright data directly into image files — built for an era when news photos moved over wire services and needed a compact, standardized structure.

As Adobe’s XMP format became the dominant way to embed structured metadata in image files, IPTC and Adobe jointly developed the IPTC Core schema for XMP around 2004–2005, followed later by IPTC Extension for a broader field set. Modern software — Photoshop, Lightroom, most DAM platforms — reads and writes IPTC data through XMP rather than the older IIM binary format, though many tools still maintain IIM for backward compatibility, sometimes writing the same values into both to avoid data loss when a file passes through older systems.

The current reference is the IPTC Photo Metadata Standard, maintained and periodically revised by the IPTC’s Photo Metadata Working Group, which documents the full field set, its XMP namespaces, and mappings to related standards like Exif.

Frequently asked

What kind of information does IPTC metadata cover?

IPTC is a metadata field set — caption, keywords, credit, and copyright — maintained by the International Press Telecommunications Council specifically for photo rights. It's embedded either via the legacy IIM standard or the modern IPTC Core/Extension schema carried in XMP.

Why do editorial and stock photo workflows rely so heavily on IPTC?

Because a wire photo without a By-line, Credit, and Copyright Notice can't legally clear a newsroom's editorial checks. In DAMs handling licensed or editorial imagery, IPTC fields are usually what legal and licensing teams query first, since they're the fields the industry actually standardized on for authorship and usage.

What's the risk of mixing legacy and modern IPTC tools?

Software built only around the legacy binary IIM standard can silently drop fields when reading a file whose metadata was written in the newer XMP-based IPTC Core/Extension schema, or vice versa. A round trip through an older tool can quietly strip captions or credit that a newer tool wrote in.

How is IPTC data physically stored in a file?

Either through the legacy IIM binary block or through IPTC Core/Extension fields embedded in an XMP packet — both are ways of writing the same field set into the file, just using different underlying encodings.

Who typically queries IPTC fields inside a DAM?

Legal and licensing teams most often, since IPTC's caption, credit, and copyright fields are the industry-standard record of who made an image and what can be done with it, particularly for editorial and licensed photography.

Can IPTC and other metadata standards like Exif coexist in the same file?

Yes — a single file commonly carries Exif (device-generated technical data), IPTC (rights and captioning), and XMP (structured or custom fields) simultaneously, each covering a different layer of information about the same asset.

Sources