How to prove you created something first

To prove you created something first, you need dated evidence that you had the work before anyone else. The strongest combination is an independent timestamp of the exact file (a blockchain timestamp or official registration), plus your drafts, source files and the history of publishing. Self-made evidence — file dates, e-mails to yourself — is easy to fake and weak on its own.

Why "who was first" is the real question

In most countries you own the copyright the moment you create an original work. When a dispute starts, nobody asks for a registration number first — they ask: can you show you had this work before the other person? That needs evidence that is dated, hard to fake and tied to the exact work.

7 ways to prove you created it first, ranked

#EvidenceStrengthCostNotes
1Official copyright registrationHigh (where it exists)Fee per workStatutory benefits in the US; not available or not needed in many countries
2Independent blockchain timestamp of the fileHighFree–lowProves the exact file existed at a time; anyone can verify
3Qualified / trusted timestamp (RFC 3161, eIDAS)HighUsually paidLegal presumption of accuracy in the EU for qualified timestamps
4Drafts, sketches, layered and RAW filesMedium–highFreeShows the creative process; strongest combined with #2
5Public first publication (dated)MediumFreeProves publication date, not creation; posts can be edited
6Witnesses, contracts, invoices, client e-mailsMediumFreeContext and chain of events
7File metadata, e-mails to yourself, mailed envelopeLowFreeEasy to alter or fake

Step 1 — Timestamp the exact file, early

Register the file as soon as it exists and before you post it or send it to anyone. With SecureAuthor:

  1. Open the web app or the Chrome extension.
  2. Drop the file — you get a PDF certificate with its SHA-256 hash and UTC time.
  3. Twice a day the hash is anchored on the Polygon blockchain.

Register drafts and intermediate versions too: a series of certificates shows the work evolving in your hands.

Step 2 — Keep the creative trail

Keep what only the real author has: sketches, PSD/AI layers, RAW photos, DAW project files, manuscript versions, Git history. A thief usually has only the final file.

Step 3 — Preserve your publication history

Capture where and when you first published: your portfolio page, post, listing. Take a full-page screenshot with your browser and drop the image into SecureAuthor — it gets its own certificate. Website screenshots as evidence →

Step 4 — Register officially when it matters

If your country has a copyright registry and the work is commercially important, consider registering it. Registration vs proof of authorship →

What does not work well

  • File creation dates — reset when you copy a file, editable in seconds.
  • E-mailing the work to yourself — the e-mail can be edited; nothing independent confirms it.
  • Mailing yourself a sealed envelope — the classic poor man's copyright; envelopes can be resealed.

If someone already copied your work

Follow What to do if someone stole your work.

Frequently asked questions

Is the file's creation date enough proof?

No. File dates change when a file is copied and can be edited with free tools in seconds. They are supporting evidence at best.

Does posting on social media prove I was first?

A public post with a date helps, but posts can be deleted or edited, platforms recompress files, and it proves publication, not creation. Timestamp the original file before posting.

What is the cheapest strong proof?

A blockchain timestamp of the original file. With SecureAuthor it is free and takes seconds, and anyone can verify it later.

What if the other person also has a timestamp?

The earlier independent timestamp of the work, supported by drafts and source files, is usually the stronger evidence. This is why you should register early and register drafts.

Updated:

Protect your next file in seconds

Free proof of authorship: SHA-256 hash, UTC timestamp and a Polygon blockchain record. Your file is not stored.

Add to ChromeProtect a file