Digital literacy · 2026-10-29
What an Error Screenshot Shows—and What It Leaves Out
A screenshot can preserve an error message, but it usually cannot establish the cause, the duration or how many people were affected. Read the full message before turning one image into…
A screenshot can preserve an error message, but it usually cannot establish the cause, the duration or how many people were affected. Read the full message before turning one image into a service-wide conclusion.
Read what is present
Check whether the image includes the complete message and useful context. A cropped line may omit a qualifier. A visible device clock may provide context, but it is not automatically a verified service timestamp. Describe the image accordingly.
Do not count copies as separate incidents
The same screenshot forwarded into ten conversations still represents one source image. It does not establish ten independently observed failures. Separate reports need their own provenance and observation times.
Preserve changes chronologically
If a later screenshot shows a different status, keep both with their respective context. The later image does not erase the earlier observation. Together they may show a change, while still leaving the cause unknown. Avoid publishing account identifiers in either image. This approach supports a precise incident account without declaring a service-wide outage from a single picture.
Cropping can change the apparent meaning
A line reading “temporarily unavailable for this request” becomes a much broader claim if a crop leaves only “unavailable”. Preserve the complete sentence in a private original and share a redacted copy that keeps its qualifiers. Removing account details is different from removing words that limit the message's meaning. A clear image should protect privacy without changing the evidence.