Do Screenshots Reveal Your Location? What We Put Through a Screenshot and What Came Out

Two-part answer: a screenshot does not leak your GPS coordinates as metadata, but it can still reveal your location through what is on the screen. We built a 1200×800 photo carrying 15 EXIF fields and a GPS fix (latitude, longitude, altitude), then did exactly what a screenshot does - grabbed the on-screen pixels and wrote them to a PNG. The PNG came back with 0 EXIF fields and 0 GPS: no coordinate metadata survived. So the file itself will not tell anyone where you were. The catch is the other half: a screenshot is a picture of your screen, so if that screen shows a map pin, an address, or a recognizable place, the location is visible in the image anyway. The metadata is gone; the content is not. For the measured baseline on what a screenshot carries, start at do screenshots have exif data.

What we measured, and how (read this first)

We measured the metadata half directly with Pillow 12.3.0 and piexif 1.1.3 on Python 3.13, and we modeled the screenshot at the pixel level - which is exactly what an OS snipping tool does. We created a photo with a real GPS fix, then saved its pixels to a PNG, the format every screenshot tool writes. We also confirmed a plain save-as-PNG drops the EXIF marker too. What we did not do: run a live map app and snip it. That content-reveal half is reasoning, not a byte measurement, and we label it as such below. For confirmation that real Windows screenshots carry no EXIF at all, we lean on our earlier measured run on this machine (do screenshots have exif data), where four real Snip & Sketch captures showed zero eXIf chunks - previously measured, not re-run today.

The source photo: 15 EXIF fields and a real GPS fix

We created a 1200×800 JPEG and wrote metadata into it on purpose so there was something to lose. After writing and reading it back through piexif, the file held 15 fields across the IFD0 and Exif blocks (Make, Model, Software, Orientation, Artist, both timestamps, ExposureTime, FNumber, ISO, FocalLength, LensModel, Sharpness, ColorSpace) and a separate GPS block of 5 fields carrying a real fix: latitude 31°22'13"N, longitude 121°28'12"E, altitude 10 m. The file was 16,030 bytes, MD5 6caeecda964a3a9a01c88ec8c8fc4f77. That is the location data we then tried to screenshot away.

What a screenshot actually is

A screenshot is a raster capture of whatever is drawn on the screen, and every OS snipping tool writes it out as a PNG (Windows Snip & Sketch, macOS Screenshot, Android and iPhone capture all produce PNG). PNG has no EXIF segment - there is literally no container for coordinate metadata. Our earlier measured run on this machine confirmed the practical result: four real Windows Snip & Sketch PNGs contained the chunks IHDR, sRGB, gAMA, pHYs, IDAT and IEND, and zero eXIf chunks and zero EXIF fields. So a screenshot starts from a format that cannot hold GPS.

The screenshot test: photo pixels become a PNG with 0 GPS

This is the core measurement. We opened the 15-field, GPS-tagged source photo and saved it as a PNG - the exact transformation a snip performs on the displayed pixels. The result: 4,589 bytes, MD5 12f36468decedb9c1de30c7d06e2e11f, 0 EXIF fields read back through getexif, GPS absent, and a byte-level walk found no eXIf chunk. The location fix we wrote into the photo was gone, because none of that metadata lives in the pixel buffer a screenshot copies. We also tested a plain save-as-PNG straight from the JPEG; it, too, contained no Exif\x00\x00 marker. Either path - the screenshot or a naive re-save - strips the GPS.

The metadata answer: no, screenshots don't carry your coordinates

On the metadata question the answer is clean and measured: a screenshot file does not contain your GPS location. EXIF - including the GPS IFD - lives in the file's metadata segment, not in the pixels. A screenshot copies the rendered pixels and writes them to a PNG, which has no EXIF container. So the coordinates we embedded were simply never part of what got captured. If someone receives your screenshot and runs an EXIF tool on it, they will find 0 GPS fields, the same as we did.

The content answer: yes, screenshots can show your location anyway

This half is the catch, and it is reasoning rather than a byte measurement (we did not launch a map app in this run). A screenshot is a picture of your screen, so it shows whatever your screen showed. If your screen displays a map with your location pinned, a delivery or home address in a document, a photo whose background is a recognizable landmark or street, or a video call with a window onto a distinctive view, all of that is in the screenshot. The metadata is stripped, but you can still hand someone your location by framing it. The rule is simple: the file won't report coordinates, but the picture can still show where you are.

Why this matters more than the metadata question

People often ask 'do screenshots reveal your location' expecting a yes/no about EXIF, then relax when they learn the GPS is gone. The more common leak is the content one, and it is invisible to any metadata checker. A screenshot of a Maps window with 'You are here' is a perfect location reveal even with zero EXIF. So if your real worry is 'will this image show where I am', check the picture, not the properties panel. The metadata is the easy part; the frame is the hard part.

What to actually do about it

Three moves. If you only need to share what is visible and want zero metadata, screenshot it - that drops EXIF, GPS and any file metadata in one step, because you are sharing pixels. If you also need to avoid showing a place, crop or blur the map, address or landmark before you send; a screenshot does not redact content for you. If you need the real document or photo (not just an image of it), screenshotting loses the original, so instead strip the source file yourself first, as in clear metadata from photo. The screenshot solves the metadata problem; it does not solve the content problem.

FAQ

Do screenshots contain GPS location data? No - measured. We turned a GPS-tagged photo into a PNG the way a screenshot does and read back 0 EXIF fields and 0 GPS. A screenshot writes PNG, which has no EXIF container, so the coordinate metadata never makes it into the file.

Why doesn't a screenshot keep the GPS coordinates? Because the GPS lives inside the EXIF block, which is file metadata, not pixels. A screenshot copies the rendered pixels and saves them as a PNG. The metadata segment is simply not part of what gets captured, so the fix is gone before the file is even written.

Can a screenshot still reveal where I am? Yes - through content, not metadata. This part is reasoning rather than a byte test: a screenshot shows whatever was on your screen, so a map pin, an address, or a recognizable landmark in the frame still gives away your location even with zero EXIF. Check the picture, not the properties panel.

Do platforms strip EXIF from screenshots when I upload them? For screenshots the question is moot - our measured run already showed the screenshot carries 0 GPS before any upload, so there is nothing for a platform to strip. For photos uploaded directly (not screenshots), the stripping behaviour varies by platform; see does-facebook-remove-exif-data for the documentation-versus-testing split.

Is screenshotting a photo enough to remove its location before sharing? For the metadata, yes - the GPS is gone in the screenshot. But if the photo on your screen shows a recognizable place, that content survives. Screenshotting removes the coordinates; it does not remove what the image depicts.

How do I share something without revealing my location at all? Screenshot to drop metadata, then crop or blur any map, address or landmark in the frame to handle the content side. If you must share the original file rather than an image of it, strip the source yourself first with a metadata tool, as in clear-metadata-from-photo.