How to Prove Your YouTube Video Is Original Before Someone Copies It

How to create a date-stamped proof of your video before you publish, so you can prove it is the original if someone re-uploads it or files a false claim.

1. How will you prove it after your video is stolen?

Say you spent 3-4 days making a video. The moment you publish it, another channel re-uploads it under their own name, or someone files a copyright claim against your own video. The platform tells you: "Prove that this is your original."

At that point most creators only have a few things: the file's "date modified", a screenshot of a folder, or the YouTube upload date. The problem is that a file's date can be changed on a computer in a few seconds, and the upload date only shows when the video was published, not when it was made. Whoever publishes first can look like they came first.

That is why, before publishing, you need a proof that you cannot alter yourself. This is where a file timestamp helps.

2. The 3 layers of proof of originality

No single thing makes a complete case. Strong proof is built from 3 layers:

• Layer 1: How the work was made. Raw footage, project files (Premiere, DaVinci, CapCut), the script, the voice-over, the thumbnail's PSD or Canva file. Someone who copies your video won't have any of this.
• Layer 2: Dated records. Google Drive version history, emails you sent to yourself, drafts of the script, earlier private or unlisted uploads.
• Layer 3: Independent timestamp. A proof that comes from a third-party system. Proof of Original anchors your file's SHA-256 fingerprint to the Bitcoin blockchain, which neither you nor we can change.

3. The 6-step workflow before you publish

1. Treat your final export as the "original". Export the video, make a copy of it, and do your editing or uploading on the copy. Never rename, compress or re-save the original file, because even a single changed byte changes the fingerprint.
2. Keep the raw material in one folder. Put the raw clips, project file, script, voice-over and thumbnail in one folder and ZIP it only once. Don't create that ZIP again, because re-creating it can produce a different fingerprint. Keep safe the exact ZIP you timestamp.
3. Create the proof. Open Proof of Original, choose your final video and click "Create Proof". Then do the same for the ZIP. You will get a separate .ots for each. The file is not uploaded; only the 32-byte hash is sent.
4. Save your downloads. Download the .ots file, the certificate PNG and the JSON record. Keep them together with the original file.
5. Verify once. Add the file and the .ots in the Verify Proof tab. If it says "Hash matches", everything is fine.
6. Now publish. After a few hours, upgrade both .ots files on opentimestamps.org so the proof moves from "pending" to "confirmed".

The tool works even if your video is several GB. The file is read in small chunks, so it just takes a little time to generate the fingerprint.

4. What will you show in a dispute?

If someone claims your video as their own, you should have this package ready:

• The original video file and its .ots proof
• The certificate PNG (file name, size, SHA-256 and status in one place)
• The ZIP of the project file and raw footage, with its .ots
• Dated drafts of the script and your Drive version history
• The date of any private or unlisted upload, if you uploaded earlier

The simplest way to give the proof: send both the original file and the .ots, and ask the other side to verify it themselves on opentimestamps.org. This way they don't have to trust any company.

5. Common mistakes creators make

• Creating proof only for the published video. If the file has already been copied, its timestamp is late. Do it before you publish.
• Re-saving or compressing the original. A new fingerprint is created and the old proof won't match.
• Losing the .ots file. Without the .ots you cannot prove the earlier date. Keep it on both Drive and a pen drive.
• Treating pending as final. Bitcoin confirmation takes a few hours. Remember to upgrade later.
• Relying only on screenshots. A screenshot can be edited easily, a timestamp cannot.

6. What should you timestamp?

Not just the final video. Create proof for all of these: script, voice-over, raw clips, project file, thumbnail, channel logo and background music or beat. If you want to share a preview of a thumbnail or photos, add a watermark with the Watermark Tool, but always timestamp the un-watermarked original.

If the idea of a SHA-256 fingerprint is new to you, read this guide: What Is a SHA-256 Hash?. And for the pending or confirmed status of an .ots file: OpenTimestamps and .ots Files Explained.

7. Quick checklist

• Final video exported, editing done on a copy
• Raw material ZIPped once
• Proof of Original created for both the video and the ZIP
• .ots, certificate and JSON backed up in 2 places along with the original
• Match checked once in the Verify tab
• Upgraded on opentimestamps.org after a few hours