Device
Camera make and model, plus the software that processed the file. This is how a screenshot gets blamed on your phone — the fields survive most edits that do not re-encode the image.
Privacy tool
Every phone photo carries more than pixels: the camera model, the exact timestamps, and often the GPS coordinates where it was taken. Drop a file below to read its EXIF metadata, then download a metadata-free copy with one click if you plan to share it.
What the fields mean
Camera make and model, plus the software that processed the file. This is how a screenshot gets blamed on your phone — the fields survive most edits that do not re-encode the image.
"Date taken" records when the shutter fired, to the second, straight from the camera clock. Combined with GPS it reconstructs a precise timeline of where you were.
Location lives in a dedicated EXIF block. Phones write it whenever location services are on for the camera — which is the default on most. The tool flags GPS presence even when other fields are empty.
Many JPEGs carry a small preview image inside the metadata. Editors that rotate or crop the main pixels have historically left the original thumbnail untouched — a well-known source of leaked "deleted" content.
Why it matters
An EXIF block is a plain-text attachment to the image. Anyone who receives the file — a marketplace buyer, a Discord server, an email recipient — can read it with a right-click and a properties dialog, no special software required. The risky fields are the obvious ones: home addresses visible in GPS data, schedules visible in timestamps, workplaces visible in both.
Platforms are not a reliable safety net. Large social networks and messaging apps re-encode uploads and usually strip EXIF in the process, but that is a side effect of their pipeline, not a promise — and it does not apply to email attachments, cloud folder links, forum uploads, or any file you send directly. The safe habit is to strip metadata yourself before the file leaves your device.
What removal does here. For JPEG files the tool copies the original byte-for-byte and deletes only the metadata segments — EXIF, XMP, and comments — keeping the colour profile and image data untouched. The pixels are identical and no image quality is lost, which is why this works even on files you cannot afford to re-encode. PNG and WebP files normally carry no camera EXIF at all; when one does carry a metadata chunk, the report says so, but a lossless strip is only offered for JPEG.
For the full picture of what the site does and does not do with your files, read the privacy policy; for how metadata relates to file weight, see the image file size guide.
Questions
No. The file is read with browser APIs on your device: the metadata report and the clean copy are produced locally, and nothing is transmitted.
Not for JPEG. The clean copy is a byte-level edit: metadata segments are cut out and the compressed image data is copied verbatim, so decoding produces exactly the same pixels. No re-encoding happens.
PNG and WebP files almost never carry camera EXIF, and when they do carry metadata chunks, removing them losslessly is a different byte format for each container. The honest scope is JPEG — where the privacy risk actually lives — plus an accurate report for the other formats.
This page handles one file at a time. For batches, export through any FitMyPic tool: every export is re-encoded from pixels, so the downloaded results never contain EXIF in the first place.
Rarely useful ones. Screenshots are generated by software, so they lack camera and GPS fields, but they may still carry software names and timestamps — and those fields have identified people before.