Can you merge a PDF without losing its digital signature?

Why does merging break a digital signature?

A digital signature in a PDF is a cryptographic object, not a picture. The PDF specification says a byte range digest is computed over a range of bytes in the file, indicated by the /ByteRange entry in the signature dictionary. That range is meant to be the entire file, including the signature dictionary but excluding the signature value itself. To validate, a viewer recomputes the digest and compares it with the one stored in the signature.

So the signature vouches for a specific run of bytes. Change those bytes and the recomputed digest no longer matches. Most merge tools do not append to your file. They copy the pages into a brand new document, which is a different byte stream. There is nothing left for the original byte range to point at.

We tested the copy step with pdf-lib, the library our merge tool uses. Its page copy output contains no signature field and no signature value at all. In that case the signature is not shown as broken. It is simply gone. Other tools that re-save the whole file can keep the field but fail the digest check.

The specification does not literally say "copying pages invalidates a signature". That conclusion follows from how the digest works. An Adobe Community answer says the same in plain words: a digital signature, unlike a wet signature, applies to the entire document as a whole.

What do you actually see in a PDF viewer?

It depends on what the tool did. If the signature field was dropped, the merged PDF simply looks unsigned. If the field survived but the bytes changed, a validating viewer reports a problem. Adobe's engine documentation defines two relevant statuses. One is "The revision of the document that is covered by the signature has been altered." The other is "The document or dynamic form has been altered or corrupted since the signature was applied."

We could not find a fetchable Adobe page that quotes the exact banner text Acrobat Reader shows, so we do not quote one. Open the merged file in Acrobat Reader and read what it says yourself. The section below shows how.

Can you merge a PDF without removing a DSC?

Not into one ordinary PDF. People often ask this about a DSC, the digital signature certificate used on Indian government and tax documents. The same mechanism applies to any certificate based signature. A single merged file cannot carry the original signature intact. That is a property of how the format works, not a missing feature in one tool.

Some tools promise to merge without losing signatures. For a true page copy, the design of the format makes that impossible, because a changed byte stream cannot satisfy a digest computed over the old one. The only way a tool could keep an original signature valid is to leave the signed file untouched and attach to it, which does not produce one combined document.

What are the three real workarounds?

1. Keep the files separate. Send or upload each signed PDF as it is, named so the order is clear, or put them in a ZIP. Smallpdf's guide on this topic advises the same when you cannot get the files signed again. We read that line in a search result, so check the page before relying on its exact wording.
2. Use a PDF Portfolio. A portfolio is a PDF container that holds other files as attachments. The specification describes a collection as file attachments located in the EmbeddedFiles name tree. Whether an embedded signed file stays valid is not stated in the specification text we read. Adobe Community answers say signed files can only be combined into a portfolio, which keeps them separate, and that not every viewer opens a portfolio. Those are user answers, not Adobe documentation, so test it with your recipient's viewer.
3. Merge first, then sign again. Remove the signatures, merge the unsigned files, then apply a fresh signature to the combined file. A Soda PDF support article describes this route, and it is the usual advice from signing vendors too. It needs the signers to sign again, which is not always possible.

If the document was certified (the first signature in a file can carry a DocMDP setting), the specification lists how many later changes are tolerated. Level 1 permits none, level 2 permits filling in forms and signing, and level 3 adds annotations. Page copying is not on that list.

Can you compress a PDF without losing a digital signature?

No, for the same reason. Compression rewrites the bytes of the file. Our compressor goes further: its size based modes re-render each page as a JPEG, so the output is a new document with no signature in it. Even the mode that only recompresses embedded images changes the file bytes, so the original digest cannot match.

If you must shrink a signed file, compress the unsigned original first and sign the compressed copy. If you cannot, ask the sender for a smaller export or send the signed file by a link instead of an attachment. Our compress tool is fine for unsigned files and for the copy you sign afterwards.

Is a picture of a signature the same thing?

No. A scanned or drawn signature is page content. A glossary on PDF2Go puts it this way: an image of handwriting is page content and carries no cryptographic claim at all. A certificate based signature lives in a signature value over the byte range described above.

That also means an image signature survives a merge, because it is just part of the page. It proves nothing about who signed or whether the page changed. Our sign tool places a visual signature of this kind. It is not certificate based, and we make no claim that it is legally binding.

What does EasyPDFLoad do when you add a signed file?

When you add files to the merge tool, it reads each one in your browser tab and looks for a digital signature. If it finds one, it shows a warning with the file names before you merge. The warning says the signature will be invalid in the merged copy and links to this guide. The check reads the file locally and does not upload it.

The check has real limits, and you should know them:

• It checks structure only. It does not verify the signature, so a signature that is already broken still triggers the warning.
• It only finds signatures reachable through the form field tree (the AcroForm fields). A signature stored elsewhere is not seen.
• A file it cannot parse is treated as unsigned, so a damaged file gives no warning. An unparseable file is a false negative, not a clean bill of health.
• It warns. It does not stop you from merging, and the merge itself still drops the signature.

If you only need some pages from a signed file, the split tool also produces a new file, so the same rule applies. For the basics of combining files, see our guide to merging PDFs.

How can you check this yourself?

Do not take our word for it, or any vendor's. Take a PDF that carries a real certificate based signature and open it in Acrobat Reader or another viewer that validates signatures. Note the signature panel. Now merge it with any tool, ours or a competitor's, and open the result in the same viewer. Look at the signature panel again and read the status text. If a tool claims to keep signatures intact, this test settles it in a minute.

To confirm our detection stays on your device, press F12, open the Network tab, tick Preserve log, then add a signed file to the merge tool. You should see no upload request of roughly the file's size. This is a check you can run, not a certification.

Straight answers (Can you merge a PDF without losing its)

Related to Can you merge a PDF without losing its

• Merge PDF: Combine multiple PDF files into a single document in seconds.
• Sign PDF: Add a drawn or typed signature to a PDF, positioned anywhere on the page.
• Compress PDF: Shrink a PDF to fit email and upload limits, with a level or target size.
• Split PDF: Split a PDF into separate single-page files or extract a page range.
• How to merge or combine PDF files without Adobe
• Merge PDF Without Uploading? “No Sign-Up” Isn’t “No Upload”