Skip to main content
← Back to all articles

Forensic web capture methods compared: what each one proves and when to use it

The method you choose decides what the other side can attack. Seven ways to preserve a web page, compared honestly, with a decision guide for lawyers, investigators and experts.

Forensic capture Methods eIDAS Litigation

Why the method matters more than the tool

When web evidence is challenged, the attack rarely targets the picture itself. It targets the method: who made the capture, on which device, what was left out, and whether anyone can show the files were not changed afterwards. Two captures of the same page can carry very different weight because they were made in different ways.

This guide compares the methods, not the vendors. If you are already choosing a product, our buyer's guide covers the vendor questions. Here the question is simpler: for this page, in this case, which method gives the strongest record, and what will it not prove?

Four questions that separate the methods

Every method can be tested against the same four questions. Keep them in mind for each section below.

  • Who observed the page: you on your own device, an independent system, or a third person such as an operator or a notary?
  • What was preserved: only an image, or the page source, network traffic, certificates and a video of the page loading?
  • How was it sealed, and by whom: are the files fixed in time by someone other than the person holding them?
  • Who can verify it: can a judge, an expert or the other side check it without trusting you or the vendor?

Screenshots and print-to-PDF

The fastest method and the weakest. A screenshot is made on your own device, shows only what was on screen, and carries no independent proof of time or integrity. It is easy to edit and, more importantly, easy for the other side to say it was edited. Print-to-PDF keeps a little more text but changes the layout and drops most of the context.

Use it as a placeholder, not as the record. If the page may disappear in minutes, take the screenshot, then make a proper capture as soon as you can and keep both.

Web archives such as the Wayback Machine

A public web archive is useful when the page is already gone: it may hold a copy you never made yourself. But you do not control when or whether a page was archived, archived pages can be incomplete or assembled from resources fetched at different times, and you depend on the archive's own records to explain what happened. Treat an archive copy as a lead and corroboration, and capture the current state yourself whenever the page still exists.

Notary, bailiff or IT specialist

Having a third person record the page is the classic answer in many European jurisdictions, for example a report drawn up by a notary or, in France, a constat by a commissaire de justice. The explanatory memorandum to the Council of Europe Guidelines on electronic evidence notes that parties are responsible for proper collection and that in important matters they should consider capturing evidence with the support of an IT specialist or notary services.

The strength is the independent observer. The limits are time and cost: an appointment can take days, each page adds work, and the report is only as technical as the person making it. For a page that may vanish tonight, or for fifty listings, this route is often too slow.

Server capture by URL

You submit a URL and the vendor's infrastructure, not your device, loads the page and records it. A good server capture preserves several independent artifacts, each hashed: full-page screenshot, HTML, an MHTML snapshot, a HAR file of the network traffic, a video of the page loading, the TLS certificate chain and DNS results, with every intervention such as a cookie-banner click recorded in the metadata. The hashes are then sealed with a timestamp.

Its strength is independence from your device. Its limit is access: a server cannot log in as you, so closed groups, accounts and many interactive apps are out of reach. Check also whether captures are public or private by default, because a public proof page may not suit a confidential matter.

Browser extension capture

An extension records the page in your own browser, which means it can capture what you see after logging in. The package is then uploaded and sealed on receipt. That is the honest description: the seal proves the integrity of the package and the time it was received, not that an independent party observed the content.

That makes it a practical tool for logged-in pages you can open yourself, and a weaker one when the other side argues that your device or account shaped what was shown. Record which account was used and why the extension was necessary.

Forensic browser on the desktop

A forensic browser is a dedicated desktop application: you browse normally, and the whole session, including many subpages and logged-in content, goes into one sealed package with its methodology documented. Compared with an extension it can also preserve what a single page capture misses, such as videos, downloaded files and multi-step journeys like a test purchase.

The output matters for the reader. A PDF with an embedded qualified timestamp in the PAdES format (ETSI EN 319 142) can be validated in Adobe Acrobat Reader by a judge or opposing counsel without any extra software, while a ZIP with a hash manifest suits experts who want every raw file. It is still your browser on your computer, so the same caution about who observed the page applies.

Done-for-you capture by an operator

An operator captures the pages for you and sends the evidence package. This adds a person who is not a party to the dispute, it works when you have no time or no technical setup, and an operator can use their own accounts for content visible only to logged-in users. The questions to ask are the delivery time, whether it is guaranteed, and which capture method the operator uses, because the package should say so.

Which method for which situation

In practice the situation picks the method. A short guide:

  • One public page that may disappear today: server capture by URL now, or a done-for-you rush capture if you cannot do it yourself.
  • A closed group, a private profile or an account page: forensic browser or browser extension, or an operator with their own account.
  • A whole storefront, a seller with dozens of listings or a test purchase: a forensic browser session, so everything sits in one package with one timestamp.
  • A video or a document linked from the page: a forensic browser, which can seal the file itself alongside the page.
  • A page that already disappeared: a web archive as a lead, then everything that still exists captured properly.
  • A high-stakes matter with time to prepare: an independent observer such as a notary or IT specialist, combined with a technical capture.

Combining methods in one case file

Strong case files rarely rely on one method. A typical combination:

  • a server capture of each public page, made as early as possible
  • a forensic browser session for the logged-in and multi-step parts
  • a repeat capture on a schedule if the content keeps changing
  • a short note per capture: who made it, when, with which method and account

Whatever you combine, the seal is what ties the files to a moment. In the EU the standard instrument is a qualified electronic timestamp under the eIDAS Regulation. Under Article 41(2) it 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, and under Article 41(3) it is recognised in all member states. The presumption covers time and integrity, not the truth of what the page says.

Where GetProofAnchor fits

We offer three of these methods, each sealed with a qualified eIDAS timestamp from an EU-listed qualified trust service provider and verifiable offline with the open-source gpa-verify:

  • Forensic Browser (Windows desktop app): whole sessions, logged-in pages, videos and files in one package, as a PAdES PDF that validates in Adobe Acrobat Reader or as a ZIP for experts. Annual licence from 290 € excl. VAT (350.90 € incl. 21 % VAT).
  • Web app: server capture by URL with screenshot, HTML, MHTML, HAR, video, TLS and DNS in one Evidence ZIP, plus a browser extension for logged-in pages. From 9 € excl. VAT for 3 proofs (10.89 € incl. VAT); for scheduled repeat captures, Business with 10 monitors at 99 € per month excl. VAT.
  • Assisted Capture: an operator captures the URLs for you, Single from 49 € excl. VAT (59.29 € incl. VAT) within 90 minutes, Rush up to 5 URLs with a guaranteed 60 minutes for 249 € excl. VAT (301.29 € incl. VAT).

No method guarantees that a court will accept the evidence; that is for the court. If your team captures web evidence regularly, the Forensic Browser is usually the method that covers the most situations. Ask us for a free sample proof of a URL from one of your own cases and compare it with what you use today.

Frequently asked questions

What is the most reliable way to capture a web page as evidence?
There is no single best method. For public pages a server capture independent of your device is strong; for logged-in or multi-step content a forensic browser session is usually needed. In both cases the files should be sealed with a qualified timestamp and be verifiable without the vendor.
Is a browser extension capture weaker than a server capture?
It proves something different. An extension records what your own browser showed and the package is sealed on receipt, so the seal proves integrity and the time of receipt, not independent observation. A server capture is made by independent infrastructure but cannot reach content behind your login.
Do I still need a notary or bailiff?
Not for every page. A third-person report adds an independent observer and can make sense in high-stakes matters, but it is slower and costs more per page. Many teams combine a technical capture made immediately with a third-person report where the stakes justify it.
Can I rely on the Wayback Machine instead of capturing the page myself?
Only when the page is already gone. You do not control when an archive copy was made or how complete it is. If the page still exists, capture it yourself and use the archive as corroboration.
What does a qualified timestamp actually prove?
Under Article 41(2) of the eIDAS Regulation it carries a presumption of the accuracy of its date and time and of the integrity of the data bound to it. It does not prove that the content of the page is true or who wrote it.

Sources

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.

Test the method on your own case

Ask for a free sample proof of a URL from one of your cases, or start with 3 proofs for 9 € excl. VAT (10.89 € incl. VAT).

Qualified eIDAS timestamp on every paid proof. Offline verification with the open-source gpa-verify.