Leaked PDF checks for journalists, newsrooms and fact-checkers
A leaked or submitted PDF arrives with a story attached to it.
A check answers one question about a file: was it edited after it was created? It does not say whether the content is true, who made the file, or why anyone changed it. An unchanged file can still contain false statements, and an edited file can still contain true ones. The result is evidence about the file, to be weighed alongside your own sourcing – never a replacement for it.
Scans, photos and screenshots are never reported as unchanged, because a picture of a page carries no edit history of its own. Other files that carry too little history to decide either way are reported as INCONCLUSIVE rather than clean.
What a file check can and cannot say
The file’s history is one more piece of evidence – not a verdict on the story
When a PDF reaches a newsroom, the first questions are usually about the source and the content. A file check adds a different kind of evidence: whether the document in your hands is the file that was originally produced, or a version someone changed afterwards.
The check returns one of three outcomes – INTACT, MODIFIED or INCONCLUSIVE – together with named findings that explain it. There is no numeric score and no ‘probability of fraud’. Where the evidence does not support a firm statement, the answer is INCONCLUSIVE, and that is a legitimate result.
What it never does: read the text of your document, judge whether the figures are correct, identify who edited the file, or infer intent. A legitimate correction and a deliberate forgery can look the same at file level. Treat a MODIFIED result as a reason to ask for the original and to ask the source how the file was handled.
Questions a check helps with
- Is this the original file, or was it edited after export?
- Was this contract changed after it was signed?
- Do two copies from different sources both hold up as unchanged?
- Was a signature removed from this document?
- Was this record put together from several sources?
- Is the file a scan or screenshot, which no check can call unchanged?
What this looks like
Four situations newsrooms bring to a file check
Three real fraud mechanics we catch at the structural PDF layer.
A signed contract that arrives as ‘the original’
A source sends a contract in which both parties signed. The check reports whether the file was changed after the signature was applied, or whether the signature was stripped. It does not tell you whether the clauses are the ones the parties actually agreed.
A bank statement or financial record from an anonymous source
The file looks like it came straight from a bank. The check reports whether it shows signs of having been changed after it was issued. It cannot confirm that the transactions are real, only that the file itself was or was not altered.
Two copies of the same document from two sources
Two people hand you what is supposed to be the same letter. Running each copy shows whether either carries signs of later changes – a useful prompt for a question to each source, not an answer on its own.
A scan, photo or screenshot of a document
Image-based files are common in leaks. They can never be reported as unchanged, because the picture says nothing about what happened before it was captured. The check still reports what it can about the file, and states plainly what it cannot.
How the press program runs
Source protection
What happens to a file you submit
Only facts from our privacy policy – read it before you submit anything sensitive.
How a file is handled
Depends on how you submit it
- API: the file is fetched from a link you provide, analyzed once and discarded. It is not stored and not used to improve the algorithm.
- Website upload: a copy may be retained after analysis, kept without linkage to your account, and used to test and improve detection.
- The API reads from a link, so the file must be reachable at that address while the check runs.
- We never read the substantive content of your document.
Choose the route that fits the sensitivity of the material and your own threat model.
What stays on record
Results, not the document
- Filename, file size, page count and creation and modification dates
- Creator and producer information, the verdict and the named findings
- Results are private by default and shared only if you switch on a link
- Kept for up to 3 years; deletion on request via [email protected]
What HTPBE? checks
Detection capabilities
Deterministic structural signals. No probabilistic scores, no model training.
Changes after the file was created
Signs that the document was edited and saved again after its original export – the most common question about a document handed over by a source.
Changes after signing
Whether content was altered after a digital signature was applied, and whether a signature was removed.
Dates that disagree
Dates recorded in the file that contradict each other.
Parts that came from different places
Pages or elements that appear to have been produced separately and put together, which matters for assembled bundles and ‘complete’ records.
What the check cannot establish
Who made the file, whether its content is accurate and why it was changed. When the evidence is not enough, the result is INCONCLUSIVE rather than a guess.
Share with engineering
Wire this into your intake pipeline in under a day
Two API calls – one POST to submit the PDF, one GET to retrieve the verdict. Forward this page to your engineering team; the full API reference, quotas, and copy-paste examples in cURL, JavaScript, Python, PHP, Go, and Ruby are one click away.
Press program
Apply for free access
Approved applicants receive a dedicated API key equivalent to our Growth plan. No payment, no time limit, no story disclosure. Manual review only – typically 1–3 business days.
Free for pressEditorial
350 credits/month – Growth-tier equivalent
For investigative reporters and editorial teams at registered newsrooms. Reviewed annually; no quota pressure.
Free for pressFact-checking
350 credits/month – Growth-tier equivalent
For NGOs and teams whose primary mission is fact-checking public claims, government documents, or leaked materials.
Free for pressPress freedom
Custom limits available
For NGOs supporting journalists in authoritarian environments or documenting human rights violations using leaked records.
Need higher limits for a multi-reporter newsroom? – mention it in the application.
Manual review – no automated signups. We do not ask which story you are working on.
FAQ
Frequently asked questions
Can a check tell me whether a leaked document is genuine?
How should I describe a MODIFIED result in a story?
If the result is INTACT, can I treat the document as authentic?
What happens to a sensitive file I submit?
What about scans, photos and screenshots?
Who qualifies for free access, and what does it cost otherwise?
Apply for free access
Approved applicants get the equivalent of our Growth plan at no cost — 350 credits/month, no time limit.
Manual review only. Typically 1–3 business days.
We do not ask which story you are working on.