PDF security blog

The Anatomy of a Modified PDF: Reading a Result

HTPBE Team··5 min read
The Anatomy of a Modified PDF: Reading a Result

This article is a snapshot – content was accurate as of November 2025 (code examples tested against the API as of October 2026). The product evolves actively; specific counts, examples, and detection rules may have changed since publication – see the changelog for the current state.

A PDF that has been edited rarely looks edited. The numbers line up, the fonts match, the layout is clean. The page you see tells you nothing – which is exactly why a result from a forensic check is worth reading closely.

This article walks through an illustrative case, not a specific customer file: an invoice that arrives by email and looks entirely ordinary. It shows what a reader sees in an HTPBE? result, which checks fire, what each one means in plain words, and what to do next.

The document that looks fine

Imagine a supplier invoice. The logo is right, the totals add up, and the sender is a company you pay every month. Nothing on the page raises a question.

Opened in a viewer, a modified file and an original file are indistinguishable. The evidence is not on the page. It sits in how the file was produced and what happened to it afterwards. HTPBE? reads that evidence – never the visible content – so a clean-looking page does not change the result.

The three verdicts

Every check ends in one of three verdicts:

  • Intact – no signs of modification were found.
  • Modified – the file shows signs of having been changed after it was created.
  • Inconclusive – the file’s origin cannot support either answer. Some files, such as exports from consumer office software, land here. See what an inconclusive result means.

Next to the verdict comes a confidence level: certain, high or none. There is no numeric risk score. A verdict, a confidence level and a named list of checks that fired are the core of the answer.

The checks that fired

Suppose our invoice comes back Modified. The result lists the public checks that fired. Here are four you might see, with the plain meaning of each. The full catalogue is on the How it works page and in the API’s modification_markers array.

HTPBE_MULTIPLE_REVISION_LAYERS – ‘Multiple revision layers – the document was modified after creation’ The file carries more than one saved version of itself. In plain words: the file’s own history shows it was changed after it was first created.

HTPBE_EDITING_TOOL_FINGERPRINT – ‘Fingerprints of a known PDF editing tool’ The file shows signs of having been processed by PDF editing software after it was created.

HTPBE_DATES_DISAGREE – ‘Modification date that differs from the declared creation date’ The file’s own timing records indicate it was changed after it was created. For a document that should not have changed since issue, that needs an explanation.

HTPBE_POST_SIGNATURE_EDIT – ‘Content changed after the document was digitally signed’ This is the clearest case. A signature was applied, and the file changed afterwards. If the invoice, or a signed contract, comes back with this check, it is treated as direct evidence of a change.

A Modified result lists every check that contributed to it. Several together give a fuller picture of what happened to the file.

What the confidence level tells you

  • Certain – the file contains direct evidence of a change, such as an edit made after a digital signature was applied.
  • High – the file shows clear signs of modification.
  • None – attached to Intact and Inconclusive results: no modification was found, or the file cannot support a verdict either way.

What to do next

For a Modified result:

  1. Do not act on the document yet – no payment, no approval, no onboarding.
  2. Ask the sender for an explanation and for the original file.
  3. Confirm the key details through a channel you already trust, not the one the document arrived by.
  4. Keep the result and its list of checks with your records.

For an Inconclusive result, treat the file as unproven rather than clean and ask for the original from its source.

For an Intact result, you have one more piece of evidence, not a guarantee. No automated check proves that a document is genuine, and Intact means only that no signs of modification were found. It says nothing about whether the content is true.

A Modified verdict reports that the file was changed after it was created. It does not say why or by whom, so read the result alongside where the document came from.

Go deeper

This article stays at the level of what a result looks like. For the mechanics, three other articles take different angles:

To see the metadata a file declares about itself, open it in the free PDF metadata viewer.

Try it on your own files

HTPBE? runs more than 60 forensic checks on every upload and returns the verdict, the confidence level and the list of checks that fired. Teams that receive documents at volume can send them through the API and read the same fields in code. Pricing starts at $15 a month, and pay-as-you-go credit packs are available without a subscription.

If you have only the one file and no original to compare against, pdf forensics without the original file explains what that check can prove and when the answer is ‘cannot tell’.

Share this article

Found this article helpful? Share it with others to spread knowledge about PDF security and fraud detection.

https://htpbe.tech/blog/anatomy-of-modified-pdf-algorithm-detects

Secure your workflow

Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.