A screenshot is a photograph of a screen, taken at one moment, by one person, for a reason. That is all it is. It can inform, and often does, but it usually strips away the three things a record needs most: the date, the source, and the surrounding context. This reference lays out the difference between an image of information and a record of it, and what to do when an image is all you have.
The habit that follows from everything below is short and slightly unpopular. Ask for the original link or document before spreading a claim. People will sometimes take offense. Ask anyway.
What a record is built to do
Public records are not just documents that happen to be public. They are documents kept under rules. In the United States, the federal Freedom of Information Act has been in force since 1967. It lets anyone request records from federal agencies, and agencies must release them unless one of nine exemptions applies, covering interests like personal privacy and national security. FOIA.gov, the government's portal, explains the basics. Every state has an open-records law of its own for state and local bodies, with different names, deadlines, and exceptions.
Look at what that machinery quietly guarantees. A record has a custodian, a person whose job is keeping it. It has a creation date. It sits in a known system where it can be found again, compared against earlier versions, and corrected through a process that itself leaves a trace. None of this is glamorous. All of it is the point.
What a screenshot actually carries
Now inventory the screenshot. It carries pixels. Sometimes a username. Sometimes a fragment of a timestamp, rendered in the local clock of whoever captured it. Rarely a URL. Never the replies above and below, the edit history, the correction posted an hour later, or the fact that the account was deleted the next day.
Two failure cases show up constantly, and neither needs a villain. A city notice screenshot without a date can restart a solved panic; last year's boil-water advisory recirculates every time someone rediscovers it in a camera roll. And a cropped image can be technically real and still misleading; the sentence was truly typed, but the reply that reframed it was cut away. Ordinary sharing does this damage on its own.
Deliberate forgery, meanwhile, costs nothing. The developer tools built into every browser let anyone rewrite the visible text of a page in seconds and capture the result. No special skill, no special software. A screenshot of a post proves that pixels were arranged, and little more.
Side by side: kept record versus captured image
When a screenshot arrives making a claim, run it against this table. The left column is the question a careful reader is really asking.
| Question | A kept record | A typical screenshot |
|---|---|---|
| Source | Named custodian and system of origin | Whoever forwarded it to you |
| Date | Creation date recorded and checkable | The capturer's clock, if visible at all |
| Completeness | Full document, prior versions, surrounding context | One crop of one moment |
| Verification | Request the original and compare | Trust it, or go hunt for the source yourself |
| Correction | Errors amended through a process, on the record | Wrong copies circulate forever, unamended |
Try the table on a familiar scene. A neighbor drops an image into the block chat: a letter, apparently from the city, announcing new parking fees. Source? A cousin who "works downtown." Date? The letterhead is cropped. Completeness? One paragraph of what was clearly a longer page. Verification? The city posts its fee schedule online, so two minutes of checking would settle it. Correction? If the letter turns out to be last year's withdrawn proposal, no take-back message will chase down every phone it reached. Nothing about the neighbor is dishonest. The format is.
Even the Library of Congress went selective
Completeness is harder than it looks, even for professionals whose entire job is keeping things. In 2010 the Library of Congress set out to archive every public tweet ever posted. In December 2017 it announced that it would stop, and collect only on a selective basis going forward, focusing on chosen events and themes. The volume had grown past what the project could absorb, and the platform had changed the format underneath them, doubling the character limit that same year.
Sit with that for a second. The national library of the United States, staffed with trained archivists, concluded that a complete public copy of one platform was out of reach. Your camera roll will not do better. The record that matters, the notice, the policy, the meeting minutes, should live somewhere designed to keep it, not in a thousand partial photographs of it.
Five questions for any screenshot you receive
- Where is the original? A link, a document, a page that loads. If the sender cannot produce one, that is information too.
- When was it captured, and when was the underlying thing posted? Those are two different dates, and confusing them is how old panics get reheated.
- What sat just outside the crop? The question above the answer, the thread before the quote, the correction underneath.
- Does the source still say this? Search the exact wording. Deletions and edits matter, and both are invisible in a static image.
- Who benefits if you pass it along unchecked? Not always a sinister answer, but always a clarifying one.
If you pass one along
Sometimes a screenshot really is the best available evidence: the post was deleted, the page sits behind a paywall, the chat was private. Fine. Then share it like a careful person. Attach the original link even if it is now dead. State when you captured it and where it came from. Say plainly what you know and what you are assuming. You are not weakening your point with those caveats; you are signing it.
And when the original still exists, do the stronger thing. Forward the link, not the image. Save the page to an archive service so the address outlives the source. A screenshot is a rumor with better typography, and the old discipline for rumors still applies: treat it as a lead worth checking, never as a record worth keeping.