Skip to content
Photo evidence9 min read

Photo Evidence: How to Make a Photo Hold Up in a Dispute

Photo evidence holds up when four things can be checked by someone who does not trust you: the photo was taken live, an independent authority dated it, nothing changed since, and anyone can verify all of that without your help.

By Cédric Driaux, Founder of tryVidimus

Front of a silver car, photographed at handover

Why a regular photo proves very little

A photo feels like proof because it shows something. In a dispute, the other side rarely questions what the photo shows. They question where it comes from. Was it taken that day, or last month? Was it taken of this car, this room, this parcel? Was it retouched before you sent it? Photo evidence is only as strong as the answers to those questions.

An ordinary photo answers none of them on its own:

  • The date comes from the phone. The clock can be changed in the settings, and the date written in the file can be edited afterwards.
  • The file can be altered. Cropping out a scratch or brightening a stain takes seconds, and a careful edit leaves nothing a reader would notice.
  • The file lives on one side's phone or servers. Whoever stores it could have replaced it, so the other party has no reason to trust it.
  • Nobody else can check. An insurer, a lawyer or a customer has to take your word for all of the above.

Take a common case. A renter returns a van. Two days later, the owner sends photos of a dented door. The renter replies that the dent was there at pickup, and sends photos too. Both sets look real. Neither can be dated with certainty, and each party stored its own. The platform in the middle has no way to tell, and often refunds to close the case.

The 4 conditions of a trustworthy photo

A photo becomes hard to contest when four conditions are met together. Each one closes a specific objection.

ConditionWhat it meansThe objection it closes
Live captureThe photo is taken with the camera at that moment, with no upload from the gallery.“This photo comes from another day or another place.”
Independent timestampA third-party authority certifies the date. Not the phone, and not the platform.“The date was changed.”
Integrity sealA fingerprint and a signature make any later change detectable.“The photo was retouched.”
Public verificationAnyone can check the three points above, without an account and without asking you.“We only have your word for it.”

Missing one condition weakens the rest. A timestamp on a photo imported from the gallery only proves that the file existed when it was stamped, not when the scene happened. A sealed file that only its owner can check is still that owner's word.

What courts, insurers and platforms actually look at

Whoever has to settle a disagreement tends to ask the same three questions about a photo: where does it come from, when was it taken, and has it changed. The bar is not the same everywhere.

  • A platform's support team decides quickly, from what both parties send. A photo they can check themselves, from a link, saves an exchange of emails and a judgment call.
  • An insurer or a loss adjuster looks for consistency: dates that match the claim, photos that were not reused from elsewhere, a record of who captured what.
  • In legal proceedings, the weight given to a document depends on how reliably its origin and its date can be established, and the other side can challenge both.

On dates, European law gives a clear reference. Under Article 41 of the eIDAS Regulation, an electronic time stamp cannot be denied legal effect or admissibility as evidence solely because it is in electronic form, and a qualified electronic time stamp enjoys a presumption of the accuracy of the date and time it indicates and of the integrity of the data to which they are bound.

That presumption concerns the date and the integrity of the file. It says nothing about what the photo depicts. It also belongs to European Union law: elsewhere, the timestamp remains a signed, verifiable record of the date, without that presumption. Our standards page explains the two standards we rely on, and their limits.

Common mistakes

  • Uploading from the gallery. Once a photo can come from the camera roll, it can come from anywhere: another day, another object, an editing app.
  • Sending photos through a messaging app. Messaging apps usually compress images, and what arrives is a copy that neither side can tie to a date.
  • Relying on a screenshot. A screenshot is a new image of a screen. It carries the date of the screenshot, not of the scene.
  • Trusting the date in the file. The date and the location stored in a photo's metadata (EXIF) can be edited with free tools.
  • Keeping the photos on one party's servers. The party that loses the dispute can say they were modified, and nothing proves otherwise.
  • Taking photos after the disagreement starts. Proof has to exist before the dispute: at handover and at return, not when the complaint arrives.
  • Adding a visible date stamp. A date printed on the image is part of the picture. Anyone can draw one.

