Know if a document was edited before you act on it

Forensic fraud signals for statements, payslips and proofs of address. Free checker, developer API — nothing is ever stored. Risk signals, never verdicts.

Get an API key

No account needed to check a file · 25 free API calls/month · nothing is stored

Redacted payslip · page 1

Covered on screen, untouched in the bytes — and the same pass reads the file's edit history back out with it. Eleven signal families run on every PDF.

  1. Drop a file. PDF, Word, Excel, PowerPoint or an image — parsed in memory, never written to disk.
  2. Read the signals. Each one shows the raw evidence behind it.
  3. Automate via API. One POST returns the same JSON report.

Drop a document or image here, or browse

Max 10 MB · processed in memory, never stored

No PDF handy? Try a sample:

Three fictional utility statements. Their reports are precomputed, so they cost nothing and take no upload.

Have the original of the file you are checking? Compare the two directly — the strongest check there is.

Everything it looks for

Eleven families for PDFs, nine more for images — what each one measures and why it fires on honest documents.

Simple pricing, one meter

Every plan runs the same engine and the same signals — you pay for volume, never for better detection. One document is one inspection; a comparison against an original counts as two.

Free

$0

25 documents/month

Full report, web checker, API — no card.

Start free

Solo

$15/mo

200 documents/month

For one integration or a small practice.

Sign up

Starter

$49/mo

1,000 documents/month

Adds private issuer baselines.

Sign up

Growth

$199/mo

10,000 documents/month

Adds priority email support.

Sign up

Self-serve upgrades and cancellation, no contract — full pricing details.

Common questions

Can you really tell if a PDF was edited?

Often, yes. A PDF records more history than it shows on screen: incremental-update revisions appended after the original save, Info dictionary dates that disagree with the XMP metadata, changed /ID pairs, editor fingerprints in the Producer field, and digital signatures that no longer cover the whole file. Tamperlens reads those byte-level traces and reports each one together with the raw evidence behind it — the field guide walks through all eleven signal families.

Does a changed modification date prove the document is fraudulent?

No. Legitimate tools rewrite PDFs all the time — scanners, print-to-PDF drivers, e-signature platforms and archiving systems all leave edit traces. That is why Tamperlens reports risk signals, never verdicts: each signal shows what the bytes say, and the judgment about the document stays with you.

Is my document uploaded or stored anywhere?

The file is sent over HTTPS, parsed in memory and never written to disk. Nothing about the document persists after the response — there is no account requirement for the free checker and no document retention on the API. The privacy policy spells this out.

Can I automate checks from my own code?

Yes. One HTTP POST returns the same report as JSON, so the checks drop into an onboarding or lending pipeline with a few lines of code. The free tier includes 25 documents a month; the API quickstart covers authentication, the report schema and pricing.