Set a clear goal before making a copy
Write down the requirements: a maximum upload size, a pixel width, a supported format or the removal of sensitive coordinates. These are different tasks. A smaller file may still contain GPS; a file without readable camera fields may still be too large. Keep your original as a backup and use a separate working copy for each export.
Try the generated example first
Open Image Comparison and run the example button. The browser creates a simple 1200 × 900 PNG and a 640 × 480 JPG. The originals contain 1,080,000 and 307,200 pixels respectively, so the JPG retains 28.44% of the first image’s pixels. File bytes vary with the browser encoder, and both examples are generated images rather than photographs with EXIF. This example tests dimensions and format changes, not location removal.
Compare your real original and exported file
Select the original in slot A and your downloaded copy in slot B. Inspect dimensions, megapixels and actual bytes before the camera, capture-date and GPS rows. A negative byte percentage means B occupies less storage; a negative pixel percentage means fewer pixels remain. These measurements do not assess whether text or faces are still sharp. Look at the previews and inspect the output at its intended display size.
Check privacy without overreading the result
If supported GPS fields are detected in A but not in B, the readable fields differ in those copies. That is useful evidence about your export, but not a certificate that all possible XMP, IPTC, maker notes or other copies are empty. A filename, visible street sign or reflection may still be sensitive. Repeat the check on the received copy if a messaging or cloud workflow creates another file.
Keep a report only when it is useful
The JSON download records filenames, dimensions, bytes and parsed metadata so you can review your workflow later. It is created on your device and may itself contain capture details or coordinates. Do not publish it by default. Review the report, keep only what you need and preserve the original if its camera information or color characteristics matter.
What a metadata result can and cannot prove
ImageMetaCheck reads supported metadata fields from the file you select, inside your browser. An absent EXIF or GPS result means those fields were not detected in this copy; it is not proof that every original, backup, XMP field or proprietary camera field is empty. Metadata can be edited and does not establish image authenticity. Compare the original and the final exported file when privacy or capture details matter.