Prove a video existed by a date.

Fingerprint your video on your device and anchor the fingerprint in Bitcoin through the free OpenTimestamps calendars. Later, anyone can check that your file existed, unchanged, by that time. The video never leaves your device.

Stamp a file

or drop it here. Any file works, any size. It's read on your device and never uploaded.

Your stamps in this browser

None yet. Stamps you make here are listed, with their proofs, in this browser only.

Kept in this browser's storage only. Pending stamps complete themselves when you come back after a few hours. Download each proof: clearing your browser deletes this list.

How it works

  1. Fingerprint. Your browser computes the file's SHA-256 hash: 64 characters that change completely if a single byte of the file changes.
  2. Anchor. The page mixes the fingerprint with a random number, hashes it again and sends only that to the public OpenTimestamps calendars. They combine it with everyone else's submissions into one hash that goes into a Bitcoin transaction, usually within a few hours.
  3. Check. The proof (.ots) links your file's fingerprint, step by step, to a Bitcoin block. Anyone can verify it on the check page or with the official client, and compare their copy of the file.

See a sample proof for this 4-second sample clip, then drop the clip on the check page to compare it.

What a timestamp proves, and what it doesn't

Its real use is order of events: footage stamped before a manipulated version of it appeared, or before a dispute began, can be shown to predate them. More on how it works and its limits

Questions

Does a timestamp prove my video is real?

No. It proves that this exact file existed no later than the time shown. It says nothing about who made it, where, or whether what it shows happened. What it can do is rule out a later fabrication of that same file: footage stamped before a deepfake of it existed can't have been made from that deepfake.

Is my video uploaded?

No. The page reads the file on your device and computes its SHA-256 fingerprint. What leaves your device is a hash of that fingerprint mixed with a random number, so the calendars can't even tell which file it is.

How long until the proof is complete?

The calendars collect submissions and anchor them in a Bitcoin transaction, usually within a few hours. Until then the proof is pending. Open the proof again later on the check page and it completes itself; or run 'ots upgrade' with the official client.

What do I need to keep?

The original file, exactly as it was when you stamped it, and the .ots proof file. A copy that has been edited, trimmed, compressed or re-uploaded has a different fingerprint and won't match.

Why doesn't the video I downloaded from social media match?

Platforms re-encode uploads, which changes every byte. A timestamp covers the exact file that was stamped. Ask for the original file; a mismatch on its own doesn't mean the video was doctored.

Who else can verify a proof?

Anyone. Proofs are standard OpenTimestamps files: this site's check page reads them, so does the official ots client (with a Bitcoin node), and so do other OpenTimestamps tools. Nothing depends on this site staying online.

Does it cost anything?

No. The OpenTimestamps calendars are free public services, and this site is free and open source.

Guides