Digitally signed PDFs: what the signature proves, why the file locks, and when to remove it

Two things called a signature

The word “signature” covers two very different things in a PDF. A visual signature is an image of handwriting placed on the page — drawn, typed in a script font or scanned. It shows intent, and it is what most everyday paperwork asks for, but anyone can copy it and nothing in the file ties it to a person.

A digital signature is cryptography. When someone signs digitally, their software takes a fingerprint of the document’s bytes, seals that fingerprint with the private key behind their certificate, and stores the result inside the file together with the certificate itself. In practice this is what happens when you sign with a government ID card, a qualified certificate or the “sign with certificate” option of a desktop PDF editor.

What the reader checks when you open it

Every time a signed PDF is opened, the reader recomputes the fingerprint of the signed bytes and compares it with the sealed one. If they match, the document is exactly as it was when signed. If they do not, even by one byte, the reader reports that the document has been altered since it was signed. Separately, it checks whether the certificate is trusted, which is why a perfectly intact signature can still carry a warning when the authority that issued the certificate is not on the reader’s trusted list.

This is the whole value of a digital signature: it makes tampering visible. It does not stop anyone changing the file — it makes sure the change is noticed.

Why signed and certified PDFs lock

A certification signature goes one step further. The first signer — typically the author — records which changes are allowed afterwards: none at all, only filling in forms and adding signatures, or comments as well. Readers enforce that choice by disabling their editing tools, which is why a certified PDF can appear “locked” or “secured” even though it has no password.

Tools that modify the file hit the same wall from the other side. Merging, compressing, rotating or filling in a signed PDF produces a document whose signature no longer matches, so the result opens with a warning that it was changed. Nothing is wrong with the new file; it simply carries a signature that describes a different document.

When removing a signature is the honest fix

If the document is yours, a signature that no longer describes it is just noise. Removing it gives you a clean, ordinary PDF instead of one that tells whoever opens it that it was altered. Typical cases:

• You certified a template or form yourself and need to update it.
• A draft was signed too early or with the wrong certificate, and must be signed again.
• You need to combine or shrink signed pages, and the result would be flagged anyway.
• An old form carries Adobe Reader usage rights that now trigger warnings.

What removal can never do

Removing a signature does not transfer it, forge it or leave the edited document “still signed”. The proof of who signed and when lived inside the signature, and it leaves with it. Passing an altered copy off as the signed original is a different act altogether, and in most places it is fraud. Keep the signed file as your record, and treat the unsigned copy as a working document.

It also cannot open a file you have no way to open: if the PDF needs a password, you still need that password. Restrictions that only stop printing, copying or editing are different — they come off without one.

Doing it without handing the document over

Signed documents are often the most consequential ones — contracts, certificates, official forms — so uploading them to a website to strip their signatures is a poor trade. Pdfect’s Remove signature tool does it in your browser: qpdf compiled to WebAssembly decrypts and rewrites the file, a PDF library removes the signature fields and their stamps, and the result is downloaded straight from the tab. You can disconnect from the internet after the page loads and it still works.