Court-Admissible Photo Evidence: What Prooflens Actually Exports

The short answer

Whether a photo is usable as evidence usually turns on one thing: can the person who receives it check the claim themselves, without taking anyone's word for it? That means handing over something self-contained — the image, the proof it has not changed, and a document that explains both.

Prooflens Pro exports a .zip together with a PDF legal statement. The .zip carries the evidence in open formats: the image, the SHA-256 manifest, the RFC 3161 timestamp and the OpenTimestamps blockchain proof. The PDF documents that evidence and its anchoring status in plain language, so the recipient reads a description rather than reverse-engineering a hash. Prooflens is on the App Store; the rest of this page is about what the export actually establishes, and where the boundary with a legal question sits.

Why people search for "court-admissible"

Nobody searches for this out of curiosity. They search because something has already gone wrong, and it is almost always the same shape:

• A contractor says the damage was there before they started. You have photos. So does he.
• An insurer disputes the timeline of a loss — when the water first appeared, when the inspector arrived.
• A workplace incident, a landlord-and-tenant dispute, a site condition that will not be there next week.
• Someone disputes that a photo was edited, or when it was taken.

The photo alone proves nothing in any of those cases, because it is just a file anyone could have produced. What is missing is not a better camera. It is a way for a stranger to check that this exact file existed at this exact time and has not changed since. That is what this page is about.

Chain of custody starts at the handoff

The instinct is to photograph, then send the photo — by email, message, USB stick or paper. Each breaks the chain differently. A re-saved or re-compressed image has a different hash. A message app strips metadata. A print resamples. Even if the file survives, nothing in it says when it was made or that it has not since been replaced by another file from the same device.

A hash is a one-way fingerprint of the exact image bytes; any later edit, crop or re-encode changes it. But a hash on its own proves only that the file has not changed since the hash was made — not when the hash was made. Someone could hash an already-doctored image. A timestamp closes that gap: an RFC 3161 timestamp from an independent authority (freetsa.org) says a particular hash existed at a particular time. The app builds that hash, timestamp and the optional Bitcoin anchor into every capture, covered in more detail on proving a photo was not edited. This page is about the last mile: how that proof travels to someone who was not there.

What the export contains, and who each part is for

The .zip and the PDF are not two versions of the same thing. They answer two different questions for two different readers.

The .zip is the evidence. It contains the image, the SHA-256 manifest, the RFC 3161 timestamp and the OpenTimestamps proof. Because these are open, documented formats, anyone can check them with standard tools — OpenTimestamps publishes a free verifier for the blockchain proof, and an RFC 3161 timestamp can be checked against the authority's certificate — without installing Prooflens and without trusting it. Verification also runs fully on-device: any .zip or OTS file it produced can be checked by the person holding it, so the check does not depend on the app.

The PDF is the explanation. A legal statement documents the evidence and its anchoring status in language a court clerk, an insurer's adjuster or a solicitor can read, saving the recipient from having to know what an RFC 3161 token is in order to engage with it. It does not replace the .zip; it explains it.

That distinction is the one to keep straight when you hand the bundle over: the recipient verifying needs the .zip, the recipient reading needs the PDF. Sending only the PDF and calling it evidence would be like sending a screenshot of a passport — it describes something, it does not prove it.

Check anchoring status before you rely on a capture

The evidence library keeps every capture with its on-chain anchoring status, so at a glance you can see which items are anchored and which are still pending. Tapping a proof opens the detail and verify view.

The distinction matters. A capture with a local hash is already tamper-evident — the file cannot have changed since it was hashed. But it does not yet have the third-party timestamp and blockchain anchor that let someone without your device verify it. Anchoring status is how you tell "this one is ready to hand over" from "this one is not yet".

One thing to know about the pending state: capture, watermarking and hashing work fully offline. Obtaining an RFC 3161 timestamp and blockchain anchoring requires a connection, so when you are out of network coverage the proofs queue locally and complete automatically once you are back online. A capture made in a basement or a remote site may sit at a local-hash stage for a while before the timestamp and anchor land. If the evidence matters on a deadline, open the evidence library before you rely on it, not after.

Anchoring itself is not a per-proof charge. OpenTimestamps is a free, open protocol and many proofs are aggregated into a single Bitcoin transaction, so anchoring costs you nothing per proof.

What the proof establishes — and what it does not

This is where the claim is most often overstated, in both directions.

What it establishes: the file has not been altered since capture, with a timestamp vouched for by an independent third party, and — once anchored — that timestamp is anchored in a public blockchain and cannot be quietly rewritten. The file is the same file, and it existed at a time no one can later deny.

What it does not establish: what the photo depicts. A perfectly authenticated photo of a scene that did not happen, or a lawful scene, is still not proof of anything about the world. It is evidence about a file, not about a fact. It does not establish who took it.

And what it cannot decide: whether a given court, insurer or counterparty will accept it. That depends on the evidentiary rules of each jurisdiction, and no app can answer it in advance — it is a legal question for a lawyer.

The honest framing is this: admissibility is a decision someone else makes. What a tool like this can do is remove the reason the decision goes against you. If a judge must take the photographer's word for it, the evidence is weak no matter how clear the photo is. If the judge can see, from the file itself, that it has not changed and that an independent authority vouched for its time, the photo is on much firmer ground. The aim is to make the second case the default, while being honest that it cannot force the first decision.

What Prooflens does differently

Most photo tools solve this problem in one of two ways, and both have a gap.

A watermark-only app gives you something legible but not cryptographic: the watermark can be cropped or edited, and it says nothing about the file's integrity. A hashing tool that outputs a hash string gives you integrity but not legibility or a timestamp, and leaves the recipient to work out what to do with it. Both are real tools; neither hands a third party a self-verifying bundle.

Prooflens puts the watermark, the hash, the third-party timestamp and the optional blockchain anchor on every capture, and then makes the whole thing exportable as a .zip plus a PDF legal statement. On top of that, it keeps the evidence on your device: photos never leave the phone, and only the SHA-256 hash — a one-way fingerprint that cannot be reversed into the image — is ever transmitted for timestamping. There is no account and no cloud backup, and for shared evidence you can optionally strip the device serial to produce anonymous evidence, which a recipient can verify without ever seeing your picture.

Two honest limits. First, the watermark is a readable marker, not the proof — the proof is the hash, timestamp and anchor, as covered in burning details into the photo. Second, admissibility itself remains a legal question this app does not and should not answer.

Where the export sits in the plan

The .zip export and PDF legal statement are Pro features — annual, with a 7-day free trial, or a one-time Lifetime purchase — along with unlimited proofs, unlimited anchoring and all watermark templates. If the handoff is the part you care about, giving someone a bundle they can verify themselves, that is the tier to look at.

The decision you can now make

You do not need Prooflens for most photos — only for the ones that will be disputed later by someone who was not there. The question is not "is my photo good enough" but "could a stranger verify this file if I sent it to them tomorrow". Prooflens makes the answer yes; the last word on admissibility still belongs to a court, an insurer or a lawyer.

Download it on the App Store or read more on the product page.