About this exif reader
This EXIF reader inspects metadata embedded in a local photo and presents the available fields in a readable table. Camera make and model, exposure time, aperture, ISO, capture time, and GPS coordinates can explain how a picture was created. The locally bundled exifr parser also reads supported XMP and IPTC fields when they are present.
Select one or several images and click Read metadata. Every file receives its own table and a JSON download of the displayed values. Files without recognizable metadata show an explicit message rather than invented camera settings. The parser reads the original binary data; it does not create a replacement image or strip any tags.
Metadata is optional and editable. A capture date does not prove when a photograph was taken, and GPS values may be missing, stale, or deliberately changed. Dates without a recorded time-zone offset should not be treated as a reliable worldwide timestamp. Some maker-specific fields and uncommon file layouts may not decode. Use this view to check privacy before sharing an original photo, but use a separate metadata-removal workflow to erase tags. Your files and location fields stay on this device; no map lookup or remote inspection occurs.
Which controls should I check first?
The EXIF Reader form labels its controls as Choose image files (up to 20, 40 MiB each). Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
Readable tags are information stored in the file, not independently verified measurements. An absent GPS field should remain absent rather than being inferred from another tag. Capture time may lack a timezone, while file modification time is another value. The metadata download is a report of available tags and does not scrub the original photo. Inspect actual coordinates and timestamps before sharing that report.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| 1000; 750 | 25 |
| {"ISO": 200, "Make": "Example", "missing": null} | [["ISO", "200"], ["Make", "Example"]] |
What is supplied data and what is an inference?
The input is a supplied record, string or local file. The output can divide that data into fields or infer likely labels using documented rules. Keep the exact source with the result so that another person can check the interpretation. A parsed field is not automatically a verified fact about the outside world. A user-agent string can be changed, a metadata tag can be edited, and an extracted address can be unavailable. Preserve unknown or missing fields rather than filling them with plausible values that were never present in the source.
Why should I inspect related fields together?
A single label can conceal ambiguity that other fields make visible. A URL has a host, path, query and fragment; a file can have a filename, claimed media type and byte signature; photo metadata can have several different dates. Keep those distinctions in the report rather than collapsing them into one convenient summary. Compare each value with the kind of source it describes. A file extension does not define its actual byte format, and a date stored in an editable tag is not an independent measurement of when the picture was created.
How do I handle absent information?
Treat an absent field as absent. It can mean that the source never contained the information, that its format does not support it, or that the parser did not recognize it. An empty text field can also differ from an omitted field. Read any status message before inferring that the entire input failed. If the result depends on rules or a supported format list, compare a minimal recognized example first. Add a precise note about the missing source value instead of inventing a device model, owner, timestamp or destination based on surrounding clues.
What does the helper example verify?
The example supplies all of its input values explicitly and reports what the local function returned. That demonstrates parsing, normalization or field preparation for those values. It does not verify a device, fetch a website, prove file safety or authenticate metadata. The distinction remains even when an output label resembles a factual statement. A parsed browser family, for instance, comes from the supplied text rather than contacting that browser. Read the example as a reproducible interpretation of data and use separate evidence for claims about the actual external source.
Why does my image have no EXIF?
Screenshots and edited images often have no camera tags, and some services remove metadata before download.
Can this display GPS coordinates?
Yes, when the original file contains supported GPS fields. It does not perform an online map lookup.
Does reading metadata change my photo?
No. It reads the original bytes and optionally saves the displayed values as JSON.
Are capture dates authoritative?
No. Metadata can be edited and many capture dates lack a time-zone offset.