If a PDF signature appears invalid after editing, preserve both the original signed file and the edited copy before making further changes. Signature verification concerns the signed electronic document, its integrity and the trust information available to the verifier. A visible signature image alone cannot answer those questions.
Start by recording the exact status message. A document changed after signing, an untrusted certificate and an unavailable validation service are different situations. This guide describes an operational investigation, not a legal opinion about whether a signature satisfies a particular law or agreement.
Compare the original with the edited copy
Open the untouched original from a trusted source and inspect its signature status. Then inspect the edited file separately. Record which application and version performed the edit and which operations were applied, such as changing text, combining pages, adding annotations or converting the file.
If you cannot identify an untouched original, ask the document owner or signer for one through an approved channel. Do not treat a printed scan or screenshot as a replacement for the original signed electronic document. Those representations can omit the information needed for verification.
Read the validation details in Power PDF
Tungsten's signature-verification instructions describe verifying a signature and opening its properties for more information. Use the detailed result rather than the appearance of an icon alone. Record whether the reported issue concerns document changes, certificate trust, identity or another validation condition.
Check integrity separately from identity
An application recognizing a certificate does not establish that every later document change was authorized. Likewise, an identity that your organization knows through other channels may still require the correct trust configuration for technical validation. Keep these questions separate in the support record.
Do not trust a certificate just to remove a warning
Follow the organization's approved trust and verification procedure. Confirm the signer's identity and certificate information through an appropriate independent route where needed. Adding an unknown identity to a trusted list simply because the PDF requests it defeats the purpose of the check.
| Observation | Next investigation |
|---|---|
| Original validates; edited copy does not | Changes made after signing and permitted modification rules |
| Both show an untrusted certificate | Approved certificate trust and identity verification |
| Status cannot be determined | Validation details, service availability and administrator guidance |
| Only a handwritten image is present | Whether the document contains a verifiable digital signature at all |

Determine whether the edit was supposed to be allowed
Digital-signature and certification workflows can impose different modification rules. Consult the document owner and the signing and certification guidance for the actual workflow. Do not assume that a harmless-looking formatting change is outside the signed content or that every annotation is permitted.
If the business process requires another version, create a clearly identified revision and follow the approved signing sequence. Avoid manipulating the display of the signature so the revised document appears to retain a validation result it no longer has.
Keep conversion and printing out of the repair path
Printing to a new PDF, flattening the page or scanning a paper copy may change the document representation. These operations should not be described as repairing the original signature. They can produce a readable copy while losing the original electronic verification context.
If a recipient only needs a visual reference, label that copy appropriately and preserve the signed original. If the recipient requires a valid signed electronic file, ask for the correctly prepared revision rather than substituting a transformed copy.
Record the change sequence
Create a brief timeline: original received, signature checked, edit made, file saved and status observed. Include the names of both files, the editing tool and the exact action. Remove confidential content from screenshots and share them only through the organization's authorized support route.
This record helps the signer, application owner or administrator reproduce the problem. Repeatedly opening and resaving the file in several products before collecting evidence can obscure which transformation first changed the status.
Decide the next step with the document owner
Possible outcomes include retaining the original and a separate working copy, issuing a corrected version for a new signature, or resolving an approved trust-configuration issue. The correct choice depends on the validation details and the process that governs the document.
Our PDF workflow selection guide explains why signing requirements deserve their own acceptance test. For this incident, preserve the original, identify the actual validation failure and keep any revised copy clearly distinguished from the signed source. A clean-looking page is not evidence that the original signature remains valid.
Before transforming a signed copy, review what flattening changes and what it does not protect.

