IPTC vs XMP Metadata: Differences and Which to Use
October 23, 2026
IPTC and XMP are not really rivals. IPTC defines what descriptive information a photo can carry (title, caption, keywords, creator, location). XMP is a container format that can hold that information, and much more. The older IPTC format (called IIM) is a separate, legacy way of storing the same kind of fields.
In practice: use XMP as your main format, and keep the older IPTC block in sync if your software supports it. Most modern tools read both, but some older systems only read the legacy block.
The short version
| IPTC (IIM, legacy) | XMP | |
|---|---|---|
| What it is | An older binary block of fields in the file | An XML-based, extensible metadata format from Adobe (standardised as ISO 16684-1) |
| Typical content | Caption, keywords, creator, copyright, city, country | Everything IPTC fields cover, plus ratings, edit history, custom fields |
| Text encoding | Often limited or inconsistent | Unicode (UTF-8) |
| Field limits | Fixed length limits per field | No fixed limits per field |
| Extensible | No | Yes, through namespaces |
| Can sit outside the image file | No | Yes, as a sidecar .xmp file (common with raw files) |
The confusing part is that "IPTC" means two things:
- IPTC IIM is the original 1990s format for news photos.
- The IPTC Photo Metadata Standard (IPTC Core and IPTC Extension) is the modern list of fields, which is now normally stored inside XMP.
So when a photo editor shows an "IPTC" panel, the values may be saved in the legacy block, in XMP, or in both.
What each one actually is
IPTC IIM: the legacy block
IIM stands for Information Interchange Model. It was designed so news agencies could attach captions and credits to images. In a JPEG, the data sits in a segment that Photoshop popularised, made of numbered records and datasets. For example, the caption is dataset 2:120 and keywords are 2:25.
It works, and it is still widely read. Its weaknesses are that fields have length limits, character encoding can be inconsistent, and it cannot be extended with new fields.
XMP: the flexible container
XMP (Extensible Metadata Platform) stores metadata as XML. Each field belongs to a namespace, such as Dublin Core (dc:), Photoshop (photoshop:) or the IPTC namespaces. That makes it possible to store structured data, multiple languages and custom fields.
XMP can be embedded in JPEG, TIFF, PNG, WebP and many other formats. For raw files, editors usually keep it in a sidecar .xmp file next to the original so the raw file stays untouched.
How the fields map across
Many of the same fields exist in both. This is the mapping most people need:
| What you see | IPTC IIM field | XMP property |
|---|---|---|
| Title | Object Name (2:05) | dc:title |
| Description / caption | Caption/Abstract (2:120) | dc:description |
| Keywords | Keywords (2:25) | dc:subject |
| Creator | By-line (2:80) | dc:creator |
| Copyright notice | Copyright Notice (2:116) | dc:rights |
| Headline | Headline (2:105) | photoshop:Headline |
| City | City (2:90) | photoshop:City |
| Country | Country/Primary Location Name (2:101) | photoshop:Country |
This is why a keyword you type in one app often shows up in another: they are reading the same logical field from different places.
Where EXIF fits in
EXIF is a third thing. It is the technical data a camera or phone writes at capture: exposure, lens, date and time, and GPS position. It uses its own structure, separate from both IPTC and XMP. (See EXIF Data Explained for the full picture.)
This matters for geotagging. GPS coordinates are normally stored in EXIF fields. XMP can mirror them with exif: properties, and the IPTC Extension has location structures that can include coordinates. The legacy IIM block has text location fields (city, state, country) but no latitude and longitude fields.
A simple way to remember it:
- EXIF: what the camera recorded (including GPS).
- IPTC / XMP: what a person wrote about the photo (title, description, keywords, rights, place names).
Which should you use?
Use XMP as your primary format
It has no field-length limits, handles Unicode properly, and is where the current IPTC fields live. If you are choosing one, choose XMP.
Keep IPTC IIM in sync if you can
Some older software, stock agency ingest tools and news workflows still read the legacy block. If your IIM and XMP values disagree, different programs may show different results. The Metadata Working Group published guidelines on reconciling these, and many editors follow them by writing both. If your tool lets you, write both and make sure they match.
Don't expect every platform to read it
Many social networks, messaging apps and some website builders strip or rewrite metadata when you upload. A file that has perfect metadata on your drive may arrive with none. Check the result after upload rather than assuming.
Does this matter for SEO?
Be cautious here. Google has not published how it uses embedded photo metadata for ranking, and no tool can promise visibility from it. Metadata is still useful for organisation, rights information and handing files to clients or agencies. For more on the local search question, see Does Geotagging Photos Help Local SEO?.
Good file names, alt text, and relevant page content are separate from embedded metadata, and you should not rely on metadata alone.
How to see which metadata a photo has
You can check what a file contains, and which blocks are present, without installing anything. The free photo metadata checker shows what is embedded in a photo. Our guide on how to check photo metadata on any device covers other methods, such as the built-in tools on Windows and macOS.
Writing IPTC/XMP fields in practice
If you need to add a title, description, keywords and GPS coordinates to a batch of photos, Geotagr writes these, along with business details, into the photo files as IPTC/XMP fields. It runs in your browser, and the photo files are not uploaded to Geotagr's servers.
A few practical notes:
- JPG, HEIC, PNG and WebP files can be opened. HEIC, PNG and WebP are converted and saved as JPG.
- Batch tagging and presets are available for repeating the same business details across many photos.
- GPX track matching and CSV import, as well as AI suggestions, are paid features. See pricing.
If your use case is specific, these guides go through it: geotag photos for Google Business Profile, real estate listing photos, job-site photos for contractors and stock photography.
One privacy point: description and location fields travel with the file. Before sharing photos publicly, consider whether you want that information included. Our guide on removing location data from photos explains how.
FAQ
Is XMP replacing IPTC?
Not exactly. The IPTC Photo Metadata Standard still defines the fields, but it is now mainly expressed in XMP. The older IIM block is a legacy storage method that remains in use for compatibility.
Can a photo have both IPTC and XMP?
Yes. Many photos carry both, and many editors write both at once. Problems appear when the two copies hold different values, so keep them in sync.
Does IPTC or XMP store GPS coordinates?
GPS is normally stored in EXIF. XMP can mirror it, and the IPTC Extension can describe locations with coordinates. The legacy IPTC IIM block has place-name fields but not latitude and longitude.
Which one is better for keywords?
XMP, because it has no short per-keyword length limits and supports Unicode. If you work with software that only reads the legacy block, keep IIM keywords in sync too.
Will my metadata survive uploading to social media?
Often not. Many platforms strip or rewrite metadata on upload. Check the file after it is published, for example by downloading it and running it through a metadata checker.
Do I need to know the technical details to tag photos?
No. For most people, it is enough to fill in title, description, keywords and location using a tool that writes standard fields, then verify the result.