IndieDev Games

Prove you published your game first

How publication certificates and fingerprints work, how to download a signed certificate, and what to do if someone copies your web game to Steam or another site.

Updated Nov 18, 2026

A web game is made of ordinary files, so nobody can stop a determined person from copying it. What you can do is prove that you published it first. That is what usually decides a takedown request to Steam or another website, and indiedev.games helps you with it.

What we record

Every time you upload a build, we work out a fingerprint (a SHA-256 hash) of each file inside it and of the zip itself, and keep them with your studio, the game and the exact upload time. A fingerprint is a short code that changes completely if even one byte of the file changes, and it says nothing about your players. Builds are never changed after they are uploaded, so the record stays true.

Builds uploaded before this feature existed are fingerprinted from the files we hold, so they get the same certificate. They have no zip fingerprint, because we do not keep the zip.

Get your certificate

  1. Open your game and find the build in the list of builds.
  2. Click Publication certificate.
  3. Click Download the signed certificate and keep the .json file somewhere safe.

The certificate states your studio, the game, the build, the upload time (UTC) and the fingerprints. It is signed by indiedev.games, so nobody, including you, can change a word without breaking the signature. Anyone can check it on Verify a copy, and it stays valid even if you later delete the build or the game.

A certificate shows when your studio uploaded these exact files here. It does not by itself prove that you wrote them, so keep your own source code, project history and dated files too.

When you find a copy

  1. Get the files of the copy if you can, or note where it is published.
  2. Open Verify a copy, choose those files (or a folder, or a zip) and check them. Your browser works out the fingerprints on your computer and sends only those, never the files. If they are the same as a game here, you see which one, who uploaded it and when. Files that engines share between many games are ignored, so a match means files that belong to that one game.
  3. Report it to the store or website. Steam, itch.io and most others have a copyright or DMCA form. Attach your downloaded certificate and link Verify a copy, so their team can check the signature themselves and see that your upload came first.
  4. If the copy is on indiedev.games, use Contact us and say which game.

Registering your copyright where you live strengthens a claim, and a copy that is nearly the same with a few changed files is still found, because every file is compared on its own.

What this does not do

  • It does not stop copying or block a copy from running.
  • A thief who changes every file, for example by recompiling, will not match by fingerprint. Your certificate and source history still show you published first.
  • Games from other sites cannot be checked: only files uploaded to indiedev.games are known to us.

Was this article helpful?

We only count the answers. Nothing says who you are.

Still stuck? Contact us. · Search the help