EXIF is the structured metadata block that cameras and phones write into a JPEG at the moment of capture, and a browser-based EXIF viewer decodes that block into a plain table without sending the image to a server. The acronym stands for Exchangeable Image File Format, a standard maintained by the Camera & Imaging Products Association (CIPA) and documented in their published specification. For a beginner, EXIF is best understood as the hidden paperwork inside every photo: it travels with the file, usually survives most edits, and quietly records what the device was, when the shutter fired, how the lens was set, and — if location services were enabled — where the picture was taken. None of that is visible when you simply open the image; it only appears once a tool parses the APP1 segment inside the JPEG. The goal for a first-time reader is not to memorise every tag, but to recognise which rows matter, what each row means in plain English, and which rows reveal information the photo owner may not have intended to share.
What EXIF Data Actually Is (and Why It Lives in Your JPEG)
A JPEG is more than a grid of pixels. The file is laid out in a series of segments, each introduced by a two-byte marker. Most of the file stores the compressed image data, but several segments store descriptive information instead. EXIF lives in the APP1 segment, which sits near the top of the file, just after the Start Of Image marker. Inside that segment is a small TIFF header followed by a directory of tagged fields. Each field is a four-character ID, a type, a count, and a value (either inline or stored at an offset elsewhere in the segment). The directory may point to a second Exif subdirectory and a third GPS subdirectory, which is how the camera's settings and the location data end up nested inside one block.
Because the structure is standardised, any well-written viewer can walk those directories the same way. The EXIF Viewer does exactly that: it reads the bytes in your current browser tab, validates the TIFF header, follows the bounded IFD0, Exif, and GPS directories, decodes only a documented allowlist of common tags, and displays the result as a table. Nothing is uploaded, nothing is mutated, and proprietary maker notes are intentionally ignored rather than guessed.
Common EXIF Fields Explained for First-Time Readers
When you open a JPEG in a beginner-friendly EXIF viewer, the table you see is the decoded contents of that APP1 block. Each row is one field. The table below explains the entries a beginner is most likely to encounter, in plain English, with a typical example value for each.
| Field | Plain-English meaning | Typical example |
|---|---|---|
| Make | Manufacturer of the camera or phone | Apple, Canon, Sony |
| Model | Specific device model | iPhone 15, EOS R5 |
| Orientation | How the image should be rotated for display | 1 (normal), 6 (rotated 90° clockwise) |
| Software | Firmware, operating system, or app that wrote the file | iOS 17.4, Adobe Lightroom |
| DateTimeOriginal | When the shutter was pressed | 2024:08:14 16:42:11 |
| DateTime | When the file was last modified or saved | 2024:08:14 16:42:11 |
| ExposureTime | Shutter speed, in seconds | 0.005 (= 1/200 s) |
| FNumber | Aperture, the f-stop | 2.8 |
| ISO | Sensor sensitivity setting | 200 |
| FocalLength | Lens focal length in millimetres | 50 |
| LensModel | Name of the lens that was attached | EF 50mm f/1.8 STM |
| PixelXDimension | Image width in pixels | 4032 |
| PixelYDimension | Image height in pixels | 3024 |
| GPSLatitude | Latitude in degrees, minutes, and seconds | 40° 30' 0" |
| GPSLongitude | Longitude in degrees, minutes, and seconds | 79° 0' 0" |
Not every photo will have every row. A screenshot taken in a chat app, a photo cropped and re-saved by a social network, or an image downloaded from a stock-photo site may carry no EXIF block at all, or only a handful of fields. Treat missing rows as normal, not as an error.
How to View EXIF Data with a Browser Tool
For a first inspection, the EXIF Viewer reads common metadata fields from a local JPEG inside the current browser tab. The whole process runs locally; the photo is not sent anywhere.
- Choose a local JPG or JPEG file up to 25 MiB using the file picker on the tool page.
- Wait a moment for the table to populate with the recognised EXIF rows from the file.
- Scan the rows for camera info, capture time, exposure settings, lens, and pixel dimensions.
- Look specifically for any GPS latitude and longitude rows, since these reveal where the photo was taken.
- Compare Make, Model, DateTimeOriginal, and Software against what you remember, to spot edited or copied metadata.
- If you only need a quick read, screenshot or copy the table; if you need to act on the data or work with other formats, move on to a full desktop tool.
The viewer stops at the first valid Exif APP1 segment, rejects malformed segment lengths and offsets that point outside the file, and never executes anything stored in the metadata. The bytes and parsed values stay in your browser tab for the duration of the session.
Reading GPS Coordinates Without Oversharing
GPS rows are the most sensitive part of an EXIF block. If the camera had location services on, the JPEG may contain latitude and longitude accurate to a few metres. The values are stored as three numbers — degrees, minutes, and seconds — plus a hemisphere reference letter (N, S, E, or W). A beginner-friendly viewer converts them into signed decimal degrees, the form a map can read, using the formula:
Decimal = Degrees + Minutes ÷ 60 + Seconds ÷ 3600
For a southern or western coordinate, negate the result. As a single worked example, take a stored value of 40° 30' 0" N and 79° 0' 0" W. The latitude works out to 40 + 30 ÷ 60 + 0 ÷ 3600, which is 40 + 0.5 + 0, giving 40.5. The longitude works out to 79 + 0 ÷ 60 + 0 ÷ 3600, which is 79 + 0 + 0, giving 79. The hemisphere reference marks W as west, so the longitude becomes −79.0. The final signed decimal degrees are 40.5, −79.0.
Because GPS can pinpoint the place a photo was taken, scan the table before you share the image or the parsed report. If you do not need the location, strip it from the file before posting — the EXIF Remover alternative guide walks through a no-upload workflow that rebuilds a JPEG from its decoded pixels.
What a Beginner-Friendly EXIF Viewer Will Not Show You
A bounded viewer is scoped on purpose. The fields you see are the documented common tags: camera make and model, orientation, software, original and modified capture times, exposure time, f-number, ISO, focal length, pixel dimensions, lens model, and GPS coordinates when present. Anything outside this allowlist is intentionally ignored rather than guessed, which means several categories stay hidden.
Proprietary maker notes are the biggest one. Each manufacturer packs vendor-specific data into the EXIF block — autofocus positions, lens corrections, noise tables, scene-detection hints. A bounded viewer skips these to avoid misreading them. XMP and IPTC sidecars are a second category: modern editing software writes its own metadata blocks alongside EXIF, and the viewer reads only the Exif APP1 segment. Other formats are a third: HEIC, PNG, WebP, RAW, and video containers use different metadata rules, and a JPEG-only viewer will not parse them.
This is a scope decision, not a shortcoming. The viewer cross-checks its tag table against ExifTool's official list and rejects malformed segments, oversized directory counts, and offsets that point outside the selected file, which is why a single safe tool can read several different cameras' files without crashing or guessing.
When to Reach for a Desktop Tool Instead
Use a browser EXIF viewer when the question is small: "What camera took this?", "What's the ISO?", "Where was this photo taken?" Use a maintained desktop tool such as ExifTool when the question is bigger. You will want a desktop tool if you need the full metadata inventory including maker notes; if you are working with RAW, HEIC, video, or PDF files rather than JPEG; if you need batch export across hundreds of files; if the result will be used as forensic evidence where complete provenance matters; or if you need to preserve the original bytes for a chain-of-custody record.
One caution deserves emphasis. EXIF is not proof. The values can be edited, copied, made stale, or removed by messaging and social platforms. A photo carrying a 2024 timestamp is not necessarily from 2024; a photo with no GPS is not necessarily location-less. Treat metadata as a hint, not as a verdict, and reach for a desktop tool whenever the answer has to hold up under scrutiny.
For a deeper look, see Compress Image for Beginners: A Plain English Guide.