Inspect

Looking inside a file

Half of all media trouble is solved by finding out what you actually have. Media info reads the container, the video and audio codecs, resolution, frame rate, bitrate, duration and channel layout straight out of the file, which is usually enough to explain why something will not play, why it is enormous, or why it went silent after a conversion. Compare videos and compare images put two files side by side with their numbers, which is the honest way to check whether a conversion actually cost you anything.

What your files are telling everyone else

Photographs and videos carry metadata you did not choose to write. A picture from a phone typically holds the exact GPS coordinates where it was taken, the timestamp, the device model and serial, and sometimes the owner's name. Video files carry creation dates, device information and encoder strings. None of it is visible when you look at the picture, and all of it travels with the file when you post it, email it or send it to a client. View metadata shows you what is in there; remove metadata strips it without re-encoding, so the picture itself is untouched.

The point of doing this locally

Checking a file for hidden location data by uploading it to a website is self-defeating: you have just given away the thing you were trying to control, plus your IP address, to find out that it existed. These tools read the file in the tab and nothing leaves the device, which is the only arrangement in which the answer is worth having.

The two model-based checkers

The explicit content check and the age estimate run vision models locally to give you a rough, private read on a picture before you use it somewhere. Both are approximate, both have real error rates, and neither is fit to be used as a moderation decision or as any kind of verification about a real person. They are a sanity check on your own files, and that is the whole of their claim.