Digital Signature Shows Invalid After Making Small Changes to the PDF
A digital signature that becomes invalid after any edit is working correctly — signatures are designed to detect changes. Learn what changes break signatures and what does not.
Seeing "Signature is invalid" or "Document has been altered or corrupted since it was signed" after making what seems like a minor change to a signed PDF is not an error — it is the signature working exactly as designed. Digital signatures cryptographically bind to the exact document content at signing time. Any modification, even adding metadata, invalidates the signature. Understanding what counts as a "change" helps you work with signed PDFs correctly.
Why Any Change Invalidates the Signature
A PDF digital signature computes a cryptographic hash of all document content at signing time and encrypts it with the signer's private key. When you open the signed PDF, the viewer: decrypts the hash (proving who signed), recomputes the hash of the current content, and compares the two. If the content changed — even by one byte — the hashes differ and the signature is invalid. This is the entire security guarantee: you cannot modify a signed document without detection. Adding a word, changing metadata, adding an annotation, or even re-saving with a compression change all modify the document bytes and invalidate the signature.
What Can Be Done After Signing Without Invalidating
Certification signatures (the first signature on a document) can specify which changes are allowed without invalidating: (1) no changes allowed (fully locked), (2) form filling allowed (recipients can fill fields but not change content), or (3) form filling and commenting allowed. If the signing was done with option 2 or 3, recipients can fill forms or add comments without invalidating the certification signature. Approval signatures added after the certification (by other signers) are also valid in this scenario — each signer adds their signature to the already-signed state.
How to Make Changes and Re-Sign
If you need to modify a signed PDF: you must obtain a new signature after making changes. The workflow: (1) note that the original signature will be invalidated, (2) make the necessary changes, (3) have the signer re-sign the modified document. There is no way to retroactively "fix" a signature after content changes — the signature is evidence that the content was a specific value at a specific time. If the original signed version is needed for records, keep it archived separately and create a new document version for the modified+re-signed copy.
Adding a Timestamp to Preserve Validity Long-Term
Signatures without a timestamp expire when the signing certificate expires (typically 1-3 years). After certificate expiry, even a completely unmodified signed PDF shows "Signature is invalid" because the certificate can no longer be validated. Prevent this: when signing, add a Document Timestamp from a trusted Timestamp Authority (RFC 3161). The timestamp proves the document existed before the certificate expired, preserving validation indefinitely. In Acrobat Pro: the signing dialog has an option to contact a timestamp server — configure it before signing important long-lived documents.
Legitimate Invalid Signatures vs Tampered Documents
Not all invalid signatures mean tampering. Common innocent causes: (1) the signing certificate expired, (2) the document was opened in a viewer that automatically saves the file on close (some older Preview versions did this), (3) a PDF optimization or compression tool modified the file after signing, (4) the email client re-encoded the attachment. Before concluding a document was tampered with, check when the certificate expired and whether the file was processed by any automated tools after signing.
Try Edit Pages Now — Free
Browser-based, private, and instant. No account or software required.
Open Edit Pages