Inspect metadata attached to an image
The viewer requests EXIF, GPS, IPTC and XMP information from its metadata parser. Use it to examine fields that may accompany an image, such as camera settings or location, before sharing it.
Inspect a file
- Choose an image no larger than 25 MiB.
- Press Inspect metadata.
- Inspect the
metadataobject in the JSON result. The outer object also reports filename and bytes. - Select and copy fields if needed. The source image is not modified.
Example: a camera photograph
A camera JPEG may report camera model, exposure time and GPS coordinates. A screenshot often has fewer fields. Keys depend on the file and parser support: a missing GPS field is not evidence that a photograph never contained location data.
Try synthetic camera tags
Download the synthetic EXIF JPEG, choose it and press Inspect metadata. Look inside metadata for these deliberately created fields:
Make:All Device TestModel:Demo CameraArtist:Synthetic sample
The picture is a generated 640 × 480 diagram, not a camera photograph. No GPS tags were added. This example demonstrates that metadata can be written independently of the pixels; a camera-model field does not authenticate where or how an image was captured. The result's outer name and bytes describe the selected file rather than EXIF fields.
Next, make a copy with Remove Image Metadata, then inspect that downloaded PNG here. The three demonstration tags should no longer appear. Choosing another file clears the previous JSON so the earlier tags are not mistaken for the new file's result.
What does null mean?
A null result means no supported metadata was returned. It does not certify that the file contains no other data. Proprietary blocks, unsupported structures or other metadata formats may not appear.
Can the viewer remove GPS information?
No. Use Remove Image Metadata to create a pixel-only PNG and inspect that output. A location visible on a sign in the pixels remains a separate privacy consideration.
Parsing happens locally. Avoid publishing sensitive GPS fields from the output unintentionally. The underlying exifr parser exposes supported metadata; this page is not a forensic validation or complete privacy audit.





