Read recognized EXIF metadata from JPEG, PNG and WebP files locally. Inspect camera details, recorded timestamps, orientation and any EXIF GPS coordinates, then filter fields or download a JSON report.
No file selected.
JPEG, PNG or WebP · up to 20 MiB
No image selected.
Choose an image to read its recognized metadata. The photo is not rendered or modified.
These are coordinates stored in the file. They are not your current location. No map or location service is contacted.
Ready. Choose an image to inspect.
This viewer reports recognized EXIF/GPS and basic container details. It does not inspect XMP, IPTC, ICC profiles, maker-note subfields or embedded thumbnails. No tags found is not proof that the file contains no other metadata.
Metadata fields will appear here.
| Field | Value |
|---|
Reports are bounded to keep the page responsive. Any omitted fields, shortened text or summarized binary values are identified in the report.
EXIF timestamps often have no time zone. Values are shown as recorded; no local time zone is inferred. Metadata can be changed or removed and does not prove when, where or how a photo was taken.
Your image and metadata are never uploaded to any server; parsing runs locally in a disposable worker with a self-hosted library. GPS coordinates are shown as stored values without contacting a map or location service. The viewer does not render or modify the photo, and no account or metadata history is needed.
Recognized EXIF tags, computed EXIF GPS coordinates, and basic JPEG/JFIF, PNG and WebP container tags. It excludes XMP, IPTC, ICC profiles, maker-note subfield decoding and embedded thumbnails. Binary EXIF values may be summarized rather than decoded. This is a scoped metadata viewer, not a forensic inventory or a file-integrity validator.
JPEG, PNG and WebP files up to 20 MiB. The tool reads metadata without rendering pixels, so it does not impose the image-editing tools’ megapixel limit. Unsupported formats, corrupt metadata or browser limitations can still prevent parsing. The filename and MIME label alone are not trusted; the file signature is checked.
The file may have no EXIF, contain only unsupported metadata blocks, or have been stripped by editing, sharing software or the operating system before selection. Basic container fields can appear even without EXIF. Inspect the original file when possible. No recognized tags is not proof that no other metadata exists.
No. They come from EXIF GPS tags stored in the file, if a complete valid pair is recognized. The tool does not request device location or contact a map service. Coordinates display to six decimal places, while JSON keeps parsed numeric values. Other metadata blocks can contain location information outside this viewer’s scope.
No. Timestamps are shown as recorded. EXIF dates often omit a time-zone offset; this tool does not infer one. Browser file names and sizes are shown separately and are not treated as capture-time evidence. Metadata can be edited and does not prove when or where a photo was taken.
No. It contains normalized reported fields, readable descriptions, parsed values and any computed coordinates. Reports allow up to 1,000 fields and approximately one million serialized field characters, with 2,000-character text values, 64 array items and four nesting levels. Binary values show their length and a short byte preview. Truncation flags and parser warnings identify report limits. Compressed metadata parsing is capped at 4 MiB.
The table shows at most 250 matching rows at once. Narrow the search or select a group to view other fields. Copy and Download JSON include every field retained in the bounded report, independently of the current filter.
Yes. Stop, choosing another file or Clear terminates pending parsing and discards old results. The parser has a ten-second response limit. Clear and leaving the page release application-held bytes and metadata. The viewer does not rewrite the image or save inputs to browser storage.
