EXIF data is the structured metadata block that cameras, phones, and editing apps store inside the APP1 segment of a JPEG file, recording camera make and model, exposure settings, lens details, capture timestamps, and — when location is enabled — GPS latitude and longitude. A local EXIF viewer reads those bytes inside the current browser tab to surface them in a plain table, parsing the TIFF header, the IFD0 directory, the Exif subdirectory, and the GPS subdirectory in order, following the published specification maintained by CIPA. Because every step happens on your machine rather than on a remote server, the original image and any decoded values stay on your device and the file is never written back or modified. The viewer recognizes a bounded tag allowlist that includes the fields listed above plus orientation, software, pixel dimensions, focal length, and ISO, while proprietary maker notes are deliberately ignored rather than guessed, so unrecognized tags simply do not appear in the result. Files up to 25 MiB are accepted in one pass, and out-of-range offsets, malformed directory lengths, and unsupported field counts are rejected before any value is shown.
What EXIF Data Actually Contains
EXIF stands for Exchangeable Image File Format, and it is a standardized block of structured metadata that cameras, smartphones, and editing software write into a JPEG file at capture or save time. The block sits inside the same file as the compressed picture, in a section called the APP1 segment, immediately after the two-byte start-of-image marker. Because EXIF follows a published specification maintained by CIPA — the camera industry's standards body — the same fields can be decoded by different tools and operating systems in a consistent way.
A typical file might store the make and model of the camera, the lens model, the exposure time, the f-number, the ISO speed, the focal length, the pixel dimensions, the orientation, the original capture timestamp, the software that last modified the image, and GPS latitude and longitude when location services were on at capture. Editing apps, messaging platforms, and social networks routinely strip, replace, or normalize parts of this block, which is why the same picture can show different metadata on different devices. A useful habit is to view the file on the device that produced it, before any platform has had a chance to touch the bytes.
Why a Local, No-Upload Viewer Matters
EXIF fields often include sensitive details — most notably the precise GPS coordinates of where a photo was taken, but also the make of a security camera or the timestamp on a printed document. Sending the original file to a remote web service for inspection means trusting that service with both the pixels and the metadata until the upload finishes and the response returns. A viewer that runs entirely in the browser keeps the bytes in the current tab, parses the APP1 segment locally, and shows the result on the same machine that opened the file. Nothing leaves the device, no account is required, and the original JPEG is never written back or modified. For a single one-off check this is the most privacy-respecting way to inspect what a file is carrying, and it is also the safest way to look at a photo you received before deciding whether to keep or forward it.
View EXIF Data in Three Steps
- Open the EXIF Viewer in your browser, click the file picker, and select a local JPG or JPEG. The viewer accepts files up to 25 MiB and refuses anything outside that limit.
- Wait while the tool locates the first valid Exif APP1 segment in the JPEG, validates the TIFF header and byte order, then walks through the bounded IFD0, Exif, and GPS directories to decode every recognized tag from its documented allowlist.
- Read the resulting table. Common rows include camera make, camera model, software, orientation, exposure time, f-number, ISO, focal length, lens model, pixel dimensions, original capture time, modified time, and — when present — GPS latitude and longitude. If no rows appear, the file has no Exif segment, has had its metadata stripped, or contains only unsupported proprietary fields.
Independent safety checks run before any value is displayed, so a malformed segment, an out-of-file offset, a directory with too many entries, or an oversized field count causes the parse to stop with the table left empty rather than producing a wrong value.
Common EXIF Fields You May See
The viewer decodes only tags from a documented allowlist that is cross-checked against the official ExifTool tag names list. The fields below come from the CIPA Exif 2.3 specification, which defines the segment layout the parser follows. A given file may contain none, some, or all of these fields, since apps and platforms routinely strip entire categories such as GPS or timestamps.
| Group | Field | What it tells you |
|---|---|---|
| Camera | Make and model | The manufacturer label and product name written into the file by the device. |
| Capture | Exposure time, f-number, ISO | The shutter speed, aperture, and sensor sensitivity used when the picture was taken. |
| Capture | Focal length, lens model | The lens focal length in millimetres and the lens product name reported by the camera. |
| Image | Pixel dimensions and orientation | The image width and height in pixels, plus a rotation flag a downstream viewer should apply. |
| Time | Original and modified date/time | Two timestamps inside Exif: when the picture was captured and when the file was last saved. |
| GPS | Latitude, longitude, hemisphere | The location in degrees, minutes, and seconds, plus N/S and E/W references that fix the sign of the value. |
| Software | Software field | The name of the program or firmware string that produced the segment. |
Coordinates are converted from degrees, minutes, and seconds into signed decimal degrees using the stored N/S and E/W references, so a positive value is north of the equator or east of the prime meridian and a negative value is south or west. Orientation is shown with a plain label in addition to the numeric flag, so a row that reads "Rotate 90° CW" is clearer than the raw numeric value.
GPS Coordinates and Privacy Before You Share
The most sensitive row in the table is usually the GPS block. When a phone or camera has location services enabled at capture and embedding is not disabled, the resulting JPEG can carry coordinates accurate to a few meters, plus the cardinal reference that fixes the sign of the value. Anyone who receives the file can recover the spot where it was taken. The viewer shows a clear location warning for exactly this reason, and you should review the GPS row of every picture before you post it online, attach it to an email, upload it to a cloud drive, or hand it to a third party. The same logic applies to the camera make and model on security footage and to the original timestamps on documents where the capture date is confidential. If you want to keep the image but drop the sensitive fields, follow a no-upload stripping workflow such as the browser-based EXIF stripping guide to remove the GPS block without re-encoding the pixels.
When a Desktop Metadata Tool Is the Better Choice
The viewer targets one job: surfacing standard EXIF tags from a single JPEG in a browser, without sending the file anywhere. Several real workflows fall outside that scope and need a maintained desktop tool. Working with RAW files from a mirrorless or DSLR camera, inspecting HEIC images from an iPhone, parsing XMP or IPTC sidecars, viewing proprietary maker notes such as Canon's lens data or Nikon's scene detection, batch-processing hundreds of files, or producing a complete export of every tag for a forensic report all sit beyond what a browser-based JPEG viewer can offer. ExifTool is the most widely cited reference implementation for those jobs, and its tag tables are the basis used to cross-check the values shown here.
Treat the local result as a quick read of the common tags, not a substitute for an authoritative metadata inventory. Metadata is never proof of authorship, ownership, capture time, location, or authenticity: fields can be missing, stale, edited, copied from another file, or stripped entirely by a messaging platform, so do not rely on them for evidence without corroboration from the original file and a trusted desktop tool. The parsing rules follow the CIPA Exif specification, with little-endian and big-endian byte order, inline and offset values, ASCII, SHORT, LONG, RATIONAL, signed values, and the GPS subdirectory all decoded from a documented allowlist. Eight standard fixtures pin the core tag identifiers and types, so the viewer rejects malformed segment lengths, directories with excessive entries, unsupported field counts, and offsets that point outside the selected file before showing any value to the reader.