Authentication now comes first
A screenshot used to be accepted almost by default. In 2026 the first question a careful opponent asks is different: can anyone check where this image came from, when it was made and whether it has been changed since? Editing and generative tools have made a convincing fake a matter of minutes, and courts know it.
This guide is for litigation lawyers, in-house legal teams and forensic experts who rely on web content as evidence. It explains what authenticating a screenshot involves in practice, what two recent decisions show, and how to prepare web evidence so that the other side can verify it rather than simply dispute it.
Two 2026 decisions, two sides of the same problem
In Lodhia v Twelve Trees (Bromley-By-Bow) Management Company Ltd [2026] EWHC 1889 (KB), the High Court found that a litigant had put forward fabricated or altered documents, among them a doctored university e-mail and an altered court order, and rejected his explanations, which repeatedly blamed artificial intelligence tools. The court imposed a civil restraint order. The documents were not web captures, but the lesson carries over: a digital exhibit is examined, not presumed.
In the Netherlands, the preliminary relief judge of the District Court of North Holland (28 October 2026, ECLI:NL:RBNHO:2026:14782) dealt with forensic reports showing that former employees had copied company files to external storage and sent files to outside e-mail addresses. An appeal court had earlier refused to rely on those reports because the other side had not been heard on them. With later information, the judge held that the principle of hearing both sides (hoor en wederhoor) had not been breached: the former employees had repeatedly been given the opportunity to ask questions about the findings, had not instructed their own IT expert and had not made all requested data carriers available. The findings were not unusable.
Together the two cases mark the line. Evidence that cannot be checked invites suspicion; evidence the opponent was able to examine, and did not effectively challenge, is much harder to set aside. Neither decision concerned a particular capture tool, and neither suggests that any technology guarantees acceptance.
What authenticating a screenshot really means
Whatever the procedural label, a court or expert asking whether a web capture is authentic is in practice asking four questions:
- Provenance: which URL was captured, by whom, with which tool and from which network location?
- Time: when exactly was the page in that state, and how is that time established independently of the person who made the capture?
- Integrity: has anything in the files changed since the moment of capture?
- Context and completeness: does the capture show the whole page, the surrounding thread or listing and the steps that led to it, or only a cropped fragment?
Why the image alone cannot answer them
A PNG or JPEG carries almost no reliable information about itself. File dates change when the file is copied, EXIF fields can be edited, and the clock visible on a phone screen is simply part of the picture. Pixel-level checks for editing help to spot crude fakes, but a clean result does not show where an image came from or when it was made.
That is why serious methods add material around the image: the page source code, network records, certificate and DNS data, a description of the method, and a cryptographic fingerprint (hash) of every file, fixed at a known and independently provable time. The question shifts from whether the picture looks right to whether the package is consistent with itself and with independent records.
What the procedure gives you to work with
Rules differ by jurisdiction, but several reference points are worth knowing:
- England and Wales: under CPR 32.19 a party is deemed to admit the authenticity of a disclosed document unless it serves notice that it wants the document proved at trial, by the latest date for serving witness statements or within 7 days of disclosure, whichever is later. Expect such notices for screenshots that matter.
- Council of Europe Guidelines on electronic evidence (2018, non-binding): courts should be aware of the probative value of metadata (Guideline 8) and of the value of trust services in establishing reliability (Guideline 20); electronic data should be accepted unless its authenticity is challenged, as far as national law permits (Guideline 21).
- Netherlands: as ECLI:NL:RBNHO:2026:14782 shows, whether the other side had a real opportunity to examine and question forensic findings can decide whether those findings are used at all.
- EU: under eIDAS Article 41(2) a qualified electronic timestamp enjoys the presumption of the accuracy of the date and time it indicates and of the integrity of the data to which they are bound; under Article 41(3) it is recognised as such in all Member States.
Checklist: web evidence that can be checked
Before a web capture goes into a bundle or an expert report, it should come with:
- The exact URL, the capture time and the identity of the person or service that made the capture.
- More than an image: the HTML source, a network log (HAR), TLS certificate and DNS records, and for dynamic pages a video or MHTML copy.
- A SHA-256 hash of every artefact, listed in one manifest.
- A trusted time for that manifest, ideally a qualified electronic timestamp (RFC 3161) from a qualified trust service provider on the EU trusted lists.
- A written record of the method: browser, viewport, logged in or not, cookie banners handled, overlays hidden.
- Instructions that the opponent or a court expert can follow to verify the package without having to contact you.
Let the other side verify – and record that you offered it
The Dutch decision rewards openness. If the opponent can recompute the hashes, check the timestamp token against the trusted list and compare the capture metadata with the visible content, a vague objection that the screenshot might have been manipulated carries little weight. Offer that possibility early, in writing, and keep a record that you did.
In practice this means disclosing the package in its native electronic format rather than as a printout, naming the verification tool and keeping the original files unchanged. Open-source verifiers that work offline are particularly useful, because nobody has to trust the provider of the capture service.
Matching the tool to the case
GetProofAnchor offers three routes. Each binds the captured artefacts into a qualified eIDAS timestamp from an EU-listed qualified trust service provider:
- Forensic Browser (Windows, annual licence from 290 EUR excl. VAT): browse normally and capture a whole session, including logged-in pages, into one sealed package with screenshots, HTML, HAR, DNS, TLS chain and documented methodology. Output as a PDF whose embedded timestamp validates in Adobe Acrobat Reader, or as a ZIP verifiable with the open-source gpa-verify.
- Web app (from 9 EUR excl. VAT, 10.89 EUR incl. 21 % VAT, for 3 proofs; monthly plans from 19 EUR excl. VAT): server capture by URL with screenshot, HTML, MHTML, video, HAR, TLS, DNS and WHOIS, each hashed, delivered as an Evidence ZIP that includes the trusted list snapshot for offline verification. Server captures are made by our infrastructure, not your device; captures through the browser extension are made on your device and sealed on receipt.
- Assisted Capture (Single 49 EUR excl. VAT, 59.29 EUR incl. VAT, within 90 minutes; Rush 249 EUR excl. VAT with a guaranteed 60 minutes): an operator captures the URLs for you and sends the evidence package by e-mail.
What a timestamp does not prove
A qualified timestamp fixes the time and protects the integrity of the timestamped data. It does not make the content true, it does not show who wrote a post, and it does not by itself prove that every visitor saw the same page, because content can differ by location, login or personalisation. Admissibility and weight remain for the court. What a well-documented, verifiable package does is remove the easy objection and move the debate to the substance of the case.
FAQ
Is a screenshot admissible as evidence?
How do I prove a screenshot is authentic?
What did the Dutch court decide in ECLI:NL:RBNHO:2026:14782?
Does a qualified timestamp make my evidence admissible?
Can the other side verify a GetProofAnchor package without us?
Sources
- Lodhia v Twelve Trees (Bromley-By-Bow) Management Company Ltd [2026] EWHC 1889 (KB) – National Archives
- Solicitors Journal – High Court imposes civil restraint order over fabricated evidence (Lodhia)
- IE-Forum – Rechtbank Noord-Holland 28 October 2026, ECLI:NL:RBNHO:2026:14782
- Civil Procedure Rules, Part 32 (rule 32.19)
- Council of Europe – Guidelines on electronic evidence in civil and administrative proceedings (2018)
- Regulation (EU) No 910/2014 (eIDAS), Article 41
For lawyers and legal teams
Evidence the other side can’t easily dismiss
Forensic web capture with an eIDAS qualified timestamp, Bitcoin anchor and an offline-verifiable Evidence ZIP — methodology designed with reference to ISO/IEC 27037. File it as a data package and a PDF report.
Related guides
-
Forensic BrowserCapture whole sessions, including logged-in pages, into one sealed package.
-
Verify a proofCheck an Evidence ZIP online or offline with gpa-verify.
-
What courts actually look for in online evidenceThe criteria judges apply to web captures.
-
How to tell if a screenshot is fakeSpotting manipulated images – and proving yours is real.
-
Why screenshots are not enoughThe limits of a plain screenshot in court and compliance.
-
Assisted CaptureWe capture the URLs for you, from 49 EUR excl. VAT.
Web evidence the other side can verify
Capture the page with a qualified eIDAS timestamp and hand over a package anyone can check offline. Write to sales@getproofanchor.com for a free sample proof of a URL from your case.
Prices excl. VAT; consumers pay 21 % CZ VAT. No admissibility guarantee – the court decides.