How to Remove EXIF and GPS Metadata Before Sharing a Photo

A JPEG can contain GPS coordinates, capture times, camera and lens details,
editing software, comments, and copyright fields. That may be useful in a
private archive, but risky in a public issue, marketplace listing, or social
post.

Do not assume the upload destination will remove it. Platforms process formats
differently and can change behavior. Create a clean public copy before the file
leaves your control.

Inspect a sharing copy

Keep the original private. On a separate copy, check for GPS data, timestamps,
camera identifiers, and EXIF, XMP, or IPTC fields. The goal is not to damage
your archive; it is to make a public file containing only what the destination
needs.

A practical workflow is:

1. Inspect the sharing copy locally.
2. Export a cleaned file.
3. Inspect that exact output again.
4. Review what is visible in the pixels.
5. Rename it clearly before uploading.

The MonoTools EXIF Inspector & Cleaner does this in the current browser tab.
The selected photo is read through browser APIs and is not uploaded to a
processing server.

Understand the JPEG boundary

JPEG stores metadata in segments around its compressed image data. The cleaner
can remove those segments without recompressing the pixels. It currently
removes APP1 EXIF and XMP, APP2 ICC profiles, APP13 Photoshop and IPTC data,
and JPEG comments when present.

Removing an ICC profile can change color rendering in managed workflows, so
compare the cleaned copy with the original when color accuracy matters.

The cleaned export currently supports JPEG only. PNG and WebP use different
container structures; the tool can inspect them but does not yet rewrite their
metadata.

Check the pixels too

Metadata removal cannot hide information already visible in a photo. Look for
street signs, faces, badges, vehicle plates, screens, shipping labels, QR
codes, landmarks, and reflections. Cropping, blurring, or replacing the image
may still be necessary.

If the public copy also needs resizing or format conversion, do that after the
privacy review, then inspect the final file again. Compression and metadata
cleanup solve different problems.

I maintain MonoTools and wrote a fuller guide for its browser-local EXIF
Inspector & Cleaner:

https://monoware.app/guides/remove-exif-metadata-before-sharing?utm_source=devto&utm_medium=content&utm_campaign=exif_cleanup_guide

Disclosure: MonoTools is my project.

Comments

[Mustafa ERBAY]

Great reminder. One thing I’d add is that metadata removal should be treated as just one layer of privacy protection. Even a perfectly cleaned image can still reveal sensitive information through what’s visible in the pixels—reflections, unique landmarks, badges, screens, or shipping labels are often enough for OSINT investigations. Metadata is easy to strip; contextual information is usually the harder privacy leak to eliminate.