Home · Guides · Merge PDF

How to merge PDF files without uploading

Combine multiple PDFs into one file entirely in your browser — no account, no cloud upload, and nothing stored on ITCOH servers.

Why avoid uploading PDFs?

PDFs often contain invoices, contracts, ID scans, medical forms, or school documents. When you drag those into a typical “free PDF merger” website, the file usually travels to a remote server, sits in temporary storage, and may be logged for “abuse prevention.” Even reputable services create a trust and retention risk you do not need for a simple merge.

A private browser tool keeps the bytes on your device. JavaScript reads the files you select, builds a new PDF in memory, and triggers a download. Your originals never leave the machine unless you later email or upload the result yourself.

Merge PDFs with the ITCOH PDF Toolkit

1. Open the PDF Toolkit — Merge, Split & Compress.
2. Use the Merge tab and drop (or choose) two or more PDF files.
3. Reorder the list so pages appear in the sequence you want.
4. Click merge and download the combined PDF.

The same toolkit can split a large PDF into parts and rewrite/compress with object streams — also client-side. Pair it with the Image ↔ PDF Converter if you need to turn scans into PDF pages first.

Open PDF Toolkit Compare with upload sites

Tips for clean merges

• Check page sizes. Mixed A4 and Letter pages will still merge; print settings later may need “fit to page.”
• Password-protected PDFs. Encrypted files may fail to load until you unlock them in another viewer and re-save.
• Huge scans. 100+ page image-heavy PDFs can strain mobile browsers. Prefer a desktop browser with free RAM.
• After merging. If you will email the file, consider whether any page still contains sensitive IDs — merge does not redact content.

Related privacy steps

Merging keeps structure; it does not strip photo metadata inside embedded images. If your PDF was built from photos, strip EXIF from the images first with the EXIF / Metadata Remover, then convert with the image tools, then merge.

A realistic workflow example

Suppose you have three files: a cover letter PDF, a scanned ID page exported from your phone, and a signed contract. Instead of emailing each attachment separately or trusting a random merger site, open the PDF Toolkit, drop the three files, place the cover letter first, then the contract, then the ID scan last (or omit the ID if the recipient does not need it). Download one file and attach it once.

If the ID scan is a JPEG rather than a PDF, convert it first with the Image ↔ PDF Converter, optionally strip location tags from the photo with the EXIF Remover, then merge. That pipeline stays on your device end to end.

What “client-side” actually means

When a page says processing is client-side, the browser downloads JavaScript libraries (here, pdf-lib and related helpers) and runs them on your CPU. The PDF bytes you select are read through the File API into memory (ArrayBuffers). The merged output is turned into a Blob and saved via a download link. Network traffic after the page load is not required for the merge itself.

You should still use HTTPS (ITCOH does), keep your browser updated, and avoid installing untrusted extensions that can read page content. Privacy-first tools reduce server exposure; they do not replace basic device hygiene.

Limitations to expect

• Forms with complex JavaScript actions or XFA may not round-trip perfectly.
• Digitally signed PDFs can invalidate signatures when pages are copied into a new document — expected for any remux/merge.
• Browser memory on low-end phones may struggle with hundreds of high-resolution scan pages.

For those edge cases, a local desktop app on an offline machine remains appropriate. For everyday merges of a handful of office PDFs, the browser toolkit is usually enough — and safer than a casual upload.

FAQ