Do Android Screenshots Have EXIF Data? No — the Time Lives in the Filename
No — an Android screenshot does not carry GPS, camera make/model, or lens data, and in almost every case it carries no EXIF block at all. Android saves a screenshot as a PNG (or, on some devices, HEIF) by capturing the screen as a bitmap and exporting that image; nothing in that path writes a camera-style EXIF block. The one time clue Android keeps is in the file name — Screenshot_20240120-103015.png — not inside EXIF. The full picture is on our main guide, do screenshots have exif data. Honesty note: this article is compiled from Android's documented screenshot behavior, a 2023 PhotoPrism bug report, and third-party write-ups. We did not run a device test in this session, so treat the field-level claims as documented behavior, not a byte read we performed.
The short answer, spelled out
On a PC or Mac a screenshot is a fresh pixel capture where do screenshots have exif data is answered with a flat ‘no’ — the apps write a clean container from scratch. Android behaves the same way: when you press Power + Volume Down (or use the screenshot tile / Palm swipe / Assistant), the system grabs the screen as a bitmap and saves a PNG. There is no camera, no lens, and no GPS fix behind it, so there is nothing to stamp into an EXIF block. This is why an Android screenshot — like a Windows or Mac one — is metadata-empty. The one exception in this whole series is the iPhone (see our iPhone screenshots + EXIF write-up), because iOS routes the capture through its camera-image pipeline and does stamp a small block.
What is actually inside an Android screenshot
Based on documented Android behavior and what metadata tools report, here is the field-level picture. The leftmost column is the metadata; the middle is whether it shows up in an Android screenshot; the right is how we know.
| Metadata | In an Android screenshot? | How we know |
|---|---|---|
| Capture date & time | No — lives in the filename (Screenshot_YYYYMMDD-HHMMSS.png), not EXIF | PhotoPrism issue #3651 (2023): “Android screenshots lack EXIF metadata but have the timestamp in the filename” |
| GPS / location | No | airdroid.com (fetched 2026-10-24): “screenshots… without any location data embedded”; GeoTag.World states GPS is commonly absent in screenshots |
| Camera make / model / lens | No | No camera in the pipeline |
| Color profile (sRGB / iCCP) | Possibly — via PNG chunks, not EXIF | PNG spec; Android color management |
| Pixel dimensions | Yes | Always present |
| EXIF block (DateTimeOriginal etc.) | No in standard AOSP | PhotoPrism #3651: “lack EXIF metadata” |
Why Android screenshots carry no EXIF (and iPhone does)
It comes down to who builds the file. Android’s screenshot service captures the screen as a bitmap and exports a PNG; it never touches the camera image pipeline, so there is no code path that would write a date/software/GPS tag the way a photo app does. iOS, by contrast, routes the capture through the same image pipeline that handles camera photos, so it tacks on the date/time/software tags it normally writes for any image. None of that is a location. If your real concern is a camera’s GPS tag, that is a separate problem — the turn off camera location guide covers the Android switches that stop a phone from ever writing GPS into a photo. A screenshot sidesteps that entirely because the GPS never enters the file.
The one time clue Android keeps — and where it lives
Android does record when a screenshot was taken; it just does not put it in EXIF. Instead the time is baked into the file name: Screenshot_20240120-103015.png means the shot was captured on 2024-01-20 at 10:30:15. A 2023 PhotoPrism bug report (“Index: Sniff timestamp from Android Screenshots”, issue #3651, opened Aug 18 2023) is explicit about this: “Android screenshots lack EXIF metadata but have the timestamp in the filename.” The file’s own filesystem timestamps (created / modified) also reflect the save moment. So you can still recover when a shot was taken — just not from EXIF, and with no time-zone recorded in the name.
What is NOT in the file (the location question)
The reassuring part: an Android screenshot holds no GPS, so dropping it into geotag.world returns no coordinates — the site itself notes this is common for screenshots. No camera make, no lens, no shutter speed. If you screenshot a map, a chat, or a photo, the original photo’s GPS is gone; you captured pixels, not a file. A third-party write-up confirms the principle directly: airdroid.com states “Do Screenshots Show Location? No. Screenshots are essentially static captures of what’s on the screen at that moment, without any location data embedded in it” (fetched 2026-10-24).
How we know this (and what we could not check)
We are explicit about sourcing because this is a documented-behavior article, not a device test. Verified this session: PhotoPrism GitHub issue #3651 (opened 2023-08-18) states Android screenshots “lack EXIF metadata but have the timestamp in the filename,” and shows the Screenshot_YYYYMMDD-HHMMSS.png format. airdroid.com (fetched 2026-10-24) states screenshots carry no embedded location. GeoTag.World returned HTTP 200 on 2026-10-24 and, consistent with earlier checks, documents that screenshots commonly have no GPS to read. Android’s documented screenshot pipeline saves a PNG export from a screen capture, which is the basis for the “no camera pipeline” claim. Not checked this session: we attempted to load exifdata.org and exifreader.org on 2026-10-24 and both returned HTTP 502 (bad gateway), so we are not quoting their pages — we name them only as the standard EXIF viewers you can drag a screenshot into yourself.
How to check your own Android screenshot
Three ways, none of which upload your file. Open the file in a metadata viewer, or run ExifTool locally: exiftool Screenshot_*.png lists every tag — you will see no EXIF block and no GPS, and the capture time will be in the file name, not the tags. Or drag the PNG into geotag.world (live on 2026-10-24) to confirm there is no GPS; exifdata.org and exifreader.org are the other standard viewers, though both returned HTTP 502 when we tried them on 2026-10-24. Because there is no EXIF to read, the most useful metadata you have is the filename timestamp.
If you want that metadata gone
There is essentially nothing sensitive to remove from an Android screenshot — no GPS, no make/model — so stripping is optional. If you want a perfectly clean file anyway, any metadata remover that rewrites the PNG without extra chunks does it. Our do screenshots have exif data guide covers the general mechanism, and clear-metadata-from-photo walks the one-click path. Because the only time clue is the filename, you may also want to rename the file if hiding when it was taken matters to you.
FAQ
Do Android screenshots have EXIF data? No. They carry no GPS, no camera make/model, and in standard AOSP no EXIF block at all; the capture time lives in the filename, not in EXIF.
Do Android screenshots have GPS or location data? No. A screenshot carries no location; airdroid.com confirms screenshots embed no location data, and GeoTag.World notes this is common for screenshots.
Where does Android store the screenshot time if not in EXIF? In the file name — Screenshot_YYYYMMDD-HHMMSS.png — and in the file’s own timestamps, per PhotoPrism issue #3651 (2023).
Why do iPhone screenshots have metadata but Android screenshots don’t? iOS routes the capture through its camera-image pipeline and stamps date/software; Android’s screenshot service exports a PNG from a screen bitmap with no camera pipeline, so nothing writes EXIF.
How do I check an Android screenshot for EXIF? Run exiftool Screenshot_*.png or drag the PNG into a viewer; you will find no EXIF block and no GPS, with the time only in the filename.
Was this tested on a device? No. This is documented behavior compiled from a 2023 PhotoPrism report, airdroid.com, GeoTag.World, and Android’s documented screenshot pipeline; we did not run a device test in this session.