Image Metadata Viewer

The Image Metadata Viewer extracts EXIF data directly from JPEG files, entirely in the browser, by parsing the APP1 segment and walking the IFD0, Exif sub-IFD, and GPS IFD tables. Load an image through the upload zone or the Choose an image button and the tool displays file name, size, type, and pixel dimensions in the Image info card, with a preview thumbnail underneath. The EXIF metadata card lists every tag it can decode with a friendly name and a raw value — including camera make and model, lens information, exposure time, f-number, ISO, focal length, capture date, copyright, and device serial numbers; RATIONAL values are shown both as fractions and decimal approximations. If the image carries GPS data, a green GPS location found panel appears with the decimal latitude and longitude plus a link to view the coordinates on OpenStreetMap. Images re-saved by social platforms, or formats such as PNG and WebP that store no EXIF, trigger a clear warning instead of failing silently. Because the parser is a hand-written client-side reader rather than a remote service, every tag and value shown stays on your machine, which makes the viewer well suited to inspecting photos before publication so unwanted metadata can be spotted or stripped in advance.

1. 1

   Drag a JPEG onto the drop zone or click "Choose an image"; if the file type does not start with image/, a toast asks you to pick an image instead.

2. 2

   Wait for the "Reading…" spinner to finish, then check Image info for the file name, size, type, and width × height dimensions.

3. 3

   Scroll the EXIF metadata table to review tags with friendly names and values, including the fraction-and-decimal rendering of RATIONAL fields.

4. 4

   If GPS data was found, click "Open in OpenStreetMap" to drop a pin at the exact decimal coordinates.

5. 5

   Read the About EXIF card to understand which segments the parser walks and why re-saved images often show no data.

• Checking the camera make, model, and lens used for a shot before publishing it.
• Reviewing exactly which tags a photo carries so unwanted GPS or serial numbers can be stripped before sharing.
• Locating where a photo was taken via the GPS coordinates before deciding whether to publish it.
• Verifying a stock image by comparing EXIF capture timestamps and camera bodies.
• Documenting camera settings from a reference shot for an exposure or photography tutorial.
• Auditing an image library for metadata that a client wants removed from derivative work.

• Expect heavy EXIF loss after sharing — platforms like WhatsApp and Instagram re-encode and strip most metadata.
• Treat GPS tags as sensitive; coordinates from a photo taken at home expose the exact location.
• Remember the parser only reads JPEG files with an APP1 segment, so RAW, HEIC, and TIFF files are out of scope.
• Check tags such as BodySerialNumber and LensSerialNumber, which can identify a specific camera body or lens.
• Cross-check the browser-loaded Dimensions stat against ExifImageWidth and ExifImageHeight to spot resizing or cropping.
• Keep originals backed up since the viewer is read-only — metadata is never modified, only displayed.

• The ExifImageWidth and ExifImageHeight tags should match the Dimensions stat — large gaps suggest resizing or cropping.
• The ASCII rendering replaces control bytes with a dot, which keeps odd tag values readable in the table.
• Heavily edited photos or those passed through chat apps lose EXIF, so re-shoot or keep a RAW original when metadata matters.
• Use the OpenStreetMap link to double-check a coordinate before deciding whether a photo is safe to publish.