Merge PDF - Combine PDF Files Online (Private, No Upload)

1. Merge flow

Filename sort is not business order. Contracts often need cover → body → exhibits; photo scans may need capture-time order. The list order is the only order the tool applies.

1. Add PDFs in the order a reader should see them. Open the first page of each file before trusting the filename.
2. Drag rows to fix order when a scan or attachment landed in the wrong place.
3. Run merge, download the result, and flip through cover, a middle section, and the last attachment.

2. Checks before you merge

Rotate sideways pages in a dedicated viewer first — merging does not auto-deskew. Remove password protection beforehand; encrypted inputs surface a clear error here. Huge scanned PDFs can produce even larger packages; compress first when email caps matter.

• Fix rotation and drop duplicate blank pages early.
• Decrypt with the official owner workflow before merging.
• Compress image-heavy scans if the package will be emailed.

3. What survives — and what may not

Page content streams and basic objects are preserved as far as pdf-lib’s structure copy allows. Bookmarks, some interactive forms, layered optional content, and attachment policies may not behave identically in every reader after a merge. If your process depends on AcroForm fields or a bookmark tree, validate in the same reader your recipient uses.

4. Ordering strategies that reduce rework

Legal and finance packs: cover letter, primary agreement, schedules, ID scans last. Engineering dumps: README or index first, then numbered annexes. When sources arrive as email attachments with random names, rename or annotate the list rows before merging so a second pass is unnecessary.

5. Privacy on shared machines

Merged packs often mix contracts and identity documents. Local merge avoids uploading the whole bundle to a stranger’s converter, but Downloads folders and projector mirrors still leak. Delete temporary copies after you confirm delivery, especially on shared laptops.

6. Related local tools

Need only a few pages from a long file? Split first, then merge the keepers. Image-only sources should become PDF pages via an image-to-PDF tool before joining. Compress afterward if the combined file exceeds a portal limit. Keep a short checklist: order verified, encryption cleared, sample pages opened in the recipient’s reader.

7. Acceptance sample

If text selection fails on a page that was selectable before, you may have used a raster path elsewhere — revisit that source, not this merger.

1. Page count equals the sum of source page counts (unless you intentionally dropped files).
2. First and last pages match the intended cover and closing exhibit.
3. Text selection still works on a born-digital page (proves you did not accidentally flatten everything to images).

8. Reader quirks and batch discipline

Some mobile readers reorder outline panels or ignore attached files after a structure merge. If your recipient must see bookmarks, rebuild the outline in a full PDF editor after merging pages here. Print workflows care about page boxes and rotation flags — a page that looks upright on screen can still print sideways if the rotate metadata was wrong going in. For archival packs, generate a one-page cover sheet listing filenames and checksums, convert that sheet to PDF, and place it first in the merge list so future you can see what went into the bundle. When a portal rejects the upload for size, compress image-heavy sources individually, then remerge — compressing the already merged file is often less effective. When merging dozens of files, build the list in a staging folder with zero-padded numeric prefixes so re-imports stay sorted. Remove duplicates by checksum before merging if email threads produced copies. If one file fails encryption checks, quarantine it and merge the clean set first.

• Rebuild bookmarks in a full editor when outlines matter.
• Add a cover index page for archival bundles.
• Compress scans before merge when portals cap upload size.