PDF merging is one of the most common document tasks, and until recently the default workflow was to upload files to a cloud service, wait for server processing, and download the result. Modern browsers now support full PDF manipulation entirely in JavaScript, which means merging can happen locally without ever sending your files over the network. The sections below explain the technical shift that makes local merging possible, why it matters for confidential documents, and how to get reliable results with page ranges and large files.
Why Local Merging Beats Cloud Services for Privacy
Traditional online PDF tools require uploading your files to a server, where the merge happens, and then downloading the result. That workflow has three problems that matter for anyone working with sensitive documents. First, your file leaves your device — the server operator sees it, their cloud storage holds it (often for 24 hours or longer under their retention policy), and any security breach exposes it. For contracts, medical records, tax documents, or anything under an NDA, this is a meaningful confidentiality risk. Second, uploads and downloads take time proportional to file size and internet speed. Third, free-tier cloud services often impose restrictive file-size, file-count, or daily-operation limits. Browser-based tools like this one use the pdf-lib JavaScript library to perform the entire merge locally in your browser's memory. Your files never leave your device; this tool accepts files up to 250 MB each and up to 750 MB in the queue, subject to additional practical memory limits.
Page Ranges, Reordering, and Fine Control
Many real-world merge tasks aren't just "combine these files whole" — you want specific pages from each source document in a specific order. The page range input accepts flexible syntax: a single page (5), an inclusive range (1-3), a comma-separated list (1,3,5), a combination (1-3,5,7-9), or the word "all" for the whole file. Out-of-bounds pages (e.g., specifying page 50 from a 30-page PDF) are silently dropped rather than causing an error, so you can paste a conservative range that covers several possible source-file lengths. Reordering files uses a drag-and-drop handle on desktop browsers and up/down arrow buttons on mobile, and the final merged PDF follows the list order top-to-bottom. A common workflow is to load all source files, use the quick range presets or specify custom page ranges to pull just the relevant pages, rotate any orientation-mismatched documents, reorder or sort the list, and then merge. This produces polished multi-source bundles — pulling the cover page from one template, the body from another, and appendices from several more — without any intermediate files or back-and-forth between tools.
Handling Large Files and Edge Cases
Browser-based PDF merging has practical limits driven by your device's available memory and by the tool's 250 MB per-file and 750 MB queue caps. Each PDF is loaded into memory during the merge, and the output document is also held in memory before the Download click. If you hit memory pressure (the browser tab slows dramatically or crashes), merge in smaller batches — combine the first group into one intermediate PDF, combine the next group into another, then merge the intermediate files together. Encrypted or password-protected PDFs are rejected and must be saved as unencrypted copies before merging. Damaged or corrupt PDFs can similarly fail. Merging copies page content without rasterizing or re-encoding it, so images, embedded fonts, vector graphics, and interactive form fields retain their source quality; document-level metadata is written for the new merged file.