How sealed photos work, step by step

A sealed photo meets the four conditions by construction. Here is how tryVidimus does it. The steps are the same in any serious system; what differs is who operates them.

  1. Your application asks for a capture. One API call creates a capture link for a booking or an order.
  2. The user takes the photos live. The link opens a capture page in the browser, with your logo and your wording. The camera is the only source: there is no upload from the gallery.
  3. The file goes straight to storage. It does not pass through your servers, so nobody can say you touched it.
  4. The proof is sealed. Each file gets a SHA-256 fingerprint. The proof receives a qualified electronic timestamp from a qualified trust service provider, and each photo is signed with a C2PA manifest that records its origin.
  5. Anyone can verify. Each proof has a public verification page, open without an account. The verifier is open source, so a proof can be checked without trusting our servers.

The timestamp follows RFC 3161, the Internet standard for time stamps: the authority receives the fingerprint of the proof, never the photos, and returns a signed token that binds this fingerprint to a certified date. C2PA is the open standard behind Content Credentials. It keeps the origin of the file and makes any modification visible.

For developers, the integration is a few API calls and a webhook. The developer page shows the calls, and the documentation covers them in detail.

Photo evidence by industry

The pattern is always the same: something changes hands, and two parties may later disagree about its state. The proof has to exist before the disagreement.

  • Vehicle rental. The owner or the agency captures the vehicle at handover, and the renter captures it again at return. Cars, vans, motorhomes, boats, scooters.
  • Equipment rental. Cameras, lenses, drones, tools, outdoor gear: a few seconds of live capture at each handover.
  • Short-term rentals. The host or the cleaning team photographs the property before arrival and after departure, room by room, and the two proofs are linked.
  • Resale and shipping. The seller photographs the item, then the packed box, before the parcel leaves.

Our use cases page walks through a stay step by step, from the capture before arrival to the disagreement.

Going further

Each point of this guide has its own article.

Frequently asked questions

Can a photo be used as evidence?

In many disputes, yes, but its weight depends on what can be established about it: where it comes from, when it was taken and whether it changed. A photo that anyone can verify on those three points is much harder to contest than a file sent by one party. Rules differ by country, so ask a lawyer about a specific case.

How do I prove when a photo was taken?

Not with the phone's date or the file's metadata, which can both be changed. The date has to be certified by an independent timestamp authority at the moment of capture. In the European Union, a qualified electronic timestamp carries a presumption of accuracy of the date under Article 41 of the eIDAS Regulation.

How do I prove a photo has not been edited?

By sealing it when it is taken. A fingerprint (a SHA-256 hash) is computed from the file and bound to a certified date, and the photo is signed. Any change to the file, even a single pixel, produces a different fingerprint and breaks the signature. Anyone can check this.

Is the date stored in a photo (EXIF) proof of the date?

No. EXIF data is written by the device and can be edited afterwards with free tools. It is useful as context, but it does not establish when a photo was taken.

Does a sealed photo decide who is right?

No. A sealed photo shows that a file existed at a certified date, has not changed since and was captured live. It does not judge the damage or the dispute. The parties, an insurer or a judge draw the conclusions.

Do I need an app to capture sealed photos?

No. The capture page is a web page opened from a link, in the phone's browser or inside your own application. The person who takes the photos has nothing to install.

Try it in the sandbox

Photo evidence does not depend on how convincing a picture looks. It depends on whether a third party can check where it comes from, when it was taken and that nothing changed. You can build and test the whole capture journey for free in the sandbox, without a card.

Create an account

Official sources

Cédric Driaux · Founder of tryVidimus

Cédric Driaux is the founder of tryVidimus, published by Fyher. He has been a software developer for 23 years. He also builds ScanStay, a photo proof tool for short-term rental hosts.

Related articles