Remove EXIF metadata from a photo

Protect location and device details before sharing images. FileGizmo reads JPG, PNG and WebP metadata, shows a row for every file, and hands back cleaned copies without recompressing the picture.

Phones and cameras can attach capture time, device model, lens settings, software details, orientation, and precise GPS coordinates to a JPEG. Those fields are not normally visible in the picture, yet a recipient or platform may be able to read them. GPS data can reveal a home, workplace, school, or travel location. Removing the metadata is a sensible step before publishing an original photo when that context should remain private.

The tool first inspects up to 20 images. The table shows file format, camera, capture date, whether a supported GPS field is present, editing software and the metadata blocks found. A missing value is labelled Not found rather than guessed. Removal then walks the file structure and copies every safe image chunk without decoding the pixels. File size may fall when metadata is present, but size reduction is not the purpose.

Metadata lives in more than one place. In JPG, photo editors, phone galleries and drones can write coordinates into XMP, news tools use IPTC, and camera makers use application blocks. Some phones append another picture or Motion Photo video after the JPEG. PNG uses eXIf, tEXt, iTXt and compressed zTXt chunks. WebP carries EXIF and XMP chunks inside its RIFF container. The cleaner removes those supported containers and fixes the WebP RIFF size after the chunks are gone.

Orientation is handled for you. Most phones store a portrait photo sideways and record the turn in an EXIF tag. When that tag is present, the cleaned copy keeps a 36-byte EXIF block holding only the orientation, so the photo opens the right way up and says nothing else about where or how it was taken.

Many social networks and messaging services modify metadata, but their behavior can change and may differ between original-file and compressed-photo sharing. Do not depend on an undocumented platform policy for sensitive material. Clean the copy yourself, download it, and inspect that final file with a metadata viewer when the consequences matter.

Inspection and stripping occur inside a local worker. No photo upload is needed. A single image downloads in its original format; several cleaned images download together as a ZIP. HEIC, AVIF, video, RAW files and separate sidecars are not accepted by this workflow.

Use a neutral filename for the cleaned copy if the original name itself reveals a person, case number, address, or event. Then share that copy rather than the source selected from the camera roll. The tool cannot control backups, earlier uploads, message previews, or copies already synchronized elsewhere, so metadata removal is most effective before the first distribution.

For high-risk publishing, inspect the cleaned download with a second trusted metadata viewer and consider whether the visible scene needs cropping or redaction. A “No metadata block detected” result answers a narrow technical question. It does not certify that the photograph is anonymous or safe to publish, because a street sign, a reflection or a face can say as much as a GPS tag.

The downloaded copy keeps the original JPEG image data, so visual comparisons match. Record the cleanup step when a newsroom, research project, or organizational policy requires a reproducible handling process. Local removal reduces unnecessary disclosure without pretending that the file is the whole privacy review.