Does screenshotting an image remove its metadata? Yes — and that's not the whole story

Short answer: yes. A screenshot is a brand-new image file rendered from your screen — the original photo's EXIF, GPS coordinates, C2PA manifest, and every other metadata block are simply not part of it. That's why "just screenshot it" is the most common folk method for scrubbing a photo.

It works — for what it does. The problem is what it does besides that. There are three catches, and depending on why you're scrubbing, each one can matter.

Catch 1: the screenshot has its own metadata

A screenshot isn't a metadata-free file — it's a file with fresh metadata, written by your device. Typically: a precise timestamp of when you took the screenshot, the fact that it is a screenshot (dimensions matching your exact screen resolution are a giveaway on their own, and some platforms tag screenshots explicitly), and depending on the OS, device or software identifiers.

For casual sharing, harmless. But if your goal was "this file says nothing about me," note that it now says something different about you: what device you use, your screen size, and exactly when you were looking at that image. Check one yourself — screenshots are a surprisingly good first file to inspect.

Catch 2: you traded metadata for quality

The original file was the photo. The screenshot is a picture of your screen showing the photo: capped at your display resolution, re-compressed, often with the image scaled to fit. Screenshot a 12-megapixel photo on a phone and you've thrown away most of its resolution permanently.

Compare that with actual metadata stripping, which removes the hidden data while leaving every pixel untouched. Same privacy result on the metadata layer, zero quality cost — the difference matters any time the image is the point: listings, portfolios, prints, anything you'd zoom into.

Catch 3: pixels don't screenshot away

Everything that lives in the image itself survives, because the screenshot faithfully reproduces it. That includes visible content that reveals location (landmarks, storefronts, reflections) — and, for AI-generated images, invisible pixel-level watermarks like Google's SynthID, which are specifically designed to survive screenshots, resizing, and recompression. We've covered what survives what in detail; the one-line version is that a screenshot kills the metadata layer and nothing else.

The flip side is worth knowing too: screenshotting an authentic photo destroys its proof. If an image carried Content Credentials establishing where and how it was captured, the screenshot carries none of that — one reason provenance systems pair fragile metadata with durable watermarks.

So when is screenshotting actually fine?

Honestly: in a pinch, for a low-stakes share where quality doesn't matter, a screenshot does remove the original metadata and requires zero tools. If that's the situation, it works, and we won't pretend otherwise.

Use a real stripper instead when any of these are true: the image quality matters (it stays pixel-identical); you want to know what you're removing rather than hope (the report shows you — exact GPS coordinates, device, AI tags); you want selective control (keep copyright, drop location); or you're cleaning many files (batch, still in-browser). And remember the delivery half of the problem: a perfectly cleaned file shared through the wrong channel picks up no metadata, but the wrong channel preserves a dirty original perfectly — WhatsApp's document mode and email don't care how the file was made.

TL;DR

Yes — a screenshot discards the original image's metadata entirely, because it's a new file. It also adds your own device's metadata, permanently downgrades the image, and leaves everything pixel-based (visible location clues, AI watermarks) intact. Fine for a quick low-stakes share; for anything else, strip the metadata properly — same privacy win, none of the costs.