The short answer. Keep the original file, sign it early with Content Credentials under the open C2PA standard, keep the signed copy unchanged, and share the signed file when proof is asked for — anyone can verify it free on the public Content Credentials Verify site (verify.contentauthenticity.org). The credential records who signed the file, when, and with which tool. If the file is changed after signing, verification can show that it no longer matches the signed record.
An honest starting point. A signature does not prove that what a photo shows is true, and it cannot prove what happened before signing. Provenance starts at signing. That limit is not a flaw to hide — it is exactly why originals should be signed while they are fresh, and why honest AI-assist labels matter. This page is general information, not legal advice.
What a Content Credential actually contains
A record that travels with the file
Depending on the signing process, the record can show the signer, the signing date and time, the tool used, recorded edits, and whether generative AI was part of the process. A reviewer does not need your word for it: they open the verification page and read the same record you see.
Tamper-evident, not magic
The point is change detection. A signed file carries a record tied to its exact contents at signing. Edit the signed copy afterwards and the record and the file no longer line up. That is a stronger claim than “trust me, this is the original” — and a narrower, more honest one than “this proves everything about the scene.”
Why ordinary metadata is not enough
EXIF data — camera model, timestamp, settings — is useful, but it was never built as proof. It can be edited with free tools, copied from another file, or stripped automatically when a platform recompresses an upload. Screenshots are weaker still: a screenshot is a new file with a new history. If proof may matter later, preserve and sign the original file, not a screenshot, export, or messaging-app copy.
The 5-step process
1. Keep the true original separate
Save the camera or source original untouched, under its original name if possible. Do all cropping, color work and resizing on copies. Once the only copy you own has been edited, no later signature can recreate the earlier state.
2. Sign early, while the history is short
Sign before the file travels — before clients, platforms, group chats and cloud folders create ten versions. The shorter and cleaner the history at signing, the clearer the record reads to anyone checking it later.
3. Label AI assistance honestly
If generative tools removed an object, extended a background, or drafted part of a document, say so in the record. An honest label protects you twice: the file's real history is on record, and nobody can later “expose” a step you already disclosed.
4. Store the signed copy unchanged
Treat the signed file as the master. Publish and send copies of it as needed, but do not re-save, recompress or rename-edit the master itself. Keep a backup: a verification record is only useful if the signed file still exists.
5. Link the verification page where decisions happen
Put the public verification link in the places where trust is decided: your portfolio, the delivery email to a client, a stock submission, or the folder with a claim or contract record. Proof that nobody can find in the moment it is challenged does half its job.
When this record matters most
Client and platform disputes
A client questions whether delivered work is yours, or a platform flags real work as generated. A dated credential plus a verification page turns an argument about impressions into a check anyone can run.
Evidence-adjacent files
Photos of damage, condition, delivery or completed work often become important only when someone disagrees later. Signing at capture or delivery preserves a checkable state from before the dispute existed.
Selling originals and archives
A file with a verifiable history — created and signed at a known time, unchanged since — is easier to trust and to price than an identical-looking file with no history at all.
Family and personal records
Voice notes, family photos and important recordings may need to stay believable for years, long after phones and accounts change. Signing while they are fresh keeps them provable later.
Five mistakes that quietly destroy proof
1. Signing only the edited export. The record then starts after the edits that may later be questioned.
2. Waiting years to sign. A signature dated today proves today's file — it cannot backdate an older history.
3. Sending originals through apps that recompress them. The received file is a new, altered copy, not your original.
4. Hiding AI steps. An undisclosed edit discovered later damages the whole record's credibility, including the honest parts.
5. Keeping no backup of the signed master. Lose the exact signed file and the strongest part of the proof is gone with it.
The one-page checklist
- Original preserved untouched, separate from edited copies.
- Signed early, before the file travels.
- Signer name and date correct in the credential.
- AI assistance labeled honestly, where it was used.
- Signed master backed up and never re-saved.
- Verification link saved with the project or claim record.
- Verification link included in delivery or portfolio.
- Edited versions clearly treated as copies, not masters.
Get your files signed without touching developer tools
ProvenanceMark is done-for-you Content Credentials signing by email: send your photos, videos or audio files, and receive the signed copies — each verifiable free by anyone at verify.contentauthenticity.org — plus a provenance report PDF. Starter is $14 one-time for up to 50 files; Archive is $79 one-time for up to 500 files. No recurring charges. 30-day money-back guarantee. Honest status: our signer certificate is not yet on the C2PA public trust list, so the public Verify site labels the record Unrecognized and warns that the issuer could not be recognized; it still names ProvenanceMark as the signer, but shows no trust badge yet, and our application for a recognized trust-list certificate is in progress.
See how ProvenanceMark works · Free Family Code Word Generator
Frequently asked questions
How can I prove a photo is original and not AI-generated?
Sign the original file with Content Credentials (C2PA) as soon as possible after creating it. The credential records who signed it, when, and with which tool, and it is tamper-evident: if the file changes after signing, verification shows that. Share the signed file when proof is asked for — anyone can verify it free on the public Content Credentials Verify site (verify.contentauthenticity.org). Signing does not prove what a photo shows is true, and it cannot rewrite history before the signing moment.
What are Content Credentials?
Content Credentials are a readable record attached to a file under the open C2PA standard. They can show the signer, the signing date, the tool used, recorded edits, and honest labels for AI assistance. Anyone can inspect them on a verification page without a special account.
Does EXIF metadata prove a photo is original?
No. Ordinary EXIF metadata can be edited, copied or stripped in seconds, and many platforms remove it on upload. It is useful information, but it is not tamper-evident. A C2PA credential is designed so changes after signing are detectable.
What does a C2PA signature not prove?
It does not prove that what a photo depicts is true, that the signer personally created every element, or what happened before signing. Provenance starts at signing — which is why originals should be signed early and AI assistance labeled honestly.
Can I sign videos and audio, not just photos?
Yes. Sign the original file, keep the signed copy unchanged, and let anyone check it free on the public Content Credentials Verify site (verify.contentauthenticity.org). ProvenanceMark handles photos, videos and audio files by email. PDFs cannot carry a C2PA signature, so documents are not signed — sign the original photo, video or audio file instead.
How much does ProvenanceMark cost?
Starter is $14 one-time for up to 50 files and Archive is $79 one-time for up to 500 files. Both include signing, free public verification of every file at verify.contentauthenticity.org and a provenance report PDF. No recurring charges, and a 30-day money-back guarantee applies. Honest status: our signer certificate is not yet on the C2PA public trust list, so the public Verify site labels the record Unrecognized and warns that the issuer could not be recognized; it still names ProvenanceMark as the signer, but shows no trust badge yet, and our application for a recognized trust-list certificate is in progress.
Written by DoubleProof, Portland, Oregon. Questions: contact@getdoubleproof.com. ProvenanceMark is an independent service that applies the public C2PA specification; it is not affiliated with or endorsed by C2PA or the Content Authenticity Initiative. This guide is general information, not legal advice.