Image & EXIF Inspector
Inspect image format, dimensions, camera settings, EXIF, GPS, colour profile, and other embedded metadata — locally.
Processed locally in your browser — this file is not uploaded
Image Inspector workspace
Start with an image
See what’s really inside.
Processed locally in your browser — the file, filename, and embedded metadata are not uploaded.
Reading locally
Looking through the image…
Checking its format and embedded metadata without sending it anywhere.
Couldn’t inspect this one
This image could not be inspected
Try another image.
Preview
Your image
Preview is decoded by your browser and never uploaded.
At a glance
Image details
Privacy cleanup
Remove supported metadataFor JPEG files, Celestia Tools can create a verified clean copy without re-encoding the image pixels.
Select a JPEG to enable privacy cleanup.
Choose or drop an image to begin.
A little context
The useful details, without the metadata maze.
The inspector puts the everyday facts first, while keeping the full parsed metadata available when you need to dig deeper.
What can it inspect?
The Image Foundation inspector recognises JPEG, JPEG XL, PNG, WebP, TIFF, HEIC/HEIF, AVIF, and GIF signatures and reads supported EXIF, XMP, IPTC, ICC/profile, GPS, and container metadata. Browser preview support is separate: metadata may still be readable when your browser cannot display a format.
What does “Download clean copy” remove?
The first verified removal path is JPEG only. It removes EXIF/XMP APP1 data, IPTC/Photoshop APP13 data, Ducky APP12 metadata, JPEG comment segments, and bytes trailing after the JPEG end marker. It preserves ICC colour-profile segments and copies the encoded image scans without re-encoding them. Unknown application segments are retained rather than being silently destroyed, so Celestia Tools does not claim that every possible vendor-specific byte has been removed.
Why can lens aperture numbers disagree?
EXIF LensSpecification describes the lens range: minimum and maximum focal length plus the minimum f-number at each end. It is different from the shot’s FNumber and from the descriptive LensModel, so phone-camera metadata can legitimately show different aperture values in those fields. The inspector keeps those source fields separate rather than trying to reconcile them.
Does my photo leave my device?
No. Celestia Tools reads the selected file locally. The filename, image bytes, GPS coordinates, camera details, clean-copy output, and other extracted metadata are not uploaded. The page still downloads normal same-origin application assets.
Why are some fields marked Location or Identifier?
Those badges call attention to metadata that may reveal where an image was captured or identify a creator/device. For supported JPEG files, the clean-copy action can remove the verified metadata families listed above while preserving the original file untouched.
Why can metadata appear without a preview?
Image decoding and metadata parsing are separate operations. A browser may not render JPEG XL, HEIC, TIFF, or another format even though Celestia Tools can inspect its metadata. Very large files can also skip preview decoding to keep memory use reasonable.
Does “no metadata found” mean the file is privacy-safe?
Not necessarily. It means the metadata formats parsed by this inspector did not expose fields here. The JPEG clean-copy action is separately verified for the metadata families it supports, but unsupported formats and unknown vendor-specific blocks are not described as universally metadata-free.