What Is IPTC Data?

The two standards come from different industries solving different problems. EXIF exists because a camera knows things about the shot it just took and there was value in recording them. IPTC exists because a newspaper receiving a wire photo needs to know what it shows, who shot it, when, where, and whether it can be published — none of which a camera can answer.

That origin explains the shape of the data. Every EXIF field is a measurement or a setting. Every IPTC field is an editorial assertion: a caption someone wrote, a credit line someone agreed to, a copyright notice someone claims. IPTC is metadata about the content and the rights; EXIF is metadata about the capture.

This dual life is worth understanding, because it produces the single most common IPTC surprise: a photo can carry two copies of the same field. Adobe applications have long written the caption, creator, and copyright into both the legacy IIM block and the XMP packet, and kept them in sync. Other software writes only XMP. If the two disagree — because one tool edited one and not the other — different viewers will show you different answers for the same photo, and neither is wrong.

There is a third overlap to know about. EXIF has its own Artist and Copyrighttags, which mean roughly what IPTC's Creator and Copyright Notice mean. They are a different pair of fields in a different block. Filling in one does not fill in the other, which is why a photo can show a copyright notice in one program and nothing in the next.

The working pattern most photographers land on is four fields, applied to everything, automatically, at import:

• Creator — your name, spelled the way you want to be credited. This is the field most systems read when they display a byline.
• Copyright Notice — the notice string itself, such as © 2026 Jane Doe. All rights reserved.
• Rights Usage Terms— one plain sentence on what a person may do with the file. "Licensed for editorial use only" and "No use without written permission" are both more useful than an empty field.
• Web Statement of Rights — a URL pointing at the page on your site with the full terms and a way to contact you. This is the field that turns a notice into a lead.

The reason to apply these at import rather than at export is that metadata you have to remember is metadata you will forget. Every serious cataloguing tool supports a preset or template that stamps a set of fields onto every file as it comes off the card, and that is the whole discipline: set it once, and never think about it again.

And now the hard part, stated plainly: IPTC data is trivially removable, and most social platforms remove it. Re-encoding an upload discards the metadata blocks wholesale — the copyright notice goes into the same bin as the GPS coordinates. Anyone who wants to strip your notice can do it in one command, and anyone who saves your photo off Instagram gets a file with no notice in it without even trying.

So embed it — the cost is nothing and it works on every file that is passed around in its original form, which is most files that matter commercially. Just do not treat it as protection. It is a label, not a lock. Our page on which social media sites strip metadata covers which platforms keep anything at all, and adding copyright to photo EXIF covers the EXIF half of the job — the camera menu that stamps every frame, and the commands that fill an existing archive.

Read what a file already has

Drop the photo into our metadata viewer and open the All tab — IPTC fields are listed there alongside the EXIF ones, so you can see at a glance whether a caption and copyright notice survived whatever the file has been through. The photo is read in your browser and never uploaded.

On the command line, ExifTool is the reference implementation and shows you which block each value came from — which is exactly what you need when the legacy and XMP copies disagree:

# Every IPTC and XMP value, grouped by the block it lives in
exiftool -a -G1 -s -IPTC:all -XMP:all photo.jpg

# Just the rights fields, across every block that might hold them
exiftool -Creator -Artist -CopyrightNotice -Copyright -Rights -UsageTerms photo.jpg

Write the fields

Naming the group tells ExifTool which block to write. Write both if you want older software to see the values too:

# Modern: the XMP packet, which is what current tools read
exiftool -overwrite_original \
  -XMP-dc:Creator="Jane Doe" \
  -XMP-dc:Rights="© 2026 Jane Doe" \
  -XMP-xmpRights:UsageTerms="No use without written permission" \
  -XMP-xmpRights:WebStatement="https://example.com/licensing" \
  photo.jpg

# Legacy: the IIM block. Declare UTF-8 or non-ASCII names get mangled.
exiftool -overwrite_original -charset iptc=UTF8 \
  -IPTC:CodedCharacterSet=UTF8 \
  -IPTC:By-line="Jane Doe" \
  -IPTC:CopyrightNotice="© 2026 Jane Doe" \
  photo.jpg

# Stamp a whole shoot at once
exiftool -overwrite_original -r \
  -XMP-dc:Creator="Jane Doe" -XMP-dc:Rights="© 2026 Jane Doe" \
  ~/Pictures/shoot/

That CodedCharacterSet line is not optional pedantry. The legacy IIM block has no inherent encoding, and readers assume Latin-1 unless the file explicitly declares UTF-8 — which is why accented names and non-Latin scripts come back as mojibake from the IPTC block while the XMP copy, which is XML and therefore Unicode by construction, reads back perfectly.

In a GUI, the field you want is usually behind a menu item called File Info, Metadata, or Properties. Photoshop and Bridge put the IPTC panels in File Info and can save a filled-in set as a reusable template. Lightroom Classic exposes them in the Metadata panel and will apply a metadata preset to every photo on import — which is the setting worth finding, because it is the one that makes the whole thing automatic.

Two cautions. First, some editors write IPTC changes into a sidecar file — an .xmp next to the raw file — rather than into the image, so the metadata lives beside the photo and is lost if you move one without the other. Sidecars are normal for raw formats; make sure your export writes the fields into the JPEG itself. Second, exporting a photo does not always carry IPTC across: check your export dialog for a metadata dropdown, and pick the option that keeps copyright and contact info rather than the one that strips everything.

Choosing between them is mostly a question of when you want the metadata applied. If it should happen automatically to every photo you shoot, you want a cataloguing tool with import presets — Lightroom Classic or digiKam. If you need to fix or inspect specific files, or you are scripting anything, ExifTool is the answer and nothing else comes close. If you shoot to a deadline and metadata has to be complete before the file leaves the building, that is exactly the problem Photo Mechanic was built to solve.

What you should not rely on: the built-in file properties dialogs in Windows and macOS. They expose a handful of fields under names of their own choosing, and it is not always clear which block they write to — fine for a quick look, unreliable as the tool of record for rights information.