What happens when you merge a signed PDF
Merging pages creates a new file. The digital signature protecting the original PDF does not automatically validate that copy. A signature image can remain visible without cryptographic validation of the new document.
Steps and checks
- Keep the original signed PDF without overwriting it and confirm whether the recipient accepts a transformed copy.
- Select the PDFs in Merge PDF and check their order and inspection warnings.
- If the system detects a signature, read the warning and confirm creation of a transformed copy only if you accept that consequence.
- Check the page count and order. Also provide the signed original when it is needed for verification.
A drawn signature and a digital signature are different
A signature image or drawing is part of the page appearance. A digital signature uses cryptographic data linked to the document. Copying the image does not recreate that protection. User PDF does not certify legal validity or replace a validator required by the recipient.
Why does the tool ask for confirmation?
The warning prevents treating the new file as the signed original. If a task returns signed_document, review the transformed-copy confirmation before trying again. Resubmitting without accepting the condition can produce the same block.
Does this also affect conversions?
Converting PDF to Word, changing pages, or compressing can alter the structure protected by a signature. Even when content looks the same, do not assume the signature remains valid. Verify the original with an appropriate validator and treat the result as a copy.
What if I need to keep the signed document?
Keep and send the original separately from attachments if the recipient process allows it. Do not convert solely for convenience when the requirement is the signed original. The absence of a warning is not an authenticity certificate either.