File Metadata Viewer & Editor

beta

Read every piece of metadata any file carries — and add or change it: set a GPS location on a photo, video or audio, then save in place or to a copy

How it works

Drop in any file and the viewer reads it entirely in your browser — nothing is uploaded. Every file first gets the basics: its real type detected from the leading bytes (the magic number, so a mislabelled extension is caught), exact size, last-modified time and a SHA-256 fingerprint. Then it decodes whatever metadata the format carries. For photos it walks the full EXIF: camera make and model, lens, exposure, every date, orientation, and the GPS sub-IFD turned into real decimal coordinates with an OpenStreetMap link so you can see exactly where a picture was taken — plus XMP and IPTC. For MP4, MOV, M4A and HEIC it reads the ISO-BMFF box tree: brand, duration, creation and modification time, each track's type and dimensions, the iTunes-style ©-atom tags, and Apple's ISO-6709 location. MP3 files give their ID3v2 frames, WAV and AVI their RIFF INFO, and PDFs their document information dictionary (author, creator, producer, dates, page size) and XMP packet via pdf.js. Across every container it also reads AI-provenance signals — C2PA Content Credentials, IPTC digital-source-type declarations like trainedAlgorithmicMedia, and generator fingerprints from tools such as Stable Diffusion, Midjourney, Firefly, DALL·E and Google — and says plainly when none are present, because absence is not proof a file is human-made. Copy any field, copy the whole report as JSON, or download it. There is no size limit: only the region that holds the metadata is read (a multi-gigabyte video is never loaded whole — just its moov atom), and the SHA-256 is streamed over the whole file. Beyond reading, it edits: an Edit panel offers the fields the file's format carries and, above all, a Location (GPS) editor — type coordinates or use your device's location, see them on a map, and write them back the standard way each format expects, so Photos, Google Photos and the like read them: EXIF GPS for JPEG, PNG and WebP, and the QuickTime udta ©xyz / ISO-6709 tag for MP4, MOV and M4A. It also sets titles, author/artist, description, camera make and model and dates, and can remove a location. Editing preserves everything else the file already had — a photo's camera EXIF, a video's media — so adding a location never re-encodes the picture. Save over the original (open the file through the picker to allow that; a video with its moov at the end rewrites only the small moov, in seconds, whatever its size) or save a copy. For cryptographic C2PA validation and trust-list checking, the Content Credentials inspector goes deeper.

Questions

Can it show where a photo was taken?

Yes, when the photo still carries its GPS EXIF tags. The viewer decodes the latitude, longitude and altitude to decimal degrees and gives a one-click OpenStreetMap link. Many photos have no location — cameras can be set not to record it, and most social platforms strip it on upload — in which case there is simply nothing to show.

Which file types does it support?

Any file is accepted. It always identifies the type and shows size, dates and a SHA-256 hash. Rich metadata is decoded for JPEG, PNG, WebP, GIF, TIFF/DNG, HEIC/AVIF, MP4/MOV/M4A, MP3, WAV, AVI and PDF; for other types it shows the detected format and any text or identifiers found in the header.

Can it tell if a file was made by AI?

It reads the metadata that declares it — C2PA Content Credentials, IPTC 'trained algorithmic media' source types, and known generator names in the EXIF/XMP. A positive signal is meaningful; a missing one is not proof of anything, because these tags are easily stripped and invisible watermarks like Google's SynthID can't be read by any third-party tool.

Is my file uploaded anywhere?

No. Parsing, hashing and the PDF reader (pdf.js compiled from Mozilla's library, self-hosted) all run in your browser. The file never leaves your device; the only network request is the map link you choose to open.

How is the detected type different from the extension?

The viewer ignores the file name and reads the first bytes — the format's signature. So a .jpg that is really a PNG, or a file with no extension at all, is identified correctly, and a mismatch between the real type and the browser's reported type is flagged.

Can I add a GPS location to a photo, video or audio?

Yes. Load the file, open the Edit panel's Location box, type the latitude and longitude (and altitude if you like) or press Use my location, then save. It is written the standard way for that format — EXIF GPS for JPEG/PNG/WebP, the QuickTime ©xyz / ISO-6709 tag in moov/udta for MP4, MOV and M4A — so Apple Photos, Google Photos and other tools read it. MP3 has no portable GPS convention, so use an MP4/M4A file for location in audio. Everything else in the file is preserved; adding a location never re-encodes the picture or the video.

Can it remove or change metadata, and save back to the file?

Yes. The Edit panel changes the fields the format carries — location, title, author, description, make, model, dates — and Remove location strips a GPS fix. Save to the file overwrites the original (open the file through the picker, not drag-and-drop, so the browser grants write access), or Save a copy writes a new file. For a video whose moov atom sits at the end (as DJI and most cameras write), saving rewrites only that small atom, so even an 8K file saves in seconds. To strip all metadata from an image instead, re-encode it with the Image Converter.