How to Remove Metadata from Photos
Updated September 18, 2026
Every photo your phone takes carries a hidden second payload: metadata. Date, time, camera model, exposure settings, and very often the exact GPS coordinates where you stood. None of it is visible in the picture, all of it travels with the file, and most people share it without knowing.
This guide explains what is actually in there, when it matters, and how to remove it without degrading the image.
What is actually stored in an image file
Three standards account for almost everything you will find:
- EXIF — written by cameras and phones. Timestamp, make and model, lens, ISO, shutter speed, orientation, and GPS latitude/longitude when location services were on.
- XMP — Adobe's format. Editing history, ratings, keywords, and sometimes the author or copyright holder.
- IPTC — the press and stock-photo standard. Captions, credit lines, contact details.
The privacy problem is concentrated in EXIF GPS. A holiday photo is harmless; a photo taken inside your home, posted publicly, quietly publishes your address to anyone who opens the file properties.
Check before you strip
Look at what a file actually contains before deciding. The EXIF viewer reads the tags and shows them to you, including any GPS coordinates. This is worth doing once on a photo straight off your phone, because seeing your own front door on a map is more persuasive than any explanation.
How to remove metadata
1. Open the EXIF remover. 2. Add the photos you are about to share. Several at once is fine. 3. The tool strips the metadata segments and reports what it removed. 4. Download the cleaned files.
This does not touch image quality
Worth being precise, because it is the most common worry: the removal is lossless.
The tool edits the file's container at the byte level, deleting the metadata segments and leaving the compressed image data untouched. It never decodes and re-encodes the picture. A cleaned JPEG is pixel-for-pixel identical to the original — only smaller, by however many bytes the metadata occupied.
This is genuinely different from what happens if you strip metadata by re-saving a photo in an editor, or by running it through a compressor. Those re-encode the image and cost you a generation of quality.
What gets removed, by format
| Format | Removed | Deliberately kept |
|---|---|---|
| JPEG | EXIF and XMP (APP1), IPTC/Photoshop (APP13), comments (COM) | JFIF (APP0), ICC colour profile (APP2) |
| PNG | `eXIf`, `tEXt`, `zTXt`, `iTXt` chunks | everything else |
| WebP | EXIF and XMP chunks from the RIFF container | everything else |
Two honest limitations:
- The ICC colour profile is kept on JPEGs on purpose. It describes how colours should be interpreted. Removing it can visibly shift colours on wide-gamut displays, which is a worse outcome than leaving a profile that carries no personal information.
- HEIC, GIF, BMP, TIFF and SVG are not supported by the byte-level stripper. For an iPhone HEIC, convert it first with the HEIC to JPG converter, then strip the resulting JPEG.
When this matters most
- Selling online. Marketplace photos are usually taken at home. GPS in a listing photo tells buyers where you live.
- Dating profiles and forums. The single highest-risk case, for the same reason.
- Journalism and sensitive sources. Timestamps and device fingerprints can identify who took a photo.
- Publishing under a pseudonym. Camera serial numbers appear in EXIF on some bodies and link separate uploads to one device.
- Business documents. Screenshots and scans can carry author names and internal file paths.
What platforms do, and why you should not rely on it
Most large social networks strip EXIF when they process an upload. That is real, but it is not protection you control:
- It applies to the copy they re-encode and serve, not to the original if the platform also offers a download of it.
- It does not apply to files sent through chat apps and email, which frequently pass images through untouched.
- It is a platform implementation detail that can change without notice.
Stripping before you upload removes the dependency.
Your files stay on your device
This tool runs entirely in your browser. The bytes are read from local disk by JavaScript, edited in memory, and handed back as a download. Nothing is transmitted, so there is no server copy to trust, leak, or subpoena — which is the only defensible way to build a privacy tool.
Troubleshooting
- "No metadata found." The file genuinely had none. Screenshots, and images already processed by another tool, often arrive clean.
- The file size barely changed. Normal. Metadata is typically a few kilobytes unless a large thumbnail or colour profile was embedded.
- The photo rotated after stripping. Rare but real: some images rely on the EXIF orientation flag rather than storing pixels the right way up. Rotate it with the rotate tool and the correction is baked into the pixels.
- An unsupported format. Convert to JPEG or PNG first, then strip.