WEBP Metadata Viewer

A photo is never only pixels. Alongside the image itself, most files carry a surprising amount of recorded context: when the picture was taken, which camera and lens produced it, what exposure settings were used, which colour profile the file was tagged with, whether a caption or credit was embedded, and in many cases exactly where in the world the shutter was pressed. All of that travels inside the file, invisible in the preview, and it follows the image wherever the image goes.

That matters for two opposite reasons, and both are practical. On one side, the metadata is often the answer to a real question: which of these three nearly identical product shots is the newer one, what profile should the print shop be told to expect, or who owns the copyright line embedded in a supplied photograph. On the other side, the same data is frequently the reason a file should not be published as it stands, because coordinates recorded by a phone can reveal a home address, and a client’s internal software tag is nobody else’s business.

This viewer surfaces the whole set rather than a subset. File level information covers the container type, the declared MIME type and the weight. Image level information is read out of the bytes themselves and includes bit depth, colour component layout, chroma subsampling and encoding process, which is the sort of detail that explains why one export behaves differently from another in a colour managed workflow.

Photographic metadata is grouped by where it lives. EXIF carries the camera record and the timestamps, GPS carries the position, IPTC carries captions, keywords and credit lines, XMP carries the editable structured description that editing software writes, and the ICC profile describes how colours should be interpreted. Showing them separately makes it obvious which application wrote which part, which is usually the fastest route to understanding why a file behaves as it does.

WEBP is handled natively rather than approximated. The container is parsed directly, reading the lossy and lossless payload chunks to recover true dimensions, bit depth and colour layout, so the report is accurate for WEBP even when a general purpose EXIF library would find nothing at all. That is the difference between a viewer that works on modern web formats and one that quietly returns an empty result.

Reading happens entirely on your own machine. The file is parsed in the browser, the extended EXIF parser is fetched from a public content delivery network the first time it is needed, and if that fetch fails the tool still reports the file and basic image information rather than giving up. Nothing is uploaded, and the report can be taken away as plain text or as a complete JSON file for your own records.