Translation status
This guide is currently shown in English for this locale. Tool links still point to localized routes where available.
Mostly yes, but not completely, and not cleanly. Taking a screenshot of a photo drops the original file's EXIF block — GPS coordinates, camera model, capture time — because a screenshot copies pixels, not the source file's internal structure. What it does not do is produce a metadata-free image: the screenshot writes its own device, operating system, and capture-time fields, and it costs you image quality in the process.
This guide is currently shown in English for this locale. Tool links still point to localized routes where available.
Mostly yes, but not completely, and not cleanly. Taking a screenshot of a photo drops the original file's EXIF block — GPS coordinates, camera model, capture time — because a screenshot copies pixels, not the source file's internal structure. What it does not do is produce a metadata-free image: the screenshot writes its own device, operating system, and capture-time fields, and it costs you image quality in the process.
This guide describes browser-based file workflows, format tradeoffs, and ConvertUnlimited processing boundaries for supported tools.
| Data in the original photo | Survives a screenshot? | Why |
|---|---|---|
| GPS coordinates | No | Stored in the source file's EXIF block, which a pixel capture never reads |
| Camera make, model, and lens | No | Same EXIF block; the screenshot has no access to it |
| Original capture date and time | No | Replaced by the time the screenshot itself was taken |
| Exposure, ISO, aperture | No | EXIF fields, dropped with the rest of the block |
| Device and OS that took the screenshot | Added | Written fresh by the screenshot function, so the file is not metadata-free |
| Visible watermark or burned-in timestamp | Yes | It is pixels, not metadata — a screenshot copies it faithfully |
| Faces, landmarks, and street signs in frame | Yes | Also pixels; screenshotting reveals exactly as much as the original did |
| Full image quality | No | Recaptured at screen resolution and re-encoded, so a photo shown smaller is downscaled |
A screenshot is a new image file capturing what is displayed on your screen. It does not contain the GPS location, camera make and model, lens information, exposure settings, or the original capture timestamp — none of the fields a camera or phone would have embedded in the source photo — because a screenshot only captures pixels, not the source file's internal data structure.
The new screenshot file gets its own metadata: the device name, operating system version, screen resolution, and the timestamp of when the screenshot was taken. A photo taken with a phone's camera can embed 30 or more EXIF fields; a screenshot typically embeds far fewer, but it is not metadata-free. Screenshots taken through the operating system's own screenshot function are also generally not geotagged the way camera captures are, since that capture pathway does not run through the camera app's location-tagging code.
Most platforms save a screenshot as a PNG file by default — iOS, macOS, Windows, and stock Android all do this — while a camera photo is more often JPEG, or HEIC on recent iPhones. That format switch matters for metadata capacity as well as privacy: PNG's original specification does not carry EXIF the way JPEG does, so a screenshot has structurally less room for camera-style fields even before considering what the operating system actually chooses to write into it.
Some camera apps burn a visible timestamp, watermark, or coarse location label directly into the image pixels, as an overlay you can see rather than a metadata field you can query. Screenshotting removes the original EXIF data, but it does nothing to a mark that is already part of the visible image, because that mark is pixels, not metadata. If a photo has a visible overlay you want gone, that has to be cropped or edited out separately.
The exact fields a screenshot embeds vary somewhat by platform and by how it was captured. iOS and macOS screenshots are saved as PNG and typically carry only OS-level metadata rather than a full camera-style EXIF block. Windows screenshots taken with the Snipping Tool or the Print Screen key are also usually PNG with minimal embedded metadata. Android varies more by manufacturer, since each phone maker layers its own screenshot handling on top of the stock OS behavior; the general pattern — no camera-style EXIF, some OS-level metadata — still holds, but the exact fields present are less predictable than on iOS.
Everything above describes the operating system's own built-in screenshot function. A third-party screen-capture or annotation tool sits between you and the OS, and can write its own additional metadata, such as an application name or version tag, or apply its own compression settings before saving the file. If you rely on a specific tool as part of a privacy-sensitive workflow, check what that particular tool writes rather than assuming it behaves exactly like the built-in function.
What is EXIF data? · Does social media strip metadata? · Remove location data from your photos
It removes the original camera-embedded GPS field, but it is an indirect method that also reduces image quality and adds new metadata of its own. A dedicated metadata-removal tool is a more direct and reliable way to control exactly what is removed.
It does not meaningfully add privacy benefit beyond the first screenshot. Each screenshot generation mainly adds its own device and timestamp metadata rather than stripping anything further.
Potentially the device model, OS version, and the exact time of the screenshot, which can be combined with other context. It is not the same kind of sensitive as GPS coordinates, but it is not nothing.
It can. A screenshot recaptures whatever the screen is rendering at that moment, at the screen's resolution and color handling, which is not always identical to the source file's own resolution and color profile. For a photo displayed smaller than its original size, the screenshot is effectively a downscaled, re-compressed copy.
It removes the GPS coordinates stored in the original file's EXIF block, because a screenshot copies pixels rather than reading the source file's metadata. It does not remove location that is visible in the image itself — a street sign, a storefront, or a burned-in location label survives the screenshot exactly as it appeared.
Screenshots generally do not carry a camera-style EXIF block, partly because most platforms save them as PNG, whose original specification has no EXIF chunk. They do still carry OS-level metadata such as device name, OS version, screen dimensions, and the capture timestamp, so "no EXIF" is not the same as "no metadata".
No. They produce different results: metadata removal keeps the original pixels and strips the fields, while a screenshot keeps neither the original pixels at full fidelity nor a guarantee about what fields the new file contains. If the goal is specifically to strip metadata, removing it directly is the operation that matches the goal.
Remove metadata directly and reliably in the browser instead: Metadata Remover. Not sure what yours is carrying? Check a photo first.