drag & drop, click, or paste from clipboard

Drop to add

Remove EXIF data and GPS location — surgical byte strip, zero quality loss

Your photos carry a hidden passenger. Every smartphone and camera embeds a block of metadata — EXIF — alongside the pixel data. It records the GPS coordinates where the shutter fired, the device make and model, the lens and focal length, shutter speed, ISO, timestamps down to the second, and sometimes the owner name or copyright string from your camera settings. Share that file and you share all of it. Publish it online and crawlers index it.

This tool removes the metadata at the byte level without touching the image pixels at all. The approach matters: tools that strip EXIF by re-encoding the photo destroy a small but real amount of quality on every pass, and slow down on large files. Direct byte editing is instantaneous on JPEGs, lossless by definition, and produces a result indistinguishable — pixel for pixel — from the original. You also have the option to retain the ICC color profile, the one metadata block worth keeping for accurate color in professional workflows.

What GPS in a photo actually reveals

The EXIF GPS block stores latitude, longitude, and often altitude with sub-meter accuracy — precise enough to identify a home address, a school, a clinic, or any other location the photographer would prefer to keep private. Smartphones write this automatically unless location services are explicitly disabled for the camera app, and many people never check.

When photos are uploaded to websites, sent to clients, posted to social media before the platform strips metadata, or shared via messaging apps that preserve the original file, GPS data travels with them. Some file-hosting services and email clients display a map pin pulled directly from EXIF. A photo that looks like an innocuous selfie may contain a precise history of where you live, work, and spend time.

Removing EXIF before sharing is the cleanest fix. There is no need to disable location services globally — shoot with location data for your own archive (geotagging is useful), strip it selectively before any photo leaves your device.

Why re-encoding matters — and why this tool avoids it

JPEG compression is lossy. Every time a JPEG is decoded and re-encoded — even at 95% quality — fine detail in smooth gradients, thin lines, and high-frequency textures is permanently degraded. Run the same file through five encode cycles and the damage compounds visibly. Many metadata-stripping tools work by loading the full image into a decoder and saving it back out, which triggers exactly this quality cost whether or not the documentation mentions it.

Enhydra RPO strips EXIF by editing the marker segments in the raw file bytes directly. The compressed image data — the part that produces the picture — is never decoded, never touched, and never recompressed. The output file is smaller by a few kilobytes (the metadata that was removed) and otherwise byte-identical to the input. For PNGs, the same logic applies to tEXt and iTXt chunks. This is measurably different from re-encoding, and for professionals delivering final assets to clients it is the only acceptable approach.

The ICC profile: the one block worth keeping

An ICC color profile is a small mathematical description of the color space the image was captured or edited in — sRGB, Adobe RGB, Display P3, ProPhoto RGB, and so on. Applications that respect color management use it to render the image accurately on screen and send it correctly to printers. Without it, color-managed apps fall back to assuming sRGB, which can shift hues and saturation noticeably in images shot or edited in a wide-gamut space.

The tool exposes a toggle to preserve the ICC profile while stripping everything else. GPS, camera model, lens data, timestamps, XMP tags, maker notes, and any embedded comments are removed. The color profile stays. For work that will be printed, displayed on wide-gamut monitors, or passed to a designer, keeping the profile is the right default. For web publishing where file size matters more than color precision, removing everything is fine — browsers use sRGB for untagged images.

FAQ

Does stripping EXIF make photos smaller?

Yes, slightly. EXIF blocks on typical smartphone photos run 20–80 KB. The pixel data is untouched, so the reduction is exactly equal to the metadata that was removed. Visible file size change is small but real.

Does this work on RAW files like CR2, NEF, or DNG?

Accepted input formats include CR2, NEF, ARW, and DNG among others. Metadata stripping on RAW files edits the EXIF segments without altering the raw sensor data. The output format depends on what you select — RAW-in does not imply RAW-out if you also convert.

Can I strip EXIF and compress in the same run?

Yes. Stack both tools together. Because compression involves a full re-encode anyway, the direct-byte EXIF stripping is folded into the same single encode pass — no double-processing penalty.

What about XMP metadata written by Lightroom or other editors?

XMP blocks — which store editing history, keywords, ratings, and copyright strings written by photo editors — are stripped along with EXIF and GPS data. The pixel result from your last edit is preserved; the editing record is removed.

Is there any metadata that stays even without the ICC toggle?

When the ICC toggle is off, the tool removes all metadata segments. Nothing is preserved by default. If downstream color accuracy matters, switch the toggle on — the profile adds only a few hundred bytes to the file.