The moment your photo leaves your editor, it starts losing its name
Ask a working photographer how to prove a photo is the original — theirs, delivered on a specific day, unchanged since — and the honest answer usually involves a RAW file, a folder of exports, and their word. The metadata that once traveled with the image doesn't survive the trip: platforms strip it on upload, messaging apps recompress it away, and the copy a client forwards to a third party arrives anonymous. Content credentials help where they survive. The professional's problem is the much larger territory where they don't.
That gap is where disputes live. A client insists the retouched version was yours. A platform copy gets re-uploaded under someone else's name. An editor asks, reasonably, "how do I know this is the file you delivered?" Each time, the photographer is asked to prove a negative about a file that has been copied, compressed, and renamed beyond recognition — with nothing but folder archaeology to stand on.
Seal the original at export, before it travels
The fix is to move the proof to the one moment the file is certainly yours and certainly final: export. Photographer Original Seal batch-seals finals as they leave your editor, fixing two measurements per file under the DocLock standard: a SHA-256 fingerprint, the final cryptographic authority, and the pixel count, the primary check for photographs and artwork. The measurements are gathered into a QR Trust Capsule and an Originals Record, with a delivery card for the client.
From then on, the question "is this the original?" has an answer that doesn't depend on you being in the room. Anyone holding the record can check any copy against it — offline, with no account — and get a graded verdict: Verified when everything matches; Warning for a supporting mismatch; Integrity Alert when a core layer fails; Broken Seal when the cryptography itself fails. Not a vibe, not a watermark — a measurement, taken at delivery, that still works after every platform between you and the viewer has stripped everything else.
What the verdict actually caught, in testing
When the app was live-tested on 2026-10-29, the sealed original verified — bit-for-bit the file that was sealed. An edited twin of exactly the same size came back Integrity Alert: the pixel count still matched, the fingerprint did not, and the verdict said so in plain language. That graded honesty matters more than a green checkmark would. A same-size edit is precisely the change a dispute is about, and a tool that waves it through because the dimensions match would be worse than no tool at all.
And that it was not produced by AI
There is a second accusation the modern photographer now has to answer, and it arrives even when nobody disputes the edit history: that the image was generated. Here the seal's contribution is provenance, fixed early. A file fingerprinted at export — inside a delivery record, under the photographer's name, on a date — carries a history that a generated image does not naturally have. The honest boundary matters, so here it is plainly: a seal cannot detect AI, and sealing a generated file produces a perfectly valid seal of a generated file. What sealing at export proves is origin and custody from that moment forward — which is exactly the ground an "it's AI" claim has to fight on, and it is much harder to fight a dated record than a person's assurance.
What a seal does not prove
A seal proves a file is unchanged since it was sealed. It does not prove the photograph is truthful, un-staged, or taken where the caption says it was taken. It is not a certificate of authenticity for the scene in front of the lens, and it does not replace content credentials where those survive — it covers the ground they can't reach: after the stripping, offline, years later, in front of someone who has never heard of your studio.
It also cannot work backwards. A photo delivered last year, never sealed, cannot be sealed into last year's state today — the record can only be fixed at a moment you actually hold the original. Which is the whole argument for making sealing a step in the export workflow rather than a rescue mission after a dispute starts.
Where it fits the working week
Wedding and event photographers hand over hundreds of finals at once — the batch is the product, and the batch is what gets sealed. Commercial photographers deliver files that travel furthest from their metadata, into client systems and agency archives. Stock and licensing photographers need the delivery record when a usage question surfaces months later. In every case the pattern is the same: seal at export, keep the Originals Record with the job, and let the file answer for itself.
The app is complimentary and runs entirely in your browser — your photos are never uploaded anywhere. The store page walks through the workflow and the test results: Photographer Original Seal. Keeping those records verifiable across drives, platforms, and decades is the second half of the problem, covered by the Proof Recovery & Continuity Kit; the rest of the proof library lives in the Learn hub.
Protocol One LLC — Standards Office, 3707 E Southern Ave, Suite 1023, Mesa, AZ 85206. {^}