There are a lot of metadata tools. The difference that matters most is not which
fields each one reads, it is where your file goes when you use it.
Every statement about another tool on these pages is a direct quote from its own
site, with a link and the date it was last checked. There are no adjectives about
them, and each page lists things that tool does which this one does not.
A photo metadata tool that offers both a client-side preview and a fuller server-side analysis.
What we claim, and how to check it
File bytes never leave your browser tab, on any page of this site. How to check: Open your browser's Network panel, drop a file in, and watch: no request carries it. The parsing code is downloaded to you and runs locally.
Coordinates leave only when a file has GPS and you ask for it to be looked up. How to check: A file with GPS shows a Look up this location button and sends nothing. Press it and it triggers one request to our /api/geocode, which asks OpenStreetMap for a place name, with the coordinates rounded to three decimal places (about 100 m) first. Leave it alone, or scan a file with no GPS, and no such request is made.
The AI summary is optional, and sends extracted text rather than the file. How to check: It only runs when you press the button, and the page says so before you do. The fields it sends are the ones already on screen; the file itself is never part of it.
We read many more formats than we can clean. How to check: The /formats page marks every format as either 'File Scan + File Stripping' or 'File Scan only'. Both counts are drawn from the same list the scanner uses.
We name the signer of a signature. We do not verify any signature. How to check: Search the code for crypto.subtle: there is none. Fields are labelled 'Certificate Validity Window' and 'Signed Attribute Time' rather than 'valid' or 'trusted'.