Is a screenshot evidence?

Not legal advice, and I am not a lawyer. This is about what stands up to a sceptical reader — an opposing party, an auditor, a counterparty's engineer — which is a lower bar than a courtroom and the one most disputes are actually settled at.

What a screenshot establishes

That somebody produced an image showing that text. That is genuinely all. It does not establish when, where it came from, or that the page ever looked like that.

The problem is not that screenshots are usually forged. They usually are not. The problem is the effort required to fake one convincingly: about a minute, in software everybody has. Your counterpart does not have to prove yours was altered — they only have to point out that it could have been, and now you are arguing about your own honesty instead of about the page.

Take screenshots anyway. They are contemporaneous, they capture layout that a raw fetch does not, and they cost nothing. Just do not build a position on one.

How a screenshot gets challenged

• “Anyone could have edited that.” True, and sufficient to create doubt on its own.
• “The metadata is missing or wrong.” Image timestamps come from the machine that made the file and are trivially changed. Uploading to most services strips them entirely.
• “That is not the whole page.” A crop is a selection, and a selection invites the question of what was outside it.
• “Where did this come from?” An image carries no proof of the URL it was taken from. A convincing-looking address bar is a rendered pixel like any other.
• “The page never said that.” Once the original changes, there is nothing left to compare against, and it becomes your word against theirs.

Three free things that make a capture much harder to dispute

Do these before spending anything.

1. Save the source, not just the picture. Use Save page as, or fetch the URL and keep the raw bytes. The response body is what the server actually sent; a picture is what your machine drew afterwards.
2. Hash it, and write the hash somewhere you cannot quietly change. sha256sum page.html takes a second. A hash in an email you sent to yourself, or in a git commit, or in a chat message with a server-side timestamp, binds the content to a moment.
3. Timestamp the hash for free. Submit the digest to an OpenTimestamps calendar. Within about a day it is anchored in a Bitcoin block, and anyone can verify that the content existed by that time. No account, no fee. This single step defeats most “you made this up later” arguments.

What those three cannot do is prove where the bytes came from. You are proving that you held this content on that date — which is often exactly enough, and sometimes the precise thing in dispute.

When you need more than free

Litigation. If this is heading for a court, use a forensic capture service — Page Vault, PageFreezer, Hunchly and similar. They render in a real browser, keep a chain of custody, and a person will sign a declaration about how the capture was made. That declaration is a large part of what a court is weighing, and no amount of hashing substitutes for it.

JavaScript-heavy pages and social media. Same answer. A raw fetch of a single-page app returns a shell with no content in it.

Someone who distrusts you has to accept it. This is the case where your own hash stops being enough, because you made it. What settles it is a record created by a party with no stake — captured by someone else, timestamped by someone else again, and published where nobody can quietly revise it. That is the case Elucora is built for, and the comparison guide sets it against the alternatives honestly.

A short checklist

1. Screenshot, for layout and speed.
2. Save the raw response as well.
3. Hash both, and record the hashes somewhere with an independent clock.
4. Timestamp the hashes with OpenTimestamps. Free.
5. If the dispute is with the person you will be showing it to, get the capture made by someone who is not you.

Steps one to four cost nothing and cover most situations. Step five is the one people skip, and it is the one that decides the arguments that matter.