Do Screenshots Have Metadata? What Gets Saved and What Doesn't

The question comes up constantly, usually from somebody who has just been told that photographs carry hidden location data and is now wondering whether the screenshot they are about to send does the same.

Here is the direct answer. No, a screenshot does not carry camera tags or coordinates, because it was never produced by a camera. That is genuinely reassuring and it is also where most explanations stop, which leaves two more useful points unsaid: the file is not blank, and the contents of a screenshot usually give away more than any hidden field ever would.

Why there is nothing to record

Think about where the two kinds of file come from. A photograph begins with light hitting a sensor. At that instant the device knows a great deal worth storing: which lens was fitted, how long the shutter stayed open, what the sensitivity was set to, and — if positioning was permitted — exactly where it was standing. All of that gets written into the file because it describes an event in the physical world.

A screen capture begins with pixels that are already on your display. The system reads the frame buffer and writes it out as an image. There is no lens, no exposure, no shutter, and critically no position was consulted, because nothing about the operation needs one. The fields are absent rather than blanked — there was never anything to put in them.

This matches what we found in the re-encoding experiment described in our guide to metadata privacy: a screenshot-style re-render of a fully tagged photograph produced a file with nothing readable left in it.

What a screenshot does hold

"No camera data" is not "no data". Several things are still written, and they are worth knowing about even though none of them is alarming.

Dimensions and format

Width, height, bit depth and the encoding used. Unavoidable — a decoder cannot draw the image without them.

A colour profile

Most systems attach one so the image displays consistently elsewhere. It describes colour interpretation and says nothing whatsoever about you. We cover why this particular block is harmless in EXIF, XMP, IPTC and ICC explained.

A creation timestamp

Held by the filesystem rather than inside the image, and usually mirrored in the filename, which on most systems spells out the date and time of capture in plain digits.

Sometimes a software note

Desktop capture utilities and annotation apps often write their own name into the file. Mark up a screenshot with arrows and save it, and the editor may add an entry recording that it was involved.

Occasionally more, if a third-party app was used

This is the honest caveat. The guarantee applies to the capture routine built into the operating system. A third-party screenshot app is ordinary software that can write whatever it likes into the output, including an account identifier or, if you granted it positioning access for some other feature, conceivably a location. Rare, but worth a check the first time you use one.

What we found when we looked

Rather than assert this, we measured it. The method: capture the same page four ways — the built-in capture on a phone, the built-in capture on a desktop, a phone screenshot afterwards annotated in the system editor, and for comparison an ordinary geotagged photograph — then read every file with our own parser and write down the groups reported.

The pattern held in every case: screen captures produced a short, dull report, and the photograph produced a long one. This was our own small check on our own devices rather than a survey of every handset on the market, but the mechanism behind it is general — there is no sensor event to describe.

The part that actually matters

Having established that the hidden layer is nearly empty, here is the uncomfortable bit. Screenshots are frequently more revealing than photographs, because of what people screenshot.

Nobody photographs their bank balance by accident. Plenty of people screenshot a transaction to show a friend, and capture the running total above it. The same goes for:

• Notification banners that slide in during the capture, showing a message from somebody else.
• Browser tabs along the top, naming every other thing you had open.
• Account names and handles in a corner of the interface.
• Email addresses and phone numbers in a contact row you did not scroll past.
• Full names of other people in a group conversation.
• Autocomplete suggestions hovering below a search box.
• Addresses in a delivery tracker, often the sharpest exposure of all.
• The status bar, quietly supplying the time, the date, your carrier and your battery level.

That last one deserves a thought. A clock and a carrier name do not identify you alone, but combined with other fragments they narrow things down — which is precisely the aggregation effect the Office of the Privacy Commissioner of Canada describes, and the point the Electronic Frontier Foundation has made repeatedly about small details adding up.

How to check and clean one

Both steps are quick, and the second is optional for most purposes.

1. Read the file. Open the screenshot in our metadata viewer. It parses the image inside your browser and nothing is transmitted. For a plain capture you should see dimensions, format and a colour profile.
2. Be suspicious of a long report. If camera or position entries appear, the file is not what you think. The usual explanation is a photograph that was saved into the screenshots album, or an image received from someone else and re-saved.
3. Clean it if you want a plain file. The image metadata remover rebuilds the image locally, which discards any capture note or editor name. Expect a colour profile on the output — browsers attach one when encoding, and it carries no personal information.
4. Then study the picture itself. Crop the status bar. Crop the tab strip. Crop the notification. This takes longer than the other three steps combined and is where the actual protection lies.
5. Prefer cropping to covering. Drawing a black box over an account number is a visual effect; some editors preserve the pixels beneath. Cutting the region out removes the information.

Screenshots are not a cleaning method

A reasonable idea occurs to people at this point: if a screenshot has no camera data, why not screenshot a geotagged photograph instead of cleaning it? It does work, in the narrow sense that the new file carries none of the original tags.

Three reasons it is a poor habit, though. You lose resolution, because the capture is limited to what the screen displayed. You usually gain the surrounding interface unless you crop carefully. And it does nothing about the visible content, which as we covered in the pre-sharing checklist is the half that identifies locations. Treat it as a workaround when nothing else is to hand, not as a routine.

What platforms do with them

Nothing special. A screenshot uploaded to a social service goes through the same resizing and re-encoding pipeline as any other image, which strips a little and leaves the visible content untouched. Since there was almost nothing to strip, the main practical consequence is a modest loss of sharpness on text.

The service-by-service detail is in do Facebook, Instagram and WhatsApp remove photo metadata? The short version applies here too: the original file reaches their servers regardless, so whatever is in the picture has been shared the moment you press send.

Frequently Asked Questions

Do screenshots contain GPS coordinates?

Normally not. Coordinates are written by a camera app that has been granted positioning access, and the screen capture routine is not a camera app. It copies pixels already on the display, so there is no position to record and nothing to attach.

What does a screenshot file actually record?

Typically its pixel dimensions, the colour profile the system attached, a creation timestamp held by the filesystem, and sometimes a short note naming the capture tool. Some editors add their own entry when the picture is marked up and saved again.

Is sending a screenshot safer than sending the photo?

For hidden camera data, yes — the original tags do not carry across to a fresh capture. You give up resolution, and you change nothing about what the image depicts, so it is a partial measure rather than a substitute for cleaning a file.

Can anyone tell which device took a screenshot?

Not usually from the stored fields, but very often from the picture. Pixel dimensions, the shape of the status bar, the notch outline, font rendering and the system theme together narrow the device model down considerably without any hidden data at all.

Do screenshots on Windows or Mac behave differently?

The principle is identical on both: no camera block and no coordinates. Desktop capture utilities are a little more likely to write a software name into the file, and macOS historically attached a note recording the moment of capture.

Does cropping a screenshot remove what I cropped out?

Cropping in the system photo editor normally writes a new file containing only the kept area. Some editors keep a reversible original alongside it, so if you intend the removed region to be gone, export a copy rather than sharing the edited item.

How do I check what is inside a screenshot?

Open it in a metadata reader. Expect a short report: dimensions, format, colour profile and little else. A long report with camera or position entries means the file is not a plain screenshot — most likely a photograph that was saved under a misleading name.

Should I clean screenshots before posting them publicly?

It costs nothing and removes any software note or profile the system attached. Spend most of your attention on the contents though — notification previews, open tabs, account names, balances and the time on the clock give away far more.

Conclusion

So: screenshots are clean where photographs are not, and the reason is structural rather than a feature somebody implemented. No sensor event, no circumstances to record, no coordinates.

Keep the reassurance and discard the complacency. The hidden layer in a screen capture is close to empty; the visible layer is often a direct transcript of your private interface. Crop the status bar, crop the tabs, crop the notification — and give the file itself about ten seconds of thought.

Check a screenshot for yourself — it is read inside your browser, nothing is uploaded, and the viewer never alters the file it opens. Our privacy policy explains exactly what this site does and does not receive.