A failed merge can mean the files exceed a limit, contain unsupported features, or are not readable PDFs. Start with the exact message in the tool. Repeating the same selection will not fix an incompatible file, and renaming it will not change its format.
Match the message to the next action
| Problem | Check | Next step |
|---|---|---|
| Too many files | More than 20 selected PDFs | Choose only the intended documents or use a tool supporting your complete packet. |
| Too many bytes | Combined input size above 25 MB | Remove unintended files or obtain suitable smaller exports. ServeJet has no compressor. |
| Too many pages | More than 100 pages across all sources | Review the required packet and choose a workflow supporting its full length. |
| Unreadable PDF | Incomplete download, damaged structure or a renamed non-PDF | Open the source in a viewer and obtain a fresh export or download from its owner. |
| Encrypted file | Password or encryption protection | Use the authorized source workflow. ServeJet has no password-entry or unlock feature. |
| Interactive form | Form fields remain in the document | Decide whether the recipient needs a fillable form before making any static copy. |
| Signature or signature field | Digital-signature data or an empty signature field | Keep the original and return to the signing workflow. |
Check totals, not just the largest input
Three PDFs of 9 MB each exceed the combined size limit even though each is below 25 MB. Four 30-page files exceed the 100-page limit. Merging small groups first does not make the same final packet fit those limits; it can also make it harder to track which original pages are included.
Find the incompatible source
Open each original in a normal viewer and confirm that it displays correctly. Then try a small set of ordinary, unsigned PDFs that fit the limits. If that works, review the remaining sources for the condition named in the error. Do not repeatedly process a signed file in the hope of removing its restriction.
A source that opens successfully can still be unsuitable for page copying. A completed form may still contain active fields, and a blank signature field can trigger the signature check without any visible handwritten signature. The form-field guide explains why appearance alone is not enough.
When the browser is the problem
Save any completed download before refreshing. If the tool controls never initialize, check that JavaScript is enabled and the page has loaded. Reopen the page and choose files again. Closing the tab clears its work; it does not leave a server-side draft to recover.
If a supported selection still fails, keep the originals and use another appropriate tool. Do not send sensitive documents in a public support message. A useful problem report describes the error, file count, approximate total size, page count and browser without including document contents.
Review a successful output too
A download is the start of verification. Check page count, order, orientation and legibility. Page copying may omit bookmarks, attachments or other document-level features. If a recipient depends on those features, choose a workflow that explicitly supports and verifies them.
General information and document organization guidance, not legal advice. Check the instructions for your jurisdiction and destination.