// PROVENANCEMARK — PROVE YOUR REAL WORK IS REAL

How to prove a video is original: keep the raw file, sign it early

A client watches your delivery and asks the new question: “Was this AI-generated?” A video file on its own cannot answer that. What answers it is a small protocol around the file: the untouched camera original, the edit chain behind the final cut, and a dated, tamper-evident signature applied before anyone doubted it.

The short answer. Keep the camera original untouched — never edit the only copy. Keep the raw clips and project record behind the final cut. Sign the original and the final export early with Content Credentials (C2PA), while the work is fresh. When anyone asks, send the signed file and its verification page — not just a platform link.

An honest starting point. Signing a video proves the file existed on the signing date and has not changed since, and records who signed it. It does not prove the events in the video were real, unstaged or filmed by the signer, and it cannot create a history from before signing. If generative tools helped with any part of the work, label that honestly — a record that hides AI assistance is worth less than one that states it. This page is general information, not legal advice.

Why a delivered video, on its own, is weak proof

The copy people watch is not the file you made

Platforms re-encode every upload for streaming, and messaging apps compress and rename what they forward. The streamed or forwarded copy is a new file with a new history. Judging origin from that copy — or trying to verify it — starts from the wrong file.

Every real video is edited, so “edited” proves nothing either way

Colour, cuts, captions and sound work are normal craft. There is no reliable visual test that separates a real, edited video from a generated one, and detector scores are opinions, not records. What holds up is not how the video looks — it is the dated chain of files behind it.

The accusation arrives after the proof window closes

Doubts surface at delivery, at payment, or when a video performs well — weeks after the shoot. By then the raw clips may be deleted, the project overwritten, and the only surviving file is the platform copy. Provenance has to be captured at production time, not reconstructed at dispute time.

The 6 steps that make a video hold up

1. Keep the camera original untouched

Copy the files off the camera or phone exactly as recorded, into an archive folder you never edit. Do all work on duplicates. The untouched original is the root of the whole chain: once it has been re-exported, renamed by an app or overwritten, that root is gone.

2. Keep the edit chain, not just the export

Save the project file, the list of raw clips used, and one plain note per project: what it is, when and where it was shot, and who shot it. Keep the unused takes from the same shoot — matching raw material from the same scene is practical corroboration that is hard to invent later.

3. Sign the original while the shoot is fresh

Sign the camera original with Content Credentials under the open C2PA standard as soon as the project matters — ideally the same week it was shot. The credential records who signed it, when, and with which tool, and it is tamper-evident: change the signed copy later and verification shows it no longer matches. Our plain-English Content Credentials guide explains what a signature does and does not prove.

4. Sign the final export you deliver

Sign the exact final cut before you send it. That freezes the delivery itself: if a different version circulates later, your signed export is the reference it can be compared against. Signing both ends — raw and final — gives you the full chain; signing only the final is still worthwhile, with provenance starting at delivery.

5. Send verification, not just a viewing link

When a client, platform or buyer asks for proof, send the signed file together with its public verification page, where they can read the signer, the date and whether the file still matches — the same record you see. A platform link is for watching; the signed file is for proving.

6. Answer the “is this AI?” question with the record, briefly

Do not argue about how the video looks. One short reply, in your own words, is enough — for example: “This is my original footage, shot on [date]. The camera file and the delivered cut are both signed with Content Credentials; here is the verification page for each, and the provenance report for the batch.” Then stop: the record does the persuading. (That wording is a template, not a quote from a real exchange.)

The honest limits — read these before relying on any signed video

Signing freezes a file; it does not certify a scene. A staged or misleading video can be signed just like a genuine one. The signature proves continuity of the file from the signing date — pair it with the raw clips and project record whenever the stakes are real.

AI assistance must be labelled, not hidden. If a generative tool created or altered part of a file, an honest AI-assist label belongs in its record. A signature over an undisclosed AI element does not make the element human-made; it makes the record misleading.

Timing is the whole game. Provenance starts at signing. A video signed after a dispute began proves only that it existed then. Shoot, archive and sign at production time — deliveries, testimonials, condition and work-progress videos especially — not after questions start.

Video provenance checklist

  • Camera originals copied off the device untouched, in an archive folder that is never edited
  • All editing done on duplicates; the originals are never re-exported or overwritten
  • Project file and the list of raw clips used are saved with the project
  • One plain note per project: what it is, when and where it was shot, who shot it
  • Unused takes from the same shoot kept as corroboration
  • Camera original signed (C2PA) while the shoot is fresh
  • Final delivered export signed before it is sent
  • Any AI assistance labelled honestly in the record
  • Signed files and their verification links kept with the provenance report, ready to send

Preparing a batch before signing? The free Provenance Record Builder organises your files, dates, sources and honest AI labels in the browser — nothing is uploaded — and the free Provenance Batch Audit Checker scores each file against six pre-signing readiness checks. For still images, the same protocol is covered in our Content Credentials guide on proving a photo is original.

Sign your footage before anyone questions it

ProvenanceMark signs your original files with tamper-evident C2PA credentials — by email, no developer tools, no calls. Starter is $14 one-time for up to 50 files; Archive is $79 one-time for up to 500 files. Every file can be verified free by anyone, and each batch comes back with a provenance report PDF.

SIGN WITH PROVENANCEMARK — FROM $14

Frequently asked questions

Can you prove a video was not made by AI?

Not with one test, and no honest tool should promise that. What you can build is a dated record: the untouched camera original, the raw clips and project files behind the final cut, and a Content Credentials (C2PA) signature applied early, before any dispute. Together they show this exact file existed on a known date, who signed it, and that it has not changed since. That is strong, checkable evidence of origin — it is not a detector score and it does not certify that everything shown in the video happened exactly as it appears.

Does uploading to YouTube, TikTok or Instagram preserve the proof?

Treat every platform upload as a new, processed copy: platforms re-encode video for streaming, and the streamed copy is not the file you signed. Keep the signed original and the signed final export in your own archive, and verify those files — not the platform stream. When a client or platform questions a video, send the signed file itself together with its public verification page, and link the platform post only as a viewing copy.

Should I sign the raw footage or the final edited video?

Both, when you can. Signing the camera original anchors the earliest date and freezes the source. Signing the final export freezes the exact cut you delivered, so nobody can swap or re-edit it later and still claim it is your delivery. The two signatures together describe the chain: this raw file, signed on this date, became this final file, signed on that date. Signing only the final export is still useful — provenance simply starts later.

What if the video is already edited and delivered?

Sign what you still have, now: the final export first, and the raw clips and project file exports alongside it. Be honest about the date — a signature applied today proves the file existed today, not on the delivery date. Then add the corroboration you do have: the delivery email, the project files, and the original clips. Late provenance is weaker than early provenance, but it still stops every later edit and swap.

Can audio be signed the same way?

Yes. ProvenanceMark signs audio files (MP3, M4A and WAV) with the same Content Credentials process as video (MP4) and photos (JPEG, PNG and WebP), and each signed file can be verified free on the public Content Credentials Verify site. PDFs cannot carry a C2PA signature and are not offered for signing.

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 C2PA signing, free public verification per file and a provenance report PDF for the batch. No recurring charges, and a 30-day money-back guarantee applies.

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.