Verify a Document

Trust Every Document. Instantly.

Upload an original document to verify whether it exactly matches the version registered by its issuer.

Product demonstration — simulated, not a live lookup

Drag and drop your document here

or browse to select it from your computer

Your file is fingerprinted in your browser and never uploaded.

How Verification Works

Three steps. No new workflow to learn.

01

Issuer registers document

  • Original document created
  • SHA-256 fingerprint generated
  • Minimal metadata registered
02

Document is shared

EmailWhatsAppCloudPDFUSBPaper scan

It doesn’t matter.

03

Recipient verifies

  • Upload document
  • Fingerprint calculated locally
  • Compared against registered fingerprint
  • Verification returned instantly

Understanding the Results

Every check ends in one of three states.

VERIFIED

Fingerprint matches. This document is identical to the version originally registered by its issuer.

VERIFICATION FAILED

The uploaded document does not match the registered fingerprint. It may have been modified, corrupted or replaced.

NOT FOUND

No matching fingerprint exists. The document has never been registered or cannot be verified.

Behind the Scenes

What happens in the moment you upload.

Upload
Fingerprint generated locally
Compared against the registry
Metadata validated
Result returned

Privacy & Security

Built to protect, not to collect.

Original documents are never stored.

Only cryptographic fingerprints are registered.

Verification protects document integrity.

Minimal metadata — nothing more than needed.

Enterprise-ready architecture.

An Important Distinction

What Kweli verifies — and what it doesn’t.

Kweli verifies

  • Document integrity
  • Document authenticity
  • Issuer registration
  • Tampering

Kweli does not verify

  • Whether information inside the document is true
  • Business decisions
  • Creditworthiness
  • Medical accuracy
  • Legal validity

Frequently Asked Questions

Questions we hear most.

Upload it in your browser. Kweli computes the document's cryptographic fingerprint locally and checks it against the registry — if it matches what was registered at issuance, the result is Verified. The document itself is never uploaded anywhere.

Whether a document genuinely originates from the issuer it claims to. Kweli establishes this by comparing a presented document's fingerprint against the one its issuer registered at the time of issuance.

Whether a document is unchanged since it was issued. Even a single altered character produces a completely different fingerprint, so integrity is either fully intact or it isn't — there's no partial match.

No. Kweli never stores the original document. Only its cryptographic fingerprint and minimal metadata are registered — the file itself never leaves your browser during verification.

Yes, easily. Text, figures and images in a PDF can be edited with common software in minutes, and the result looks identical to the original to anyone viewing it. PDF format has no built-in way to prove it hasn't changed since it was issued — that's the specific gap Kweli closes.

Yes. Anyone holding a document can verify it independently, without contacting the issuer.

Any change to a document — even a single character — produces a completely different fingerprint. Kweli returns Verification Failed rather than accepting the altered version.

You'll see a Verification Failed result: the presented document's fingerprint doesn't match what was registered at issuance. That means it has been altered in some way since then, even if the change isn't visible to the eye.

A digital signature is applied by the signer at signing time, and verifying it later depends on the recipient trusting that signer's key infrastructure. Kweli instead registers a document's fingerprint independently at issuance, so anyone can verify it afterwards on their own, in their browser, with no key exchange, certificate chain, or prior relationship with the issuer.

Not by itself. A tamper-evident ledger can prove a record hasn't been altered since it was written — that's integrity. Authenticity is a separate claim: that the record genuinely came from the issuer it claims to. Kweli anchors the issuer's registration itself, not just a fingerprint, which is what ties the two together.

Kweli is built as an independent trust layer that fits alongside the systems an organisation already uses, rather than replacing them. Integration specifics are worked out together, based on the systems and workflow involved.

Kweli returns Document Not Found. That means the document was never registered, or the version presented doesn't match anything on record.

Each fingerprint is anchored as a tamper-evident cryptographic proof, so a registered record can't be quietly altered later. The technology is an implementation detail — what matters is that the proof can't be tampered with after the fact.

Get Started

Ready to verify trust at scale?