To view EXIF data on iPhone without installing a new app, save the JPEG to a local location, open it in Safari with the EXIF Viewer, and read the parsed metadata table in the current tab — the photo bytes never leave the device. The iPhone camera embeds a rich EXIF block into every JPG by default, including the make and model, lens, exposure settings, capture timestamp, and often GPS coordinates, but the built-in Photos info pane only exposes a small slice of those fields. A browser-based EXIF viewer parses the same APP1 segment that iOS reads internally and surfaces the full recognized set in a plain table, which is useful when you want to confirm settings, audit a downloaded image, or check whether location data is still attached before sharing the file. Because everything runs locally in the browser tab, the original photo is never uploaded to a server, and you can review the values on the phone itself.
Why iPhone Users Often Need a Browser-Based EXIF Tool
The iPhone's built-in Photos app does surface some image information: tap the "i" info icon or swipe up on a photo to see date, device, lens, focal length, and a small map for location. That panel, however, only renders the values Apple chose to highlight, hides the raw EXIF structure, and gives no way to copy the metadata out for reference. Third-party EXIF apps in the App Store fill the gap, but most of them request full Photos library access, run ads, or quietly upload thumbnails to remote servers for parsing — which is exactly the wrong trade-off for a privacy-sensitive task.
A browser-based reader avoids those trade-offs entirely. You hand it one specific JPG, the file is parsed in the current browser tab, and the original image is never transmitted. On an iPhone that matters more than on a desktop because iCloud Photos is enabled by default, so any tool that uploads by default risks syncing a private image through a third-party endpoint before the user realizes what happened. The EXIF Viewer keeps the bytes and the parsed values in the local tab and never executes the metadata, so a malformed file cannot trigger remote actions on the photo.
What the EXIF Viewer Reads From a JPEG
The EXIF Viewer is built around a documented allowlist of common EXIF tags. When you load a JPEG, it locates the first valid APP1 segment, validates the embedded TIFF header and byte order, and walks the IFD0, Exif sub-IFD, and GPS sub-IFD in sequence. Only fields on that allowlist are decoded; proprietary maker notes — including Apple's unique HDR, sensor, and Live Photo tags — are intentionally skipped rather than guessed.
The supported set covers the fields most people actually want when auditing an iPhone photo:
| Field group | Examples the viewer reports | Source directory |
|---|---|---|
| Camera identity | Make, model, software | IFD0 |
| Capture settings | Exposure time, F-number, ISO, focal length | Exif sub-IFD |
| Timing | Original capture date, modify date | IFD0 / Exif sub-IFD |
| Geometry | Pixel dimensions, orientation | IFD0 |
| Lens | Lens model | Exif sub-IFD |
| Location | GPS latitude, longitude, hemisphere references | GPS sub-IFD |
Parsing follows the CIPA Exif 2.3 specification and is independently cross-checked against the ExifTool tag table. Safety limits reject malformed segment lengths, directories with excessive entries, and offsets that point outside the selected file — so a corrupted or hostile JPEG fails cleanly instead of crashing the page. The reader covers both little-endian and big-endian TIFF byte order, inline and offset values, ASCII, SHORT, LONG, RATIONAL, and signed numeric types.
Get Your iPhone Photo Into the EXIF Viewer
Since the EXIF Viewer runs in a browser tab, the workflow is: get the JPG off the phone and into the page. There are several ways to do that on iOS, and each one keeps the file local until you choose to upload or share it.
Method 1 — From the Photos app:
- Open Photos and tap the photo you want to inspect.
- Tap the share button (the square with the upward arrow).
- Choose "Save to Files" and pick a local folder such as "On My iPhone" or the Downloads folder inside iCloud Drive.
- Open Safari and navigate to the EXIF Viewer page.
Method 2 — From the Files app:
- Open the Files app and locate the JPEG.
- Long-press the file and choose "Share", then "Open in Safari" (or copy the file path).
- In Safari, open the EXIF Viewer page and select the local file from the picker.
Method 3 — AirDrop from a Mac:
- On the Mac, AirDrop the JPG to the iPhone.
- Accept the file in the iPhone's AirDrop prompt; it lands in the Files app.
- Continue with Method 2 from step 3.
Important note for iPhone camera files: the iPhone saves photos as HEIC by default. If the file you AirDropped or saved is HEIC, the EXIF Viewer will not parse it. Switch the camera format to "Most Compatible" in Settings → Camera → Formats, or convert the HEIC to JPG before loading it. Screenshots taken on the iPhone are PNG and carry no EXIF segment at all, so they will produce an empty result — that is expected, not a bug.
View EXIF Data With the EXIF Viewer
Once the JPEG is reachable from local storage, the actual inspection is short. The page accepts JPG and JPEG up to 25 MiB and produces a parsed table in the same tab:
- Choose a local JPG or JPEG file up to 25 MiB. Tap the file picker, select the saved photo, and wait for the parser to walk the APP1 segment. The selection happens entirely in the browser — no upload is performed.
- Review the recognized EXIF rows, especially any GPS coordinates. Scan the table top to bottom: camera identity, capture settings, timing, geometry, lens, and location. A missing row means the file simply does not contain that field; the parser does not invent values for absent tags.
- Use a full desktop metadata tool if you need unsupported formats, maker notes, or forensic evidence. Close the tab when you are done — the parsed values are kept in the current browser session and are not stored anywhere persistent.
If the photo carries no rows at all, the file either has no EXIF segment or its metadata was stripped — for example, by a messaging app or social platform that scrubs metadata on upload. An empty result is information, not an error.
How to Read GPS and Capture Fields Without Misreading Them
GPS coordinates are the most sensitive EXIF field on an iPhone. The EXIF Viewer converts the stored degrees-minutes-seconds value into signed decimal degrees using the N/S and E/W references: a positive latitude paired with "N" and a positive longitude paired with "E" follows the conventional northern/eastern sign convention. If the hemisphere reads "S" or "W", the sign flips, so a southern-hemisphere photo ends up with a negative latitude even though the raw digits look positive.
Capture timestamps come from two distinct fields. The Modify Date records when the file was last written, which is rewritten by every editor and by most messaging apps. The Original Capture Time records when the shutter actually fired and survives most round-trips through Photos and AirDrop. Comparing the two tells you whether a file has been edited since it was taken, but neither value is proof on its own — both can be edited, copied, or stripped.
Lens model and focal length together confirm which iPhone lens was active — main, ultrawide, or telephoto — and exposure time, F-number, and ISO together reveal whether Night Mode or a long exposure was active. If you do not want the GPS row on a sensitive iPhone photo to leak, strip it before sharing; a browser-side EXIF removal guide walks through rebuilding the JPEG from decoded pixels locally so the original image stays on your device and the new file carries no source EXIF or GPS segment.
When a Browser Tool Is Not Enough
The EXIF Viewer is intentionally narrow. It does not read HEIC, XMP, IPTC, RAW, video, or proprietary maker notes. If you need any of those, the right move is to switch to a maintained desktop metadata tool such as ExifTool and preserve a copy of the original file. Browsing the metadata inventory from a desktop tool is also better for batch work and for forensic-grade verification, where byte-level provenance matters.
A practical example: if you receive a JPG that claims to be a screenshot from a financial app, and the EXIF Viewer shows a Make of "Apple" and a Model of "iPhone 15" with a modify date one second before the original capture timestamp, the timestamp relationship is not proof of the file's authenticity. If, on the other hand, the same file shows no Make, no Model, and no GPS at all, it has likely been processed through a stripping service — and no inference can be drawn from missing data, because metadata can be edited, copied, stripped, or absent for legitimate reasons. Metadata is never proof of authorship, ownership, capture time, location, or authenticity.
If the GPS row on a sensitive iPhone photo is something you do not want to share, strip it before sending. A browser-side EXIF remover rebuilds the JPEG from decoded pixels locally, so the original image stays on your device and the new file has no source EXIF or GPS segment at all. For HEIC originals, convert to JPG first, then strip — that combination preserves the pixel quality while leaving nothing behind in the metadata.