Image metadata and EXIF viewer

An EXIF viewer should show the fields before you share

A photo can carry much more than its visible pixels. Camera and lens names, capture date, software, copyright text, a device serial number, an embedded thumbnail, and GPS coordinates may travel with a JPEG. PNG and WebP can also contain metadata blocks, so changing an extension or taking a screenshot is not a dependable privacy check.

This viewer reads the file signature and container structure locally. It does not infer the format from the filename. The result separates dimensions and file size from container blocks and named EXIF fields, and shows the numeric tag for each decoded value. Unknown manufacturer data is reported by size rather than presented as text the parser cannot honestly interpret.

Two dimensions, because a rotated photo has two

A JPEG from a phone held sideways usually stores its pixels in landscape and adds an EXIF Orientation tag saying which quarter turn to apply. Values 5 through 8 include that turn, so the header can read 600 × 400 while every viewer, browser, and upload form treats the image as 400 × 600. Neither number is wrong; they answer different questions.

When those two readings differ, the result shows both: Dimensions is what you see after orientation is applied, and Stored in header is the pair written into the container. A file with no orientation tag, or with a value that only mirrors or half-turns the image, has one pair and shows one. If you only need the numbers and the aspect ratio, image dimensions answers that question on its own page.

A metadata viewer is different from a remover

This route is deliberately read-only. Opening a file creates no replacement and changes no byte. If the result shows details you do not want to publish, use the EXIF remover to create a cleaned JPEG, PNG, or WebP copy. Keeping inspection and removal as distinct jobs makes it clear whether anything has been written.

The block list also distinguishes structural image data from descriptive metadata. An ICC color profile affects how colors are interpreted and is not the same kind of information as a GPS coordinate. An EXIF orientation value can affect how untouched pixels are displayed. The viewer reports both without calling every invisible block disposable.

Supported formats have an explicit boundary

The verified reader covers JPEG, PNG, and WebP. It follows the EXIF IFDs used for common camera, capture, authoring, location, orientation, and thumbnail fields. It does not claim general MakerNote decoding, and it does not guess at HEIC, AVIF, GIF, bare TIFF, PSD, or PSB structures. A clear unsupported result is safer than displaying plausible but misaddressed bytes. An iPhone HEIC photo can become a JPEG with HEIC to JPG first, which removes location data by default, so the copy you inspect here reflects that choice rather than the original file. If the immediate job is to extract the visible pixels from one explicit TIFF page, use TIFF to PNG. To inspect a Photoshop document’s layer inventory and verified embedded composite instead, use the PSD viewer. Neither converter turns this route into a general metadata reader.

Everything happens in this browser tab. The filename, image bytes, coordinates, and decoded values are not placed in the URL, browser storage, analytics, or a remote API. The local-processing guide explains how to check that network boundary yourself.