Inspect the file you actually plan to share
Use Image Metadata Viewer on the intended sharing file, not just another photo from the same phone. Available camera, date, exposure, lens, ownership or GPS fields can differ from one file to another. A screenshot or forwarded copy may already have lost some tags.
Absence of a field means it was not found in the supported inspection, not that the image has been independently proven private or authentic. Metadata can be edited or stripped. Avoid using a missing camera label as evidence that a picture is artificial.
Make a separate metadata-reduced copy
Remove Image Metadata re-encodes the selected image. Save that output as a new copy and retain the original when it has archival or evidentiary value. Re-encoding can change image pixels and file size, so it is not a metadata-only archival transformation.
Choose an output format appropriate to the content. A transparent logo requires an output that can retain transparency. If you use JPG for a photograph, inspect its quality as well as the metadata result. The sharing copy should meet both privacy and presentation requirements.
Verify the exported output
Reopen the downloaded copy in Image Metadata Viewer and check the fields you wanted to remove. Do not assume that the operation removed every field in every file type or that an in-browser preview proves the exported file has the same metadata state.
If you need a readable record, the viewer can generate a PDF summary. Review its thumbnail and available fields before sharing that report. The PDF itself can contain sensitive information copied from the input, so it deserves the same care as the photograph.
Examine visible details and filenames
Metadata removal cannot hide an address on an envelope, a school badge, a reflected face, a vehicle plate or a recognizable room. Review the scene and filename as well. A date or person’s name embedded in a filename can reveal information even when EXIF fields are absent.
Whole-image blur or pixelation is not a guaranteed sensitive-data redaction system. For an important privacy decision, use a suitable workflow that removes the information you intend to conceal and verify the final copy. Do not rely on a decorative effect without checking what remains recognizable.
Understand browser processing accurately
The image-editing operation is local, but the website and processing assets still load through a connection. Hosting can receive normal request information, and any enabled advertising service can have separate data handling. These are different questions from whether photo pixels are uploaded for a particular operation.
Connected forensic detection is a separate workflow and can send a selected image to a configured service. Read the per-tool processing notes instead of applying a blanket claim to the whole site. Keep private originals in a location you control and share only the copy you have reviewed.
Reopen the exported file and check GPS
Select the downloaded sharing copy in Image Metadata Viewer, rather than checking the original again. Review readable GPS, camera and descriptive fields. Re-encoding can remove embedded records, but a viewer only reports what it can parse from that particular export.
Then inspect the filename, visible signs, reflections, faces and documents in the image. Removing EXIF is not anonymization and does not make AI-generated content undetectable. It addresses one category of information inside the file.
