Verify a capture. No account needed.
Drop or choose an evidence package and your browser checks it on this device: every sealed file, the digital signature, and the permanent copy on Arweave. Nothing is uploaded. You can also look up a capture by its fingerprint, transaction id or capture id.
Check an evidence package
Use the ZIP you downloaded from a capture, or the folder it unzipped into. Your browser checks it here, so the package never leaves this device.
Drop the evidence package here
The ZIP file, or the folder it unzipped into
No package to hand?
Look up a capture
Confirm a capture exists and see when it was sealed, from a fingerprint, transaction id or capture id.
Check another value
Accepted formats: 64-character hex hash, 43-character Arweave transaction id, or a capture id in UUID form. The format is detected automatically. To look up a file, drop it on the package checker above: only its fingerprint is sent.
What this verifies, and what it does not
- Existence and timing. The lookup confirms that a Permavault capture exists and shows when it was sealed: the content hashes, the Arweave transaction, and the Bitcoin anchor on record. Captures with a Legal certificate also show an RFC 3161 timestamp, applied to the anchored fingerprint when the certificate was issued. For a Regular Capture, this fingerprint is the signed manifest hash. For a Private Capture, it is a blinded commitment to the locked record of the original file, so the timestamp does not publish its identifying details. It is called qualified only when the authority that issued it is an EU qualified trust service provider, and the capture's evidence package states whether it qualifies under eIDAS.
- Integrity is checked on your device. The package checker above works out every file's fingerprint in your browser and compares it with the signed record, checks the digital signature, compares the signing key with Permavault's published keys, and, when you ask, compares the permanent copy on Arweave. The package is never uploaded, and only the published list of keys is fetched. It runs the same checks as the verify.sh script inside every package, and it takes what a Bitcoin timestamp must cover from the signed record, never from the script, so a package cannot vouch for its own signature or Bitcoin date. New to fingerprints? Read why hashing matters for digital evidence, or the Guide.
- Timestamps are checked where they live. This page cannot confirm Bitcoin timestamps itself, so the checker shows the Bitcoin timestamp as not checked here and walks you through confirming it on opentimestamps.org, which is independent of Permavault. It never counts a check it could not make as passed.
- What a match does not prove. That the captured content is true, accurate, or complete. A match proves a capture exists, what its bytes hash to, and when it was sealed. It does not vouch for what the source page claimed.
- Storage is designed for permanence. Captures live on a permanent decentralized network of roughly 300 independent nodes, funded by a long-term storage endowment, so the record stays checkable even if Permavault the company is gone. Any Arweave transaction id can be checked here, not just Permavault captures.
For experts: check a package with standard tools
Every evidence package also carries verify.sh (and verify.ps1 for Windows), which run the same checks with standard tools. They are programs that came with the package, so run them only on a package from a source you trust; for one someone else handed you, use the checker above. They need shasum, OpenSSL 3 or later with Ed25519, and optionally curl for the Arweave copy and the OpenTimestamps client for the Bitcoin timestamp. Unzip the package, then, from inside its folder:
bash verify.sh
On a Mac, the built-in openssl cannot check Ed25519 signatures; brew install openssl adds one the script finds by itself. VERIFICATION_GUIDE.md in the package gives the manual command behind each check, and how to compare the signing key with the published list at app.permavault.xyz/.well-known/permavault-signing-key.json. Want a package to try? Download the sample package.
