How to merge PDF files (and get the page order right the first time)

A PDF is a container: a catalogue that lists pages, and page objects that reference fonts, images and content streams. Merging creates a new catalogue and copies each source page into it, rewriting the internal references so that page 1 of the second file points at its own resources rather than at the ones belonging to the page that came before it.

Because the page content streams are copied rather than re-rendered, text stays as text, vectors stay as vectors, and embedded images keep their original bytes. A merge of a 40 KB text document and a 2 MB scan produces roughly a 2.05 MB file, not a re-compressed approximation of both.

That also explains the one case where a merged file can be larger than the sum of its parts: if two documents embed the same font or the same logo, a careful merge keeps one copy of each, and a naive one keeps two. Our merge keeps one. If you merge twenty files that each carry an identical logo, the saving is visible.

Most portals that ask for a single PDF do not care about the internal order, but the human who opens your file does. Reviewers routinely reject or delay submissions where the required document is buried on page 14. The order below follows what most Indian recruitment boards and university admissions cells expect to see, and it is what our merge tool defaults to when you sort files by name.

• Cover sheet or index page, if the portal asks for one. Keep it to a single page and date it.
• The filled application form or acknowledgement slip, first — a reviewer should find it without scrolling.
• Photograph and signature page, if they are supplied as separate pages rather than embedded in the form.
• Identity proof: Aadhaar, passport, voter ID or driving licence. One document, both sides.
• Address proof, if separate from identity.
• Educational certificates in the order they are listed in the notification, not in the order you found the files.
• Experience letters and payslips, most recent first.
• Category or disability certificates, if applicable, with the issuing authority visible.
• Fee receipt or payment confirmation, last.

Nothing stops you merging an A4 form, a Letter-sized scan and a phone photograph of a signature slip. The viewer will show each page at its own dimensions, which is fine on screen and mildly untidy when printed. If the merged file is going to be printed and posted, it is worth normalising every page to A4 first.

Our merge tool preserves original page geometry by default because resizing a page is a lossy operation for anything containing small text or fine print. If you would rather have uniformity, merge first, then run the result through a converter that pads each page to A4 — padding is safe, cropping is not.

Merging is reliable, but four specific situations behave unexpectedly, and all four have an explanation.

• Encrypted files. A PDF can be encrypted with a password you must type to open it, or with an owner password that merely forbids editing while leaving the file readable. The first kind cannot be merged by any honest tool — you need the password. The second kind often merges, but the result may inherit restrictions, so strip the encryption in your reader first.
• Interactive form fields with clashing names. If two documents both contain a field called "name", some readers will show both linked to a single value. Static output is unaffected, but if you are merging fillable forms for actual online submission, use print-to-PDF on each form first.
• Digital signatures. A signed PDF is signed over the exact bytes of that document. The moment it is merged into a larger file, the signature is no longer valid for the new document, and a reader will say so plainly. Keep signed documents as their own submission where the portal allows it.
• Bookmarks and page labels. Merged documents inherit no bookmarks in most simple tools. If you are merging a 200-page report and depend on its outline, merge around the outline rather than losing it — or add a one-page index in front, which is read by more people than bookmarks ever are.

Merging does not increase size meaningfully, so a merged file that will not upload was already too large as separate documents. The fix is compression, and the guide on compressing a PDF to 100 KB walks through the pass order: strip structural bloat first, then re-encode images, and only then reduce resolution.

One shortcut specific to merged bundles: if the bundle contains both text pages and page-sized scans, compress the scans before merging. Each scan can be pushed to a target independently, which lets you decide exactly how much quality a photograph of a certificate needs, instead of applying one global setting to everything. Our compressor accepts multi-page PDFs and reports the before-and-after size per document, so you can see what each pass bought you.

Merging runs inside the browser rather than uploading the selected documents. A connection is still needed to load the page and may be needed to fetch processing code or the PDF worker the first time you use it; offline operation is not guaranteed.

The practical constraint on a phone is memory. Scanned documents can expand substantially while processing, and the amount varies by file and device. If a large job fails, try smaller batches and check the merged result before deleting your originals.