Screenshots get thrown out of court.
ProofSnap doesn't.

ProofSnap is a Chrome 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 independently checkable proof that your evidence existed at a specific point in time.

ProofSnap includes a 7-day free trial with all plans. Choose from flexible monthly or annual subscriptions: Essential ($8.99/month or $80/year), Professional ($16.99/month or $160/year), or Enterprise ($28.99/month or $280/year). 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 with legal professionals for specific cases.

Regular screenshots can be challenged in court because they lack proof of when they were taken and whether they've been altered. Courts increasingly require authentication under rules like FRE 901/902 (US) or equivalent rules in other jurisdictions.

ProofSnap addresses these challenges by creating a forensic evidence package that includes: a SHA-256 cryptographic hash proving the content hasn't been modified, a digital signature for authenticity, a blockchain timestamp proving when the capture occurred, and full metadata (URL, browser info, TLS certificate). This makes your screenshot significantly more defensible than a plain image file.

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 detble.
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, qualified electronic timestamps enjoy a legal presumption of the accuracy of the date and time they indicate and of the integrity of the data to which the timestamp is linked. The presumption covers date, time and integrity; whether the underlying evidence is admitted remains a matter for national procedural law.

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. This makes ProofSnap evidence packages suitable for legal proceedings in the United States and across the EU.

Forensic mode is an opt-in capture depth included in the Professional, Enterprise and Company plans (not in Essential or the SnapPacks). A standard capture documents what the page showed. Forensic mode also documents how the browser got it, by archiving the entire network layer of the load:

• capture.warc, a WARC 1.0 web archive of the load, including the redirect hops most tools drop silently
• network.har, an HTTP Archive 1.2 log of every request and response with full headers and timings
• resources/ plus resources.json, every loaded resource written to its own file with its own SHA-256 hash
• certificate_details.json, the real TLS session: protocol, cipher suite, key exchange, issuer, subject, validity window, SAN list and Certificate Transparency compliance

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.

Reach for it when the transport itself is in dispute: a phishing redirect chain, a resource served from a CDN that later changed, a paywall or geoblock you need to prove, or a certificate that expired after the capture. To record all of that, Chrome reloads the page under the DevTools protocol and displays its standard "being debugged" banner for the duration of the capture. The screenshot, HTML and DOM text are taken before that reload, so your authenticated view of the page is preserved as you saw it.