Screenshots get challenged in court.
ProofSnap evidence gets checked.

ProofSnap is a Chrome and Edge extension that captures web pages as legal evidence with blockchain timestamping, ensuring the authenticity and integrity of digital evidence.

ProofSnap uses OpenTimestamps to anchor a SHA-256 hash of your evidence to the Bitcoin blockchain, creating a cryptographic proof of when the capture was made. This timestamp is independently verifiable and cannot be backdated or tampered with, providing proof that your evidence existed at a specific point in time.

ProofSnap includes a 7-day free trial with all plans, and the trial requires a credit card. Choose from flexible monthly or annual subscriptions: Essential ($8.99/month (about £7) or $80/year (about £60)), Professional ($16.99/month (about £13) or $160/year (about £120)), or Enterprise ($28.99/month (about £22) or $280/year (about £210)). Annual plans save up to 26%.

ProofSnap generates forensically sound evidence with cryptographic proofs aligned with eIDAS 2 standards for qualified timestamps and digital signatures. Admissibility depends on jurisdiction and specific legal requirements. Consult a legal professional about your specific case.

Regular screenshots can be challenged in court because they carry no proof of when they were taken or whether they have been altered. In the United Kingdom the answer to that is unusually strong. The trust services chapter of eIDAS is now UK assimilated law, and Article 24A of the assimilated Regulation treats an EU qualified service as qualified here for the purposes of Article 41(2): a qualified electronic time stamp enjoys a rebuttable presumption of the accuracy of the date and time it indicates and the integrity of the data to which it is bound. Alongside that, in England and Wales the Civil Evidence Act 1995 governs proof of statements in documents and section 9 covers business records, while under the civil procedure rules the authenticity of a disclosed document is deemed admitted unless the other side serves a notice to prove it, by the deadline for witness statements or within 7 days of disclosure, whichever is later.

ProofSnap addresses this by creating a forensic evidence package containing a SHA-256 hash proving the content has not been modified, an RSA-4096 digital signature for authenticity, an eIDAS qualified timestamp issued by Disig a.s., a Qualified Trust Service Provider on the EU Trusted List, a Bitcoin blockchain anchor, and full metadata including the URL and the capture time in UTC. The presumption goes to the time and the integrity of the data rather than to admissibility in the round, so a court still applies the CPR and weighs the evidence. What it removes is the argument about when the capture was made and whether it changed afterwards.

Yes, and the small claims track is where it tends to matter most, because you present the evidence yourself with no solicitor to argue authenticity for you. Put the signed PDF in the bundle as your exhibit and keep the ZIP available. The PDF is readable on its own, so a district judge does not have to run anything to follow it, and the hashes and the manifest are there if the other side says the page never said what you claim.

The practical advantage is that a small claim is usually decided at a short hearing, on the documents the parties have filed. There is no time to reconstruct what a listing, an advert or a chat said months ago, and the party who can produce the page as it stood, with the date fixed by something other than their own word, is in a materially better position than the party describing it from memory. This describes the small claims track of the County Court in England and Wales; the simple procedure in Scotland and the small claims procedure in Northern Ireland are separate regimes.

No. Nothing in the Civil Procedure Rules or the law of evidence requires a web page to be notarised before a court in England and Wales will look at it. Under the notice-to-prove rule the authenticity of a disclosed document is deemed admitted unless the other side serves a notice to prove it, so in most cases the question never arises at all.

A notary helps only in a narrow band of cases, and it is worth understanding what one actually gets you. A notary attests what was shown to them, on the day, in their presence. They do not hash the file, so nothing in the certificate lets anyone check months later that the copy you are producing is byte-identical to the one that was certified. They charge per document, and getting an appointment takes long enough that a page can be edited or deleted while you wait.

A ProofSnap package attacks the same problem from the other end and does so in seconds: a SHA-256 hash of every file, an RSA-4096 signed manifest, the public key in the package, a chain of custody, an OpenTimestamps anchor and, where the plan includes it, a qualified timestamp carrying the eIDAS presumption in UK assimilated law. If your matter needs a notary for some separate reason, the two are not alternatives and you can do both.

Whether to apply is a question for your solicitor. What to preserve first is not, and it is the step that gets skipped. An application to identify an anonymous poster takes weeks, and the account can be deleted before the order is granted, whether by the poster, the platform or a moderator. If that happens you may end up with an order and nothing left to attach it to.

Capture the material before you do anything that alerts the poster: the post itself, the full thread or comment chain around it, the account profile with its handle, display name, join date, follower count and any other posts you may need, and the URL of each. Capture the page as it appears to the public rather than only to you. Do the same for any republication you have found, because reach matters to a defamation claim and a republication may be gone before disclosure. Then instruct your solicitor. The jurisdiction described here is England and Wales; the equivalent order in Scotland is sought under a different procedure.

ProofSnap uses three layers of cryptographic protection:

1. SHA-256 Hashing: Every file in the evidence package is hashed. Changing even a single pixel or character produces a completely different hash, making any tampering immediately detectable.
2. Digital Signature: The manifest (listing all files and their hashes) is digitally signed with a private key. The corresponding public key is included for anyone to verify authenticity.
3. Blockchain Timestamp: The manifest hash is anchored to the Bitcoin blockchain via OpenTimestamps, creating an immutable record of when the evidence was captured. This timestamp cannot be forged or backdated.

Together, these mechanisms create a chain of integrity that proves the evidence is authentic, unaltered, and was captured at a specific point in time.

The eIDAS 2 regulation (EU 2024/1183) will be fully rolled out by the end of 2026, establishing stricter standards for electronic identification, digital signatures, and qualified electronic timestamps across all EU member states.

Under Article 41, a qualified electronic timestamp enjoys a rebuttable presumption of accuracy for the date and time it indicates and the integrity of the data to which the timestamp is linked, and Article 41(1) stops a timestamp being denied legal effect and admissibility as evidence merely because it is electronic. Admissibility itself still follows each court's own procedural rules, which in the United Kingdom means the CPR in England and Wales and the equivalent rules in Scotland and Northern Ireland.

ProofSnap's cryptographic proofs align with eIDAS 2 requirements: SHA-256 hashing for data integrity, RSA-4096 digital signatures for authenticity, and blockchain timestamps via OpenTimestamps for independent time verification. In the United Kingdom the recognition runs through the assimilated Regulation, not through eIDAS 2, which does not extend to the UK.

Forensic mode is an opt-in capture depth included in the Professional, Enterprise and Company plans (not in Essential or the SnapPacks).

Adds a complete archive of the page's network layer: every HTTP request and response (network.har), a WARC copy of the page, all loaded resources, and the full TLS certificate chain. To capture that it attaches the debugger (the browser shows a “being debugged” banner).

Every one of those files is hashed into the RSA-4096 signed manifest, so the OpenTimestamps blockchain anchor and the eIDAS qualified timestamp cover the network archive exactly as they cover the screenshot.