How to Remove Metadata From Photos, and What Each Method Actually Strips

The advice is everywhere: strip the metadata before you share a photo. The instructions are usually correct and the claim about what they achieve usually is not.

On an iPhone the standard recipe is Photos → Share → Options → Location off. That does exactly one thing: it excludes the GPS tag from that share. Apple’s own guide describes it as a location switch and nothing more, so the rest of the EXIF block (device model, capture timestamp, camera settings) is not what it is for, and the location stays attached to the photo in your library.

Which is fine, if the GPS tag was what you were worried about. It is worth knowing that is all it was.

What is in there, and what actually matters

A photo carries a block of EXIF fields. In practice there is a steep hierarchy of consequence:

• GPS coordinates: precise enough to identify a home, a school, a workplace. This is the field that matters, and it is the reason the rest of this page exists.
• Capture timestamp and device model: individually dull, collectively a way to link photos to each other and to you.
• Exposure, lens, orientation: of no consequence to anyone.
• Free-text fields: comment, description, artist, copyright. Normally empty. They will hold whatever anyone puts in them, which makes them the first place anyone looks for hidden text.

If you only ever deal with the first item, you have addressed most of the real risk.

The methods, and what each one leaves behind

iPhone: share sheet, Location off. Removes the GPS tag from that share only. Leaves the rest of EXIF. Leaves the original untouched in your library. Has to be done every time.

iPhone: stop it at the source. Settings → Privacy & Security → Location Services → Camera → Never. New photos are never tagged, so there is nothing to remember and nothing to strip. This is the better fix for most people, and the one the advice articles mention last. It does not clean photos you already took. Apple documents the location-metadata options in its Personal Safety guide.

Android: varies, so verify yours. Google Photos offers a location toggle when sharing, and several manufacturers add their own. Android is not one product, so rather than trusting a recipe from a page like this one: share a photo to yourself, then inspect what arrived with an EXIF viewer. That takes two minutes and answers the question for your phone rather than for someone else’s.

Windows: right-click → Properties → Details → “Remove Properties and Personal Information.” This is a real and thorough built-in. It will create a cleaned copy or strip the original, and it removes far more than the location.

Mac: Preview shows you EXIF (⌘I) but is not a reliable stripper. To actually remove it, exiftool -all= image.jpg from a terminal rewrites the file without the metadata block. This is the blunt, complete option.

Any platform: re-encode the image. Opening a photo and exporting it as a new file usually drops the EXIF block, because the export writes a fresh header. This has a side effect worth knowing: it also destroys anything hidden in the pixels, because a re-encode rewrites them.

The one that catches people out: “the platform strips it anyway”

Most social platforms do remove EXIF from the copy other people can download. That is a genuine protection against a stranger saving your photo and reading the coordinates out of it.

It is not the same as the data being gone. The platform received the original. The GPS tag was in the file you uploaded, and what the company does with it afterwards is its own business, governed by its policy rather than by the stripping.

So: uploading protects you from other users. It does not protect you from the service. If that distinction matters for a particular photo, strip it before it leaves your device, not after.

Metadata is not the pixels

One thing to be clear about, because the two get conflated.

Metadata and image data are separate regions of the file. A metadata stripper rewrites the header and leaves the pixels alone. So:

• Stripping metadata does not remove anything embedded in the pixels. If a photo was carrying a hidden payload there, it still is.
• Re-encoding does destroy pixel payloads, comprehensively. It is the same mechanism that makes hidden data not survive chat apps, measured here.

If you are checking a photo someone sent you rather than cleaning one you are about to send, the two places text can actually live, the metadata and the pixels, are compared in How to Hide Text in an Image: Two Ways.

Where StegoSafe sits in this

Opposite, and worth stating so the distinction is clear.

This page is about removing something from a photo that you did not intend to be there. StegoSafe is about putting something there on purpose: a seed phrase, a set of recovery codes, encrypted on your device and written into the pixels of a photo you keep. It writes to the pixels, not the metadata, precisely because metadata is the first thing every upload pipeline strips.

The two concerns do not conflict. Strip the EXIF from photos you send other people; that has nothing to do with the photos you are using as storage, which should not be uploaded anywhere in the first place.

The short version

1. The iPhone share-sheet toggle removes the GPS tag from that share, not the EXIF block, and not the copy in your library.
2. Settings → Privacy & Security → Location Services → Camera → Never is the fix that does not depend on remembering.
3. Windows has a thorough built-in; on a Mac, exiftool -all= is the complete option.
4. Platforms strip EXIF from what other users download, after receiving your original.
5. Metadata and pixels are different parts of the file. Stripping one does nothing to the other.