For agencies & freelancers · delivery disputes

Prove which file existed. And when.

“That's not the file we agreed on.” “You sent that late.” Today it is your word against your client's. HashStamp hands you a receipt they can check themselves — so you stop being the one who has to be taken on trust.

Works with anything you can upload: contracts, designs, manuscripts, code, invoices, deliverables. If it's a file, you can stamp it.
A stamp shows which file existed and when — pair it with your send record (email, upload, shared link) to show which version you delivered.

final_logo_v3.pdf
Verified
Stamped: 2026-05-21 14:08 UTC
File: final_logo_v3.pdf
SHA-256:
a7f3c9…e21b
Verify at: verifyknot.io/QK7M-2F
Try it

Stamp a file right now.

Drop in a file. It never leaves your device — it is hashed right here in your browser, so you can stamp confidential client work without handing it to anybody. You get back a link your client can check for themselves. Free, no account.

Whatever you type here becomes public. Your label is published on this record's verification page, which anyone with the link can read. We do not offer label removal as a right. Never enter personal or confidential information — client names, addresses, account numbers, or case details. How labels are handled.
Leave blank for none. Your file's name and contents stay on your device — only the fingerprint, and anything you type here, is published.
Stamped
File (local only):
Public label:
SHA-256:
Stamped at:
Chain position:
ZK code:
Open verification page →

What actually gets sent: only your file's SHA-256 fingerprint, plus any public label you type. The record is signed by HashStamp's hosted service key and hash-linked into ZKNOT's tamper-evident chain, at a time HashStamp states — not an external time authority.

Why not just email yourself

Because you control your own inbox.

Anything you control, a client can argue you faked. The point of proof is that it doesn't depend on you.

Email it to yourself / Drive history

  • You control the timestamp — easy to dispute
  • Can be edited, backdated, or "lost"
  • Proves nothing to a skeptical client
  • No independent way to check it

Hashstamp

  • Tamper-evident — any later change to the file breaks the proof
  • Hash-linked — later entries lock in earlier ones, so a record can't be silently reordered or edited
  • Signed by an independent service, not by you
  • Your client verifies it independently
  • One link, checkable by anyone, independently
How it works

Three steps. Zero trust required.

You don't have to take our word for it — and neither does your client. The proof checks itself.

1

Upload your file

Drop in the deliverable — a PDF, a design, a contract, a zip. We never store the file itself, only its cryptographic fingerprint.

2

Get a stamped receipt

You get a timestamped, tamper-evident proof: the exact file fingerprint, sealed at a stated time, recorded in a hash-linked chain.

3

Share the verify link

Hand your client a link. They confirm the file and the date themselves — no account, no login, no calling you. The math does the vouching. Verification is served by a system separate from the one that stamps — we run both — so checking a record never goes back through the tool that made it.

What a HashStamp proves

That this exact file — identified by its SHA-256 fingerprint — existed at the stated time, signed by HashStamp's service key and hash-linked into a tamper-evident chain. Anyone can check it without trusting you.

What it does not prove

Who created or sent the file, that a recipient received it, or that the time is independently anchored — the timestamp is provided by the HashStamp service, not an external authority. Pair a stamp with your delivery record (an email, upload, or shared link) to show which version you delivered.

Founding Supporter Status

Founding Supporter Status — a one-time payment.

One payment. No subscription. Back HashStamp early at today's founding rate — tiers step up as seats are taken. Stamping is open to everyone today — this is about supporting the build.

$49 one-time · founding — opening rate

Each record is signed by HashStamp's hosted service key and hash-linked into the ZKNOT chain — a tamper-evident record, not a blockchain — at a time HashStamp states.

You'll continue to Stripe's secure checkout. Your exact price is confirmed there and is authoritative. One-time payment — no subscription.

Not ready to buy? Leave your email and we'll send one note as we ship more — no card, no spam.

No spam, no list-selling. Unsubscribe anytime.
✓ You're on the list. We'll be in touch.
Questions

The honest answers.

Do you keep my files?

No. We compute a one-way fingerprint (a SHA-256 hash) of your file and store only that. We never see or keep the file's contents — we couldn't reconstruct it if we tried.

Is this legally binding?

Hashstamp gives strong, independently verifiable evidence of when a specific file existed and that it hasn't changed since. Whether that's decisive in a given dispute depends on the situation — but "here's cryptographic proof, verify it yourself" is a much stronger position than "trust me, I sent it on time."

Does this prove I actually sent it to my client?

Not on its own — and we're careful not to claim it does. A stamp proves that this exact file existed and was sealed at a specific time, and hasn't changed since. What that kills is the two moves a client can make: "that's not the file we agreed on" and "you backdated it." Pair the stamp with your own send record — the email, the shared link, the upload — and it stands on cryptographic proof instead of your word against theirs.

What can my client actually see?

They see a verification page: the file fingerprint, the timestamp, and a confirmation that it's intact. They never see your account or anything else you've stamped. One link, one proof. A stamp shows that this exact file was recorded at that time — it doesn't assert who created or uploaded it.

What's it built on?

A tamper-evident, hash-linked ledger — the same evidence infrastructure behind ZKNOT. You don't need to understand any of that. You upload a file; you get a proof.