How to Remove Metadata from Screenshots

What a screenshot carries

A screenshot usually holds less than a camera photo, but what it holds is specific. Expect the device model, the operating system, and the exact date and time the shot was taken, written into the PNG file screenshots are normally saved as. Some systems and apps add a software field naming the tool that captured or last saved the image, and screenshots passed through editors can accumulate more with every save.

There is generally no GPS in a fresh screenshot, because no camera and no location fix were involved in making it. The risk profile is different rather than absent: a screenshot's timestamp is precise to the second, the device and OS fields identify your setup, and if the screenshot later passes through an AI editor or a cloud tool, fields describing that — including, for AI-edited images, generation data — can be added on top.

It is also worth knowing what a screenshot's metadata says about your habits rather than your identity. A run of screenshots shared over months — support exchanges, public posts, documentation — carries consistent device and timing fields that show when you work, how quickly you respond and which tools you use. Individually these are footnotes. Together they sketch a working pattern, which is one more reason to clean the files you publish most often rather than treating every screenshot as disposable.

How it differs by platform

On phones, screenshots are typically PNG files carrying the model, software version and timestamp. What happens next depends on the app you share through: some routes recompress the image and drop most fields, others send the original file untouched. On Windows, the Snipping Tool and similar utilities write their own identifying fields, and on a Mac, screenshot files carry creation times and may gain software data whenever a preview or editor saves them again.

Because behaviour varies by tool, version and sharing route, treat any single description of 'what screenshots contain' — including this one — as a starting point. The reliable method is to scan the actual file you are about to send. Thirty seconds of checking settles what pages of general advice cannot, and it works the same on every platform.

The screenshot-of-a-photo trap

A persistent myth says that screenshotting a photo strips its metadata. It does remove the original's EXIF from the new file, because the screenshot is a new image — but it replaces a good file with a worse one. The screenshot is limited to your screen's resolution, may include interface elements or black bars, and its colours are a screen rendition rather than the photograph itself.

Worse, the screenshot is not metadata-free: it carries fresh fields of its own, including your device and the exact time you took the screenshot. So the trade quietly exchanges the photographer's data for yours, at lower quality. If the aim is to share the photo without its metadata, clean the original file instead — the picture survives intact, and the removal is deliberate rather than a side effect.

Edited and annotated screenshots carry more

Most shared screenshots are not raw captures. They have been cropped, arrowed, highlighted or blurred in a markup app, and every save is a chance for that app to write itself into the file: its name and version in a software field, a new modification timestamp, and in PNG files, text chunks that some editors use to store their own settings or document data.

AI-assisted editors add another layer. An image that has passed through an AI cleanup, expansion or annotation tool may carry generation fields or provenance data much like an AI-created image. None of this makes annotation a bad idea — it makes the order of operations matter. Do all your editing first, and treat metadata removal as the final step before the file leaves you, because any later save can write new fields back in.

There is a subtler addition to watch for: some annotation and collage apps preserve the fields of every source image they combine, or write an editing history listing the operations applied. A screenshot annotated from a photo can therefore end up carrying traces of the photo's data as well as the screenshot's own. You cannot predict this from the app's store description, and you do not need to — the scan of the finished file lists whatever the chain of tools left behind, and cleaning at the end of the chain handles all of it at once.

Clean the pixels too: visible content

With screenshots, the larger risk is usually on the surface. Contact names, email subjects, account balances, file paths, browser tabs, notification previews and the clock in the corner are all visible content, and metadata removal cannot hide any of them. A perfectly cleaned file can still give away everything that matters if the picture itself was never reviewed.

So review the screenshot as a stranger would before it goes anywhere. Crop tightly to the area that makes your point, blur or cover anything that identifies people, accounts or systems, and check the edges — status bars and window borders are where stray details collect. Pixel problems get pixel solutions; file problems get file solutions. Sensitive screenshots usually need both, in that order.

A workflow for sharing screenshots of work

Capture the screenshot, then do every visible edit: crop, annotate, blur. Export or save the finished version as your share copy, keeping the raw capture aside if you might need it. Then run the copy through a metadata cleaner — screenshots are PNGs, and MediaPure's image cleaner accepts PNG alongside JPG and WebP, processing images in memory and verifying that every pixel survives unchanged.

Finish with a scan of the cleaned copy. The report should show no device, date or software fields you care about, and the image should look exactly like the version you approved — because if it does not, something re-saved it along the way. Only then send it, through whatever channel the work requires, knowing both layers of the file have been looked at.

Screen recordings are the video version of the same problem

Everything in this guide applies, with more at stake, to screen recordings. A recording carries container tags naming the device and encoder, creation timestamps, and — for phone recordings — potentially the same location data a camera video would have. It also runs for minutes, which multiplies the chances of a notification or a stray window appearing in the visible content.

Our separate guide to removing metadata from screen recordings covers that workflow in full. The shared principle is simple enough to state here: edit for the eyes first, clean the file second, verify third, and never assume a screen capture of any kind is anonymous just because no camera was involved.