Verify If a PDF Is Real — Detect a Forged or Modified File
You’ve been sent a bank statement or payslip PDF and need to know if it’s genuine. The common advice — “you need the original to compare” — is wrong. The file’s own structure carries the evidence. HTPBE? reads that structure and tells you whether the document was edited or forged after it was issued. It detects tampering; it is not a KYC or identity-verification platform, and it works alongside KYC rather than replacing it.
There are two different questions hiding inside “verify if a PDF is real.” First: is the content true — does this account really belong to this person, is the salary figure accurate? That is the issuer’s or a KYC platform’s territory, and HTPBE? does not answer it.
Second: was the file edited or forged after it was issued — did someone change a number, swap an image, or rebuild the document outside the bank’s system? That is what HTPBE? detects, structurally, from the bytes of the file itself.
The manual signs
The manual signs people look for — and why they fall short
Most “is this PDF genuine” checklists tell you to open the file’s properties and read the Producer field. If a bank statement says it was produced by Word, Canva, or Photoshop instead of the bank’s core system, that is a real signal — institutional documents come from institutional software, not design tools.
The other manual tells: a Modified timestamp that trails the Created timestamp on a document that should never have changed; fonts that don’t match between lines; suspiciously round numbers; totals that don’t actually sum. Each of these can expose a clumsy edit.
The problem is that doing this by hand is slow, easy to get wrong, and shallow. The eye misses the byte-level evidence — cross-reference table history, revision layers, broken or stripped digital signatures — and most of these checks quietly assume you have the original to compare against. You usually don’t.
What manual checking misses
- Cross-reference (xref) and trailer history showing extra edits
- Revision layers appended by a PDF editor, invisible in a viewer
- A digital signature that was broken or removed after signing
- Producer fingerprints that contradict the claimed issuer
- Font subset drift across pages assembled from different sources
What this looks like
Check a PDF for signs of tampering (free)
Three real fraud mechanics we catch at the structural PDF layer.
Upload the PDF — no account, no original needed
Drop any PDF up to 10 MB into the free checker. You don’t need the bank’s original copy, a reference file, or anything from the sender — only the file you were given. The analysis is one-sided: it reads evidence that lives inside the single PDF.
Every structural layer runs at once
The file passes through all 61 forensic checks — metadata timestamps, cross-reference and revision history, digital-signature state, producer fingerprints, and page-assembly consistency — in under 3 seconds.
Read the verdict: INTACT, MODIFIED, or INCONCLUSIVE
You get a clear verdict with a plain-language list of every finding. MODIFIED means the file was changed after creation; INTACT means no structural editing trace was found; INCONCLUSIVE means the evidence is ambiguous and the document warrants a closer look.
The “you need the original” myth
You don’t need the original PDF to tell if this one was edited
HTPBE? reads the file’s own internal structure — no reference copy required.
Comparison-based checking
Needs a trusted original to diff against
- Requires you to already hold the genuine file
- Useless when the sender is the only source
- Compares pixels, not structure
- Misses edits that preserve the visual layout
Breaks down exactly when you most need an answer.
One-sided structural analysis
Reads evidence inside the single file you have
- Examines xref and trailer history for extra edits
- Checks the digital-signature chain for breaks or removal
- Reads producer fingerprints against the claimed issuer
- Counts revision layers a viewer never shows you
What HTPBE? checks
Detection capabilities
Deterministic structural signals. No probabilistic scores, no model training.
The same check, as a REST API
Send a PDF URL, get back the same INTACT / MODIFIED / INCONCLUSIVE verdict plus named structural markers — deterministic and suitable for an audit trail. Teams wire it into document intake so every uploaded file is screened before a human sees it.
Test keys are free on every plan
Integrate and validate the response shape against synthetic test documents before spending a single live credit. No sales call, no commitment to evaluate the API.
Pricing: free here, API from $15/mo
Checking one file on this page is always free. The automated API starts at $15/month — see the plans below, or read the full API reference to integrate it.
Pricing
Self-serve plans, no sales call
All plans include the same forensic checks. Pick the quota that matches your monthly document volume.
manualStarter
$15/mo
30 checks/mo
Manual spot-checks and integration testing
most commonGrowth
$149/mo
350 checks/mo
Active document processing pipelines
high volumePro
$499/mo
1,500 checks/mo
High-volume automation and API integrations
Enterprise (unlimited, on-premise available) — see full pricing
API key on signup. Free test environment on every plan. No card required.
Customer Stories
Teams that stopped document fraud
Compliance, finance, and risk teams use HTPBE? to catch manipulated PDFs before they become costly mistakes.
Caught an invoice where the total had been changed by less than a thousand dollars. Without this I would have approved it without a second look.
Sarah M.
AP Manager
United States
We had three applicants in the same week with bank statements that looked completely fine. Two of them were flagged as modified. You simply cannot see this by reading the document — it is in the file structure.
Lars V.
Risk Analyst, Online Lending
Netherlands
Salary slips were coming with altered figures. We identified two problematic files before the placement was finalised.
Priya K.
HR Operations Lead
India
Since we started checking documents this way, we stopped two applications early in the process that would have been very difficult to reverse later.
Julien R.
Fraud Analyst, Fintech
France
Some applicants were sending PDFs that looked authentic but had been edited in ways not visible to the eye. We now ask for checked originals when something is flagged. Already saved us from a few bad decisions.
Marta S.
Compliance Coordinator
Spain
One invoice was caught because there was a mismatch between the document dates and structure. That particular case would have cost us significantly.
Tariq A.
Finance Manager
United Arab Emirates
FAQ
Frequently asked questions
Can you tell if a PDF was edited without the original?
What does the Producer field reveal about a PDF?
Is this a KYC or identity-verification check?
Can I check a bank statement or payslip for free?
Secure your workflow
Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.