IPTC is the most widely used metadata standard for photos, developed by the International Press Telecommunications Council, defining fields for rights, creator, location, dates, and descriptions. It is not a piece of software; it is a shared specification that any compliant tool can read and write, which is what makes metadata portable between systems.
Why it matters
Mapping your metadata to a standard like IPTC means information moves cleanly between tools and survives a platform migration, instead of being trapped in one system's proprietary fields. A shared standard also means a photographer, a wire service, and a brand can exchange images without re-keying the rights and credit.
How it shows up in practice
IPTC began in news and photography and is now used across industries. Most DAM platforms support it, and tools like Adobe Bridge and Photo Mechanic expose IPTC fields directly. A common wrinkle: IPTC does not support custom fields, so organization-specific information sometimes has to be mapped into a standard field whose name is not obvious. That is why teams build a mapping table that records which information goes in which IPTC field, so everyone enriching or searching assets reads them the same way.
Common mistakes
- Inventing proprietary fields instead of mapping to IPTC where a field exists.
- Skipping the mapping table, so the same information lands in different fields.
- Assuming every platform exposes the same IPTC fields the same way.
- Not confirming IPTC metadata stays embedded after export.
Stacks covers standards in metadata best practices.