Digital Signatures on PDFs

Overview

“Signing a PDF” can mean two very different things. A drawn or typed signature appearance is a visual mark—useful for intent, weak as technical proof. A digital (cryptographic) signature uses a certificate to seal document bytes so verifiers can detect later changes and identify the signer’s credential.

PDF software often shows both: an appearance stream (the look of a signature) and a cryptographic signature dictionary (the math). When people say a document is “unsigned” after you stamped a PNG of your name, they are talking about the cryptographic layer, not the artwork.

Dockzio’s pdf-signature tool helps place signature appearances for everyday document workflows. Pair that with pdf-protect when you need passwords or permissions controls—understanding that password protection and digital signatures solve overlapping but distinct problems.

Step-by-step

1. 1. Choose appearance-only vs cryptographic signing

   Use a visual signature when counterparties only need a conventional signed look for informal agreements or internal routing.

   Use a certificate-based digital signature when you need tamper evidence, identity binding, or compliance with a policy that requires cryptographic signing.

2. 2. Finalize content before you seal the file

   Cryptographic signatures hash the document. Editing pages, compressing aggressively, or merging after signing typically invalidates the signature.

   Complete merges, redactions, and compressions first. Sign last—or re-sign after any approved change.

3. 3. Apply the signature appearance in the right place

   Place marks on designated signature lines without covering critical terms. Keep a clear margin so printing and flatbed scans do not clip the mark.

   With pdf-signature, preview placement at realistic zoom. A signature that looks fine at 70% zoom can collide with text at 100%.

4. 4. Add protection appropriate to distribution

   Password permissions (via pdf-protect) can discourage editing or printing, but a determined user may still work around simple restrictions. Treat permissions as a speed bump, not a vault.

   For sensitive files, combine access control in your sharing platform with the PDF controls you actually need. Unlock only when you have authorization (pdf-unlock).

5. 5. Verify how recipients will validate

   Ask whether they check signature panels in Acrobat/Reader, require a specific certificate authority, or only look for a visual mark.

   If validation matters, do a round-trip test: sign, open on a clean machine or reader profile, and confirm the signature status matches expectations.

Common mistakes

• Confusing a scratched signature image with a digital signature. A PNG of your pen stroke does not by itself prove integrity. Call it what it is—an appearance—unless a certificate signature is also applied.
• Editing after signing. Even “harmless” metadata changes or page reordering can break cryptographic validity. Freeze the file or use incremental update workflows designed for multi-signer review.
• Sharing the only unencrypted copy broadly. Signatures prove tampering after the fact; they do not stop unauthorized reading. Use appropriate sharing controls for confidentiality.
• Stacking multiple visual stamps until the page is unreadable. Initials, dates, and approval stamps should stay legible. Prefer structured approval fields over decorative clutter.