Inspecting EXIF camera, exposure, GPS, and C2PA blocks locally
Every digital camera and smartphone writes invisible header blocks alongside raw pixels, recording device serial details, exposure math, and often exact street-level coordinates. Decoding those raw bytes inside your browser tab reveals what a file carries before you publish or archive it.
Six grouped metadata sections and live keyword filtering
Once a file loads, inspectPhotoDetailed organizes every discovered tag into six tables: File, Camera, Exposure, Location, Color & Provenance, and Notes. Typing into the Filter tags (ISO, lens, GPS, C2PA)… search bar narrows rows immediately across tag labels, internal keys, values, and section names.
A 256 px thumbnail preview renders beside the filename so you can confirm the right shot is loaded. If you spot sensitive location tags that should not leave your computer, click Remove hidden metadata to strip GPS, camera and date data without re-compressing pixels.
Private GPS coordinate decoding in decimal and DMS formats
According to the Library of Congress EXIF Format Description, EXIF stores location inside a dedicated GPS Image File Directory using degrees, minutes, and seconds (DMS) rational triplets paired with cardinal reference tags (N/S, E/W).
The viewer converts those DMS triplets into decimal coordinates rounded to 5 decimal places (about 1.1 m on the ground) and highlights them in a banner above the tables. No map tiles or tracking pixels load automatically; the Open on OpenStreetMap button only opens openstreetmap.org if you click it.
| Metadata section | Example tags inspected | Typical source block |
|---|---|---|
| File | File name, Container format, File size, dimensions | Container header (IHDR, SOF, ftyp) |
| Camera | Make, Model, Lens model, Software, Orientation | TIFF IFD0 and ExifIFD (0x010f, 0x0110) |
| Exposure | Shutter speed, Aperture, ISO, Focal length, Flash | ExifIFD rational and short tags |
| Location | GPS latitude, longitude, DMS string, Altitude | GPS IFD (0x8825) rational triplets |
| Color & Provenance | Embedded ICC profile, XMP, IPTC, C2PA manifest | JPEG APP1/APP2/APP11/APP13 |
| Notes | JPEG comments and PNG tEXt/zTXt/iTXt notes |
JPEG 0xfe or PNG text chunks |
Why do photos from messaging apps show no EXIF data?
Photos saved from WhatsApp, Instagram, Discord, or Slack almost always display only basic File dimensions and byte counts because those platforms strip EXIF and GPS blocks during upload re-encoding. Re-encoding shrinks payload weight and prevents strangers from extracting home addresses from public posts.
Automatic header stripping on WhatsApp, Instagram, and Slack
When a social network ingests a photo, its media pipeline decodes the pixels, resizes them to feed dimensions, and writes a fresh JPEG or WebP without copying APP1 EXIF or GPS directories. As a result, camera model, shutter speed, and coordinates disappear permanently from the downloaded copy.
How to inspect original camera and AirDrop files instead
To audit full camera settings or verify GPS exposure, inspect the untouched original transferred via USB cable, SD card, AirDrop, or cloud drive in “Original” mode. Converting modern formats for sharing can also drop headers if not handled carefully, so check AVIF to JPG outputs before sending archives.
How JPEG, PNG, WebP, AVIF, and HEIC store hidden metadata
Different image containers package metadata in distinct binary wrappers, even when they carry similar camera or creator fields. Understanding where each block lives explains why a PNG screenshot holds text notes while a DSLR JPEG holds TIFF directories and provenance boxes.
TIFF IFD tags, XMP packets, IPTC records, and C2PA JUMBF boxes
Inside JPEG files, inspectPhotoDetailed scans marker segments including 0xe1 (APP1) for Exif\0\0 and Adobe XMP packets, 0xe2 (APP2) for ICC_PROFILE, 0xed (APP13) for IPTC press captions, and 0xfe for embedded comments. Both little-endian (0x4949) and big-endian (0x4d4d) TIFF headers of 8 bytes with magic 42 and IFD entries of 12 bytes are supported.
As defined in the C2PA Content Credentials Specification v2.1, Content Credentials embed cryptographically signed provenance manifests inside JUMBF boxes. When a JPEG 0xeb (APP11) segment contains c2pa or jumd markers, the viewer flags C2PA provenance under Color & Provenance.
PNG tEXt, zTXt, and iTXt text chunks unpacked with Deflate
Tip: AI image generators and screenshot tools frequently embed prompts, software versions, and creation parameters inside PNG text chunks rather than EXIF blocks.
In PNG files, the parser walks every chunk after the signature and inflates compressed zTXt and iTXt payloads using fflate inflateSync. If you convert web graphics with a lossless WebP to PNG converter, inspect the resulting Notes table to see what text chunks remain.
Exporting JSON or CSV reports and cleaning sensitive tags
Auditing image metadata is often the first step before publishing forensic documentation, cataloging stock libraries, or sanitizing files for external clients. Built-in export controls turn raw binary tags into portable reports without extra command-line tools.
Copying or saving structured -metadata.json and -metadata.csv files
Under Export report, click Copy JSON to place formatted tag data onto your clipboard, or click Save JSON and Save CSV to download <basename>-metadata.json or <basename>-metadata.csv. Both formats include container metadata, grouped field keys, and decoded GPS values.
According to the W3C PNG Third Edition Specification, PNG chunks store standardized keywords like Title, Author, and Software cleanly, which map directly into CSV rows for spreadsheet audits.
One-click handoff to lossless metadata removal
When you need to publish graphics safely, you can export clean raster PNGs from SVG vectors or click Remove hidden metadata directly inside the viewer. Keeping both inspection and cleaning in local browser memory ensures sensitive GPS coordinates never cross the network.