Verifying a PDF digital signature, step by step
A signed PDF carries a green checkmark and a name, and it is tempting to read that as "this document is authentic and correct." Digital signatures are powerful, but they answer a narrower question than most people assume. This article walks through what a signature actually verifies, how the verification works, and where the trust ends.
What a PDF digital signature proves
A properly applied PDF signature is a cryptographic seal over the document's bytes at the moment of signing. It can demonstrate:
- Integrity. The document has not been altered since it was signed. Change a single character and the signature breaks.
- Authenticity. The signature is tied to a signer's private key, and the corresponding certificate identifies who (or what organisation) held that key.
- Non-repudiation. Because only the signer's private key could produce the signature, the signer can be held to having produced it.
These are strong, verifiable claims — and they are not the same as "the document's contents are true."
How verification works
When a reader validates a signature, it performs a chain of checks:
- Hash check. It recomputes the document hash and compares it to the signed hash. A match means no bytes changed.
- Certificate chain. It verifies the signer's certificate chains up to a trusted root certificate installed in the system or reader's trust store.
- Validity period. The certificate must have been valid at signing (a trusted timestamp helps prove when).
- Revocation. The certificate should not appear on a revocation list (CRL/OCSP) as compromised.
Only when these line up does the reader show a valid signature.
What a signature does NOT mean
This is the part people get wrong:
- It does not vouch for truth. A signed contract can still contain false statements; the signature proves only that the signed party put their key to those exact bytes.
- It does not guarantee the signer is who you think. A certificate's identity claim depends on how carefully the certificate authority vetted it. A self-signed or poorly issued cert is mathematically valid but weakly identifying.
- A later edit breaks it — by design. If someone adds a page after signing, the signature will (correctly) show as invalid or cover only part of the file.
Treat a valid signature as evidence of integrity and origin, not of accuracy. This is exactly why a signed document still deserves the same skepticism you would give an unsigned one.
How to verify it yourself
You do not need to be a cryptographer:
- Open the signed PDF in a reader that shows signature details (valid / invalid / unknown).
- Expand the panel to see the signer name, certificate issuer, and signing time.
- Check whether a trusted timestamp is present — it proves the signature existed before a certificate later expired or was revoked.
- If the reader flags "certificate not trusted," inspect the chain; it may be a legitimate cert your trust store simply does not recognise.
For the wider context of opening untrusted files, see security risks when opening PDFs.
A reference table
| Claim | Signature proves it? | Notes |
|---|---|---|
| File unchanged since signing | Yes | Hash match |
| Signed by key holder | Yes | Via cert chain |
| Contents are true | No | Not its job |
| Signer identity certain | Maybe | Depends on cert vetting |
| Signed before revocation | With timestamp | Otherwise uncertain |
When signatures matter most
Signatures earn their keep in workflows where tamper-evidence is the point: signed contracts, regulatory filings, approvals, and court exhibits. There, "unchanged since signed by X" is exactly the assurance you need. Just keep the distinction crisp: the seal guards the bytes, not the facts.
Timestamps and long-term trust
Certificates expire and can be revoked, which creates an awkward question: does a signature made years ago still mean anything? A trusted timestamp answers this by proving the signature existed before the certificate expired or was revoked. Without it, a signature valid today may show as uncertain tomorrow, not because the document changed, but because the confirming clock is ambiguous. For documents meant to matter for years — contracts, permits, archives — insist on a timestamped signature, and verify it in a reader that displays the signing time clearly.
Conclusion
Verifying a PDF signature is straightforward: confirm the hash matches, the certificate chains to a trusted root, the timing is right, and the certificate was not revoked. That gives you solid proof of integrity and origin. What it never gives you is a verdict on whether the contents are true — only on whether they are the untouched bytes the signer sealed. Open signed documents in a trustworthy offline reader so you can inspect the signature details without exposing the file to anything else.
FlyPDF does this locally. Read-only by design: OCR, search, annotations and text export all run on your machine, and the source file is never rewritten.
Try FlyPDF free for 30 days