Does Screenshotting a Photo Remove Its Metadata?

The folk privacy trick is: open the geotagged vacation still, take a screenshot, send the screenshot. The intuition is half right. The screenshot is a new framebuffer capture. It does not copy APP1 from the decoder’s input. Camera GPS does not teleport. The intuition is half wrong: you now have two objects, and the dangerous one is usually still the one in Photos. Channels that look like ‘I already screenshotted it’ still attach Recents. Quality drops. UI chrome (clock, notch, nav bar) becomes part of the picture. The master is untouched.

Why two copies disagree is why two copies of the same photo can have different metadata. How to strip a screenshot file itself is remove metadata from an Android screenshot. This page is the myth: screenshotting as a substitute for wiping the original.

What a screenshot inherits — and what it does not

Does not inherit: the camera’s GPS IFD, DateTimeOriginal from the shutter, MakerNotes, the lens model. Those tags live in the still you were viewing, not in the pixels of the screen buffer as EXIF. The screenshot encoder writes a new file. On many phones that file is a PNG with a thin header, or a JPEG with capture-time fields about the screenshot, not about last Tuesday’s hike.

May include: capture time, device or OS software strings, sometimes a color profile. iOS and Android change this. Do not memorize last year’s screenshot EXIF as a warranty. Open the screenshot in a panel if that is the file that will travel.

Never does: delete tags from the original. Never does: cover a house number in the pixels (you still see the house). Never does: remove the original from iCloud or Google Photos.

Why the trick still leaks

You send the screenshot from the share sheet’s first suggestion — which is the photo, because you had it open. You put both in a zip. You later post from the album. A partner downloads the original from a shared library. The screenshot was theatre; the master was the send.

Quality is the other cost. You photographed a photograph through a display: moire, status bar, lower resolution. Recipients who need a clean still will ask for ‘the original,’ and you will send the tagged one to be helpful.

What to do instead

1. Decide which file will leave the device. If it is the camera still, convert HEIC to JPEG if needed, open the MetadataWipe tool, strip, send the -metadatawipe download.
2. If you truly must send a screenshot (a viewer with no export), wipe that screenshot as an image too — remove metadata from an Android screenshot — and still do not attach the camera original beside it.
3. Name the objects. hike-original.jpg versus hike-screen.png. Headers will not match. That is why two copies of the same photo can have different metadata.

Scenarios

A map photo with GPS, screenshotted to ‘remove location.’ The screenshot may lack EXIF GPS and still show the map. The original still has the pin in the header. Strip the original if that is what you will post; cover map pixels separately if the picture itself locates you.

A dating-app ‘screenshot this so they don’t get EXIF.’ The app may receive a screenshot while your camera roll still has the tagged selfie. The next app import from Recents is the selfie.

A desktop: screenshot of Lightroom’s main view. The screenshot is a picture of the UI. The TIFF on disk is unchanged.

Mistakes

Screenshot, then share from Recents. Recents is chronological and visual. You will pick the wrong object.

Assuming the screenshot is empty of all tags. Inspect it if it travels.

Using screenshot instead of strip because it felt faster, then sending original quality later. The later send is the tagged file.

Two-copy mechanics: why two copies of the same photo can have different metadata. Screenshot-as-file hygiene: remove metadata from an Android screenshot.

Related guides

See also:

• Why two copies of the same photo can have different metadata
• Remove metadata from an Android screenshot