Wedding photography has three recurring evidence problems and they're all getting worse:
- The client claims you delivered different photos than you actually sent. A year later. After the marriage hit a rough patch and everything's a fight.
- Someone on social media accuses your portfolio shots of being AI-generated. The accusation gets more reach than your denial.
- Another photographer's portfolio quietly includes your work, and you need to demonstrate priority — that you took the photo first.
In all three cases, the strongest single piece of evidence a working photographer can produce is a cryptographic timestamp on the delivered files, dated to the day of delivery. Orphograph generates that timestamp in your browser in about thirty seconds.
The ritual
On the day you deliver a gallery:
- Build the final delivery — JPEGs at the resolution the client gets, or a zip of the full set.
- Drop the file or zip into Orphograph. SHA-256 runs in your browser; the files never upload. Within seconds you have a 64-character hash and within minutes you have a Bitcoin-anchored receipt.
- Save the receipt JSON in the same folder as the delivered gallery. Back it up the same place you back up your business records.
- Optionally: include a one-line note in the delivery email letting the client know the gallery is timestamped. It signals professionalism and quietly closes off "you sent me different photos" as a future dispute.
What this actually proves
The receipt proves: this exact zip of these exact JPEGs existed on this exact date. If the client later claims you delivered different files, you can re-hash the original zip, compare to the receipt, and demonstrate the bytes match. If the client claims a particular photo is fake, you can show the zip containing that photo was anchored before any AI tool could have been used to generate it (assuming you anchored promptly).
It does not prove you took the photo — it proves the file existed in its exact form by date X. For "is this photo from my camera," you pair the timestamp with your RAW originals on read-only storage. Together they're a strong evidence package; separately they're each one piece.
RAWs versus JPEGs
RAW files and the JPEGs you deliver have different SHA-256 hashes. If you anticipate ever needing to prove "I have the original capture data," anchor a zip of the RAWs in addition to the JPEG delivery. The two receipts cost the same — free, $29 for a Pack of Fifty, $9/month for unlimited. For a photographer doing twenty weddings a year, unlimited is the right tier.
The AI-generation accusation
This one's worth addressing directly. Generative image models have published training-data cutoffs. If your photo was anchored before the cutoff for any major model, the AI-generation accusation collapses — the model literally couldn't have produced your photo because it didn't exist when the model trained. For new work, anchor at delivery and that defense is permanent.
FAQ
Why would I need to prove the photos came from my camera?
Client disputes, AI-generation accusations, and portfolio-theft cases. A Bitcoin-anchored delivery timestamp defeats most of these in one step.
Do I have to anchor every photo?
No. Zip the final delivery and anchor the zip. The receipt covers the whole gallery.
RAW versus JPEG?
Different hashes. Anchor a zip of the RAWs separately if you might need to prove the capture data exists.
Will clients see the receipt?
Only if you share it. Many photographers include a one-line note; others keep the receipt private as personal insurance.
What does this cost for a working photographer?
Free for three anchors every 24 hours; $29 for a Pack of Fifty that never expires; $9/month for unlimited.