01

What we checked

The files were validated as PNG by signature, then inspected for EXIF, GPS, XMP, ICC and textual chunks. Pixel dimensions were read directly from the PNG header.

Key points
  • Real format, not extension alone
  • Location-related fields
  • Software and text metadata
  • Image dimensions
02

The safe conclusion

Say that no supported location metadata was detected in these samples. Do not claim every Windows screenshot is metadata-free, because capture and editing tools can change the output.

03

The test question and sample boundary

We asked a narrow question: did these three PNG screenshots contain readable EXIF, GPS, XMP or related text evidence? The files were ordinary Windows screen captures with different dimensions, not downloaded stock images or generated metadata demonstrations.

A three-file sample cannot establish the behavior of every Windows version or screenshot program. The article therefore reports each file and preserves “not detected” wording instead of saying Windows screenshots are metadata-free.

Key points
  • Real files, small sample
  • PNG signature verified
  • Supported metadata groups inspected
  • No universal platform claim
04

How each file was inspected

The analyzer checked the real signature before trusting the .png extension, read width and height from the header and scanned supported EXIF, XMP, ICC and text paths. The files stayed in the local browser and were not uploaded for server analysis.

The same release code used by the public screenshot checker produced the observations. We retained dimensions and result categories but not the screenshot pixels in the repository, because publishing private screen content is unnecessary to support the claim.

05

What the results say

All three files exposed basic structure and dimensions. None returned a supported GPS coordinate, EXIF camera block or XMP location field. That makes the tested copies less likely to leak location through those metadata paths.

The result does not prove they contained no ancillary chunk unknown to the parser, nor does it prove another application will behave the same. “Not detected in three tested files” is the complete conclusion.

06

Visible content remains the main review

One screenshot can show an address, email, open document, account name, authentication code or private message directly in the pixels. Metadata analysis cannot redact those details or understand their social context.

Inspect the entire frame, crop unnecessary areas and create a flattened redaction. Then test the final exported file again because an annotation tool may add software or text metadata.

07

How to repeat the check on your own device

Create screenshots with the capture tools you actually use: system shortcut, Snipping Tool, game capture and any annotation app. Analyze the untouched capture and the edited export separately.

Record operating-system version, application version, output format and observed fields. A small personal matrix is more useful than a generic internet claim because it matches the workflow that will handle your files.

08

Questions the sample cannot answer

The test does not determine whether Windows keeps additional information in a cloud library, recent-files database or filesystem attributes. It only inspects the selected PNG bytes. It also cannot establish behavior for Xbox Game Bar, third-party capture utilities or future Snipping Tool releases.

Those limits are part of the result, not a weakness to hide. If your use case involves confidential screens, repeat the procedure on every capture and annotation path that touches the file.

Key points
  • No filesystem forensics
  • No cloud-library database inspection
  • No cross-version prevalence estimate
  • No automatic visible-content redaction
  • No claim about every Windows capture tool

What this does not prove

A metadata result describes the fields and structures that the supported parser could read. It does not, by itself, prove authenticity, intent, authorship or the truth of the visible scene.

Sources