GPA
GetProofAnchor
Tamper-evident proof records for public URLs
Sign in
← Back to tutorials

Evidence ZIP explained (what’s inside)

In short: Evidence ZIP is a portable package you can archive or attach to a case file — and later prove it was not altered.

An Evidence ZIP bundles captured artifacts (like screenshot + extracted content) together with a cryptographic manifest (SHA-256) so integrity can be verified later.

Tutorial Evidence ZIP SHA-256 Verification ~4 min read
Quick overview

Evidence ZIP is the shareable “evidence package”. It includes files (artifacts) + a SHA-256 manifest. That’s what makes later verification strict and trustworthy.

1) What it is
Portable evidence package
2) What’s inside
Artifacts + metadata
3) Manifest & hashes
Why edits can’t pass
4) Sharing rules
How to keep it valid

What is an Evidence ZIP?

Evidence ZIP is a file you export from a proof. It’s designed for situations where evidence must leave your account: you want to archive it, attach it to a case file, or share it with third parties.

The key feature is not “just export” — it’s that the package can later be verified to prove it is original and unchanged.

What’s inside (typical contents)

An Evidence ZIP generally contains captured artifacts plus metadata about the capture. Exact filenames can vary, but the idea is consistent: reviewers get what was captured, plus integrity information.

Common artifacts inside the ZIP
  • full-page screenshot (what the page looked like)
  • extracted text/content (what was readable on the page)
  • proof metadata (URL, capture timestamp, capture details)
  • manifest file (list of files + SHA-256 hashes)

Why the manifest matters (SHA-256)

The manifest is a simple but powerful idea: it lists every file in the ZIP and the file’s SHA-256 hash. A hash is like a fingerprint — if the file changes, the fingerprint changes.

That’s why verification is strict: editing extracted text, modifying a screenshot, replacing or recompressing files — anything — will change hashes and fail verification.

Best practices for sharing Evidence ZIP

  • Share the ZIP exactly as exported (don’t re-zip or “clean it up”).
  • Store a copy in read-only storage if possible.
  • When attaching to a case file, keep the Proof ID and capture timestamp in notes.
  • If someone needs to review it, ask them to verify the ZIP first.
Try it now

Export an Evidence ZIP from a proof, then verify it. You’ll immediately see how strict integrity checks are.

Create proof → Verify ZIP →

Not legal advice. Admissibility depends on jurisdiction and circumstances.

Next tutorial

Continue with: Browser widget (Enterprise/Business).

Open widget tutorial → Back to tutorials →