Screenshots get challenged in court.
ProofSnap shows what the page said, and when.

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, and it shows that your evidence existed no later than that point.

ProofSnap includes a 7-day trial with all plans (credit card required). 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%. Every plan and SnapPack is broken down in ProofSnap plans and prices explained.

Yes. In the ProofSnap Dashboard at app.getproofsnap.com you paste one or more URLs and our servers load the pages and return the same sealed evidence package. It works for public pages; for a page behind a login or paywall, use the extension. A new dashboard account starts with 50 free test captures, and the dashboard and the API have their own plans, separate from the extension.

Each ProofSnap capture carries a SHA-256 hash for every file, an RSA-4096 signature and a chain of custody, and on the eIDAS plans a qualified electronic timestamp from Disig a.s. Whether a court admits it depends on the jurisdiction and the case, so ask a lawyer about your specific matter.

Regular screenshots can be challenged in court because they lack proof of when they were taken and whether they've been altered. Courts require authentication under the rules of evidence, in the US and elsewhere.

ProofSnap addresses these challenges by creating a forensic evidence package that includes: a SHA-256 cryptographic hash showing any later change, a digital signature over the file list, a blockchain timestamp showing the capture existed no later than a given moment, and full metadata (URL, browser info, HTTP headers). This makes your screenshot significantly more defensible than a plain image file. The whole workflow is shown screen by screen in how to capture a web page as evidence.

Yes. Open each listing or storefront in Chrome or Edge and capture it: ProofSnap saves the full page as a screenshot and as HTML, records the URL, DNS, WHOIS and server headers with an NTP-verified time, hashes every file with SHA-256 and signs the manifest. Session mode captures several tabs into one package, so a whole set of listings travels as a single ZIP you hand to your attorney, and anyone can verify it for free. ProofSnap records what each page showed; it does not identify who runs the store. For the wider playbook, see brand protection evidence for e-commerce.

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 later change 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, showing that the evidence existed no later than that moment. Anyone can verify the anchor independently.

Together, these mechanisms create a chain of integrity that shows the package has not changed and existed at that point in time. Anyone can check this; see how to verify a ProofSnap evidence package.

eIDAS 2, the 2024 amendment of the eIDAS Regulation, is mainly about the European Digital Identity Wallet. For timestamps, the rule that matters did not change.

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.

On the eIDAS plans ProofSnap adds a qualified timestamp from Disig a.s. to the SHA-256 hashing, the RSA-4096 signature and the OpenTimestamps anchor, so each package is built for proceedings in both the United States and 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. Step by step: how to use forensic mode.