File formats

What a Signed PDF Actually Proves

PDFs are designed to look like paper and proof never appears on screen. That is the whole of it.

Robert Smith 9 September 2026 7 min read

A signed PDF proves something only when the signature is cryptographic. Three different things in a PDF get called a signature. A picture of one. A form field holding a typed name. A cryptographic signature over the file. Only the third can tell you anything about the document. Nothing on screen distinguishes them.

This is written for the receiving end. Almost everything published about signing is aimed at whoever signs. Rather less exists for the person handed a signed document who wants to know what the tick means.

Three Things Called a PDF Signature

They look similar on a page and they are not remotely the same object.

An image A picture pasted onto the pageScanned ink or a drawn line. Copyable onto any other document in seconds. Proves nothing about the file it sits on
A form field A typed name in a boxRecords that somebody filled it in. Editable afterwards like any other field. No harder to change than the rest of the form
A cryptographic signature A calculation over the bytesTies a specific version of the file to a specific key. The only one of the three that detects a change

The first two are statements of intent. The third is a fact about the file. Legal systems care a great deal about intent, so all three can matter. Only one of them answers whether the document you hold is the document that was signed.

A visible mark and a cryptographic signature are unrelated. A document can carry one, both or neither. Automated systems sign without any mark at all. Plenty of documents carry a handsome signature graphic with nothing behind it. Appearance cannot tell you which you are looking at.

What a Real PDF Signature Actually Does

The mechanism is short and it explains every limitation that follows.

1  hash the document
     a fixed length fingerprint of the bytes

2  encrypt that hash with the signer's private key
     only the holder of that key can produce this

3  attach the result and the signer's certificate
     that certificate says who the key belongs to

Verifying runs the same thing backwards. The reader hashes the document again, decrypts the attached value with the public key, then compares the two. Matching means the bytes are unchanged since signing.

This is hashing with a key attached. The hash answers whether anything changed. The key answers who could have produced it. Neither half works alone, which is why a checksum published beside a download proves integrity and not origin.

What a Valid Signature Does Not Mean

The tick is precise about a narrow thing and people read it as a broad one.

Valid means	Valid does not mean
The covered bytes are unchanged	The whole document is unchanged
The signing key was used	The named person used it
The certificate chain checked out	The issuer verified anybody carefully
Your reader trusts the issuer	You should trust the issuer
Something was signed	The signer had authority to sign it
It verifies now	The certificate was valid at signing

The identity half rests entirely on somebody else's diligence. A certificate says this key belongs to that person because an issuer says so. The mathematics is sound and the claim underneath it is only as good as the checking that issuer did, which varies enormously and is not visible in the document.

The Signature Gap That Comes From How PDFs Save

Here is where this meets the format rather than the cryptography.

A signature covers the file as it stood at that moment. Because a PDF grows by addition, more can be appended afterwards. The signature still verifies, correctly, for the version it covered.

What was signed

Revision 1

pages 1 to 4
signature applied
  covers everything
  above this point

Sound. It stays that way regardless of what follows. What happens next undoes none of it.

What arrives

Revision 2

pages 1 to 4
signature
  ...appended...
pages 5 and 6
  outside the
  signature

The signature still verifies for pages one to four. Pages five and six were never covered.

Readers do report this. The panel says the signature covers a previous revision and later changes exist, which is exactly right and is also a sentence people skim past on their way to the green tick.

Signatures can be applied to allow certain later changes on purpose. Filling in form fields, adding further signatures. That is a legitimate design for a document going round several people. Later revisions are not automatically suspicious. It means they are worth reading rather than ignoring.

Why Old PDF Signatures Stop Verifying

A document that verified in 2019 can show a warning in 2026 with nothing whatever wrong with it.

Certificates expire. Signing happened while the certificate was good. Years later a reader cannot confirm that unless something recorded the time independently.

With a Trusted Timestamp

An independent record of when
Still verifiable after expiry
Added at signing, not afterwards

Without One

Only the signer's own clock
Warnings once the certificate expires
Nothing can be added later to fix it

This is the archival problem in miniature. A signature meant to prove something years later needs the timestamp at the moment of signing. Nobody thinks about it then.

Reading a Signed PDF Properly

Open the signature panel, not the page. Every reader has one. It names the signer, the issuer, what is covered and whether later revisions exist. That mark is decoration.
Read who issued it. The name on the signature is a claim and the issuer is who vouched for it. An issuer you have never heard of is worth a moment.
Check what the signature covers. Where the panel mentions a previous revision, look at what came afterwards before treating the whole document as signed.
Look for a timestamp. Its presence is the difference between a signature that ages well and one that starts warning the moment a certificate lapses.
Treat a picture as a picture. No panel, no signature. A graphic on a page is worth exactly what a graphic on a page is worth.

Whether any of this is legally binding is a separate question. Jurisdictions differ. A typed name can be binding while a cryptographic signature is disputed. This describes what the file can demonstrate, not what a court will accept.

Why the Confusion Is Reasonable

Nobody arrives at this misunderstanding through carelessness.

On paper a signature is one thing and everybody knows what it means. The digital version split into three and kept the same word for all of them. Then it displayed the weakest one most prominently. A picture of ink sits large on screen. The cryptographic signature, the only one that proves anything, is a panel most people never open.

PDFs are designed to look like paper and proof never appears on screen. Everything else here follows from that. A document that looks convincingly signed has told you nothing. One that looks like nothing at all may carry a signature that would stand up.

Mechanism checked against the referenced articles and the published PDF specification in August 2026. Legal weight differs by jurisdiction and nothing here concerns whether a particular signature is binding.

Questions People Ask

7 questions, answered in full below.

Is a scanned signature on a PDF a real signature?

It is a picture. It shows intent and it proves nothing about the document, because the same image can be copied onto any other file in seconds. Whether that counts as signing is a legal question rather than a technical one.

What does the green tick actually mean?

Two things. The bytes the signature covers have not changed since it was applied. The certificate chain checked out against something your reader trusts. It says nothing about whether the content is true or whether the signer had authority.

Can a signed PDF be changed afterwards?

Added to, yes. A PDF grows by appending, so pages can be added after signing. The signature still verifies for what it covered. A careful reader can see that later revisions exist. A careless one sees a tick.

Does a signature prove who signed?

It proves the private key was used. Whether the person named holds that key depends on who issued the certificate and how carefully they checked. The cryptography is sound and the identity rests on somebody else

Why does a signature go invalid over time?

Usually because the certificate expired or was revoked. The signature was fine when applied and the reader cannot confirm the certificate was still good at that moment. A trusted timestamp exists to answer exactly this and it has to be added when signing.

Can I sign without a visible mark?

Yes. It is common in automated systems. The visible mark and the cryptographic signature are separate things. A file may hold either without the other. The page gives no clue which.

How do I check a signed PDF properly?

Open the signature panel rather than looking at the page. It names the signer, the issuer, what the signature covers and whether later revisions exist. That panel is the document. That mark is decoration.

Sources

Where the figures and behaviour described above were checked.