TL;DR: EXIF, IPTC, and XMP are three separate metadata standards that can all live inside the same image file. EXIF (Exchangeable Image File Format) is written by the camera and records technical capture data—make, model, exposure, timestamp, and GPS coordinates—stored in a JPEG's APP1 marker. IPTC, from the International Press Telecommunications Council, holds descriptive and rights data—caption, keywords, creator, and copyright—originally in the legacy IPTC-IIM block inside the APP13 marker. XMP (Extensible Metadata Platform), Adobe's RDF/XML framework from 2001, acts as a modern container that can mirror both and store far more, either embedded in the file or in a separate .xmp sidecar. They overlap heavily, often duplicate the same value, and can disagree—which is exactly why removing metadata means clearing all three at once.
If you have ever opened a photo's "info" panel and seen camera settings in one place, a copyright notice in another, and a caption somewhere else, you have already met all three of these standards without knowing their names. EXIF, IPTC, and XMP are not competing products you choose between. They are layers that accumulate inside a single file as it moves from the camera, through editing software, and out to the world. This guide explains what each one is, where it physically lives in the file, how they overlap, and what that means when you want to read or strip the data.
Three Standards, One File: Why Photos Carry All of Them
The reason a photo can hold three metadata systems at once is that each was invented to solve a different problem at a different time. EXIF came from camera manufacturers who needed a standard way to record how a shot was taken. IPTC came from the news industry, which needed captions, credits, and rights to travel with press photos. XMP came from Adobe, which needed a flexible, future-proof way to store editing history and every other kind of metadata in one extensible format.
None of these efforts replaced the others. Instead, software learned to read and write all of them, so a modern JPEG often carries an EXIF block from the camera, an IPTC block added during cataloging, and an XMP packet written by the editor—each describing some of the same picture. Understanding the difference is the foundation for everything else, including our broader explainer on what EXIF data actually is and why it matters for privacy.
EXIF: What Your Camera Writes
EXIF, short for Exchangeable Image File Format, is the oldest and most automatic of the three. First published in 1995 and maintained since by camera-industry bodies, it defines how a device records information about a photograph inside the photograph's own file. Every time you press the shutter on a phone or a dedicated camera, the device writes an EXIF block alongside the pixels.
The fields are technical by design. EXIF stores the camera make and model, the lens, focal length, aperture, shutter speed, ISO, and whether the flash fired. It stamps the exact date and time of capture, often to the second. And in a dedicated GPS sub-block, it can record latitude and longitude accurate to a few meters if location services were enabled. That GPS field is the one with the biggest privacy implications, because a single image can point straight at your home.
The defining trait of EXIF is that it is written by the device, not by you. You rarely choose what goes in—the camera decides. That makes it reliable for photographers studying their settings, and quietly risky for anyone who shares files without checking what the camera recorded.
Photo by MART PRODUCTION on Pexels
IPTC: The Caption, Credit, and Rights Layer
Where EXIF describes the camera, IPTC describes the content and ownership of the image. The standard comes from the International Press Telecommunications Council, which built its original Information Interchange Model (IPTC-IIM) in the early 1990s so that news photos could carry their caption, byline, and copyright as they were transmitted between agencies and newspapers.
IPTC fields are the human, editorial ones: a headline and caption, descriptive keywords, the creator or "by-line," the copyright notice and usage terms, and named locations like city and country. Unlike EXIF, this data is almost never written by the camera. It is added later, by hand or in bulk, inside cataloging and editing software when a photographer tags a shoot or a stock contributor prepares a submission. The official IPTC photo metadata standards define exactly which fields exist and what each is meant to hold.
This is the layer that matters most for professionals who care about attribution and licensing—the same concerns we cover in our guide on removing metadata before delivering photos. It is also why a downloaded image can sometimes reveal the photographer's real name and contact details long after the file has changed hands.
XMP: The Container That Ties It Together
XMP, the Extensible Metadata Platform, is the newest of the three and the hardest to picture, because it is less a fixed set of fields than a framework. Adobe introduced it in 2001 and it was later standardized as ISO 16684-1. Technically, XMP is a subset of the W3C's RDF expressed in XML, which means any software that can read XML can parse it without a proprietary decoder.
What makes XMP powerful is extensibility. It uses named "namespaces" to organize data—dc for Dublin Core descriptive fields, photoshop for editorial values, Iptc4xmpCore for the modern IPTC schema, and even an exif namespace that can mirror camera values. So XMP does not just add new fields; it can re-express EXIF and IPTC data in one consistent, modern structure. Adobe's XMP standards documentation lays out how those namespaces fit together.
Crucially, XMP can live in two places. It can be embedded directly inside a JPEG, TIFF, PNG, or PDF, or it can be stored in a separate .xmp sidecar file that sits next to the original. That sidecar behavior is central to RAW workflows, which we will come back to next.
How XMP Sidecars Work With RAW Files
Proprietary RAW formats—Canon's CR3, Nikon's NEF, Sony's ARW, and others—are a problem for metadata. Editors are reluctant to write new data back into a RAW file, because the format is proprietary and altering it risks corrupting the original capture. XMP solves this with the sidecar.
When you adjust a RAW image in Lightroom or Camera Raw, the program does not rewrite the RAW. Instead it writes your edits and metadata into a small companion file with the same name and an .xmp extension. Open a folder of RAW shots that have been edited and you will often see this pairing: IMG_4087.CR3 next to IMG_4087.xmp. The DNG format is the exception—it is designed to embed XMP internally, so it needs no sidecar.
The practical consequence is easy to miss: if you clean the metadata inside a RAW file but leave its .xmp sidecar untouched, the descriptive and rights data is still sitting right there in the folder. Anyone who receives both files receives the metadata. We dig into this further in our piece on delivering RAW files without leaking metadata.
Photo by Kawê Rodrigues on Pexels
How EXIF, IPTC, and XMP Overlap—and Disagree
The three standards were built independently, so they inevitably describe some of the same things in different vocabularies. The clearest example is the creator field. The same photographer's name can be written into the EXIF Artist tag, the IPTC By-line, and the XMP dc:creator property—three copies of one fact, in three places, in three formats. Copyright and description fields overlap the same way.
This redundancy is convenient until the copies disagree. Edit a name in one tool and not another, and a file can end up claiming two different creators depending on which block a reader trusts. To manage this, an industry group called the Metadata Working Group published guidance in 2010 on how software should reconcile the standards—for instance, preferring EXIF or IPTC-IIM based on a stored checksum, and synchronizing values into XMP so they stay aligned. Good cataloging software handles this reconciliation automatically; for example, some editors expose a single "creator" field and quietly write it to all three locations at once.
For you, the takeaway is simpler than the machinery behind it: a value you think you deleted in one place may still survive in another. That is the heart of why partial cleanup fails.
Where Each Standard Lives Inside the File
It helps to know the physical addresses, because tools that strip one block can leave another intact. In a JPEG, EXIF and XMP are both read from the APP1 marker segment, while the legacy IPTC-IIM block sits in the APP13 marker—often called the Photoshop Image Resource Block, because Photoshop popularized that location. The reliable way to inspect all of them is a full metadata reader such as the open-source ExifTool, which surfaces every tag regardless of which marker holds it.
This separation explains a frustrating real-world outcome. A quick tool that clears the EXIF APP1 segment may leave the IPTC APP13 block—and its embedded caption, keywords, and copyright—completely untouched. The photo looks "cleaned" in a basic viewer that only reads EXIF, while a more thorough reader still pulls your name and keywords straight out of the file. Genuine removal has to address every marker, not just the most famous one.
Which One Holds the Data You Want to Remove?
If your concern is privacy and location, EXIF is the block to watch, because that is where the GPS coordinates and capture timestamp live. If your concern is attribution, licensing, or anything tied to your identity as the creator, the descriptive and rights data is most likely in IPTC and mirrored into XMP. And if you have been editing RAW files, remember that a copy of that descriptive metadata may be living in a .xmp sidecar outside the image entirely.
In practice, you rarely want to keep one standard and surgically remove another. The fields overlap too much, and the same sensitive value often appears in two or three of them. This is the same lesson we draw in our comparison of C2PA versus EXIF: metadata is layered, and trusting a single block to be "the" location is how data slips through. The dependable approach is to treat EXIF, IPTC, and XMP as one combined payload and clear the whole thing.
How to Remove EXIF, IPTC, and XMP at Once
Removing all three is simpler than understanding them, because you do not need to know which field holds what—you clear them together. Start by opening the photo in a metadata viewer so you can see what is actually present, including the IPTC block that basic tools skip. If you are working with a RAW file, check the folder for a matching .xmp sidecar, since that file carries its own copy and has to be handled too.
The fastest reliable method is a dedicated cleaner like Metadata Cleaner that strips EXIF, IPTC, and XMP in a single pass and processes the image locally, so a geotagged photo never has to be uploaded to a third party just to be cleaned. For a full walkthrough across Mac, Windows, and iPhone, see our guide on how to strip EXIF data from a photo, which applies to the other two standards as well. After cleaning, re-open the copy in a full viewer and confirm that no EXIF, IPTC, or XMP tags remain before you share it.
One honest limit is worth stating: stripping these three blocks removes the embedded text metadata, but it does not change the pixels themselves. It will not erase a visible watermark, a logo burned into the image, or content that platforms fingerprint visually. And if a service kept its own copy of your original on upload, removing metadata from your local file cannot reach back and delete theirs. Clean before you share, not after.
Conclusion
EXIF, IPTC, and XMP are not rival formats you pick between—they are three layers that pile up inside one photo as it travels from sensor to software to the open web. EXIF is the camera's technical record, IPTC is the editorial and rights layer, and XMP is the modern container that can hold and reconcile both, whether embedded in the file or parked in a sidecar. Because they overlap and duplicate the same sensitive values, reading any one of them tells only part of the story, and clearing any one of them leaves the rest behind.
If you want the data gone, treat all three as a single payload and strip them together. Try Metadata Cleaner free to remove EXIF, IPTC, and XMP from your images in one local, private pass—no uploads, no leftovers.