Image Metadata Inspector: Read the EXIF, IPTC, and XMP Hiding in Your Photos

Every photo you take or download carries more than pixels. A single JPEG can hold three separate metadata blocks at once, and most people never see any of them. EXIF records the camera settings, the timestamp, and sometimes GPS coordinates. IPTC stores the human-written stuff: captions, keywords, the photographer's name, and copyright lines. XMP is the modern layer that editing software writes into, including an edit history that shows what was done to the file after it left the camera. Reading all three gives you the full picture of where an image came from and what happened to it.

This guide walks through what those blocks contain, how to read them, and where this kind of inspection is genuinely useful. I'll also draw a clear line between inspecting metadata and scrubbing it, because those are two different jobs.

The three metadata blocks, and why an image has all three

EXIF (Exchangeable Image File Format) is written by the camera or phone at the moment of capture. It is the technical fingerprint: aperture, shutter speed, ISO, focal length, lens model, white balance, the exact capture timestamp, and — if location services were on — a GPS IFD with latitude and longitude.

IPTC (International Press Telecommunications Council) is the editorial layer. Newsrooms and stock agencies built it. It holds captions, headlines, keywords, the creator's name, credit lines, and copyright notices. When a photo agency licenses an image, the IPTC fields are how the rights travel with the file.

XMP (Extensible Metadata Platform) is Adobe's XML-based container, now an open standard. It can mirror EXIF and IPTC values, but its real value is what editors stamp into it: the software that touched the file, edit history entries, ratings, and document IDs. If a JPEG passed through Lightroom or Photoshop, XMP usually says so.

So a photo shared online can quietly carry the camera settings, the location it was shot, the photographer's name and copyright, and a record that it was edited — all at once. The Image Metadata Inspector reads these signatures straight from the file bytes and reports format, dimensions, megapixels, bit depth, color mode, orientation, plus flags for EXIF, GPS, XMP, ICC profile, and animation, alongside the camera string, software string, and timestamp.

A worked example: reading a single photo

Suppose a friend sends you a JPEG and asks what camera shot it. You drop it into the inspector and the metadata reads out like this:

Format: JPEG, 6000 × 4000, 24 MP, 8-bit, sRGB
Camera: SONY ILCE-7M3
Lens: FE 35mm F1.8
Aperture: f/1.8
Shutter: 1/250 s
ISO: 400
Timestamp: 2026-04-12 17:43:08
GPS: present — 35.0116° N, 135.7681° E
Software: Adobe Lightroom Classic 13.2
Copyright (IPTC): © Mai Tanaka

From that single read you learn it was a full-frame Sony with a fast 35mm prime, shot wide open at f/1.8 in late-afternoon light (the 1/250 and ISO 400 line up with that), the GPS pins it near Kyoto, the XMP/software field shows it was developed in Lightroom rather than straight out of camera, and IPTC names a copyright holder. None of that required opening a heavy editor. The aperture, ISO, lens, and GPS were sitting in the file the whole time, waiting to be decoded.

Where reading metadata actually pays off

Photography review. When you cull a shoot, the EXIF tells you which settings worked. Sorting by aperture and ISO across a folder shows you, in numbers, why some frames are crisp and others soft. Exporting a batch to CSV turns "I think I shot these at f/2.8" into a verifiable list.

Forensics and verification. If an image's claimed origin matters — a news photo, an insurance claim, a marketplace listing — the metadata is the first thing to check. Does the timestamp match the story? Does the GPS match the supposed location? Does the software field show an edit that the sender didn't mention? Missing metadata is its own signal: a re-saved screenshot or a heavily processed export often has its EXIF stripped, which tells you the file is not the original capture.

Copyright and licensing. IPTC and XMP copyright fields are how rights stay attached to a file. Before you reuse an image, reading those fields tells you whether someone has claimed it and how to credit them. For a content team migrating an asset library, auditing copyright lines across hundreds of files at once is far faster than opening each one.

Inspecting is not the same as scrubbing

This is the distinction that trips people up. An image metadata inspector and a privacy scrubber sit on opposite sides of the same data.

An inspector reads and reports. It shows you everything the file is carrying so you can make a decision — keep it, credit it, question it, or clean it. It changes nothing.

A privacy scanner or scrubber removes. Its job is to strip GPS, camera serial numbers, and timestamps before you publish, so you don't leak your home address in a photo's EXIF. That is a write operation, and it destroys data on purpose.

You usually want both, in order: inspect first to see what's there, then decide whether to scrub. Reading is also why the inspector deliberately does not map GPS coordinates to a place name — it flags that a GPS IFD exists and reports the raw values, leaving the interpretation to you. If you later resize or recompress an image, remember that Canvas-based tools frequently drop metadata as a side effect, so a resized copy may look identical but carry nothing. Tools like the Image Resizer change dimensions; the inspector is what confirms what survived the trip.

The read happens on your machine

Here is the part I care about most, having handled plenty of files I wouldn't want bounced through a stranger's server. The inspection runs entirely in your browser. The image bytes are parsed locally to pull out the signatures and metadata blocks, and the only thing produced is a report — a CSV you can keep or throw away. Pixels are never uploaded, and metadata that might be sensitive, like a capture location or a photographer's full name, never leaves the device during the read.

That local-only design is exactly why it works for forensics and for confidential client handoffs. You can inspect a sensitive batch of images without it touching the network. The caveat is on the output side: the CSV you export can contain private camera and date metadata, so treat that file with the same care you'd give the originals.

How I use it in practice

When a designer sends me a delivery folder, the first thing I do is run the whole batch through the inspector and skim the CSV. I'm looking for three things: dimensions that don't match the spec, a stray animated GIF hiding among the stills, and EXIF or copyright flags I didn't expect. Last month that exact pass caught a hero image delivered at 8000 px wide with full GPS data still attached — the photographer had shot it on a phone with location on. We stripped the metadata and downscaled it before it ever went live. The whole check took under a minute, and it happened on my laptop without a single byte leaving it.

Reading metadata is one of those habits that feels minor until it saves you from publishing someone's location or shipping a 24 MP file as a thumbnail. The data is already in your images. The inspector just makes it visible.

Made by Toolora · Updated 2026-06-13