A bare screenshot is among the weakest forms of digital evidence. The browser's developer tools can edit any visible text in fifteen seconds. Image editors can do the rest. Any opponent in a dispute will, correctly, respond to your screenshot with "you fabricated this." A cryptographic timestamp on the screenshot, captured within minutes of the screenshot itself, cuts off most of that response. It doesn't prove the original page actually said what your screenshot shows — but it does prove that you weren't just now editing it after the dispute began.
The 30-second workflow
- Take the screenshot the normal way.
- Drop the screenshot file into Orphograph. SHA-256 runs locally; the image bytes don't leave.
- Save the receipt JSON in the same folder as the screenshot.
The gap between "I took the screenshot" and "I anchored it" is the window in which an opponent can claim you doctored the image. Keep that window minutes long, not days, and the claim becomes implausible.
What the anchor actually proves
The receipt proves: this exact screenshot file existed by this Bitcoin block time. It does not prove the page you screenshotted ever said what's in the screenshot — that's a separate evidentiary question, addressed by tools like archive.org, the Wayback Machine, and platform-side records. The Orphograph timestamp closes off the "you doctored it after the fact" defense. It does not close off the "you doctored it before the screenshot was taken" defense, which is a different conversation about the source authenticity.
Common use cases
- Harassment documentation. When someone sends threatening DMs and then deletes them, a screenshot anchored immediately after receipt establishes the message existed in your inbox at a specific time.
- Defamation receipts. Public posts get edited or deleted. An anchored screenshot captures the original form.
- Vendor disputes. A pricing page or terms-of-service page that changes mid-dispute. The anchored screenshot documents what the page said when you relied on it.
- Bug reports. A weird UI state that the vendor later denies could have happened. The anchored screenshot is timestamped evidence.
Pair with the rest of the evidence stack
For anything serious, the anchored screenshot is one layer. Additional layers worth collecting at the same time:
- The live URL, copied to a notes file you also anchor.
- A Wayback Machine capture, requested at the moment of the incident.
- Browser developer-tools network logs, exported as HAR and anchored.
- A short text note describing what happened, anchored alongside the screenshot.
Each is cheap. Together they form a corroborating story that's hard to dismiss as fabricated.
What this is not
Not legal evidence on its own. Not authentication of the underlying page. Not source-protection or anonymization tooling. For serious cases, consult an attorney who handles digital evidence.
FAQ
Why does a screenshot need a timestamp?
Screenshots are trivial to fake. Without an independent timestamp, "you fabricated it" is the easy response. An anchor seconds after capture closes off that defense.
Does the screenshot upload?
No. SHA-256 runs in your browser. Only the hash leaves.
How quickly should I anchor?
Within minutes. The shorter the gap, the stronger the claim.
Can I anchor a batch?
Yes. Zip them and anchor the zip; the receipt covers the whole batch.
Is a screenshot timestamp enough by itself in a serious case?
No. Pair it with the live URL, an archive.org capture, and platform-side records. It's a strong layer, not a one-shot proof.