PDF Merge
Browser-based PDF merger: combine multiple PDFs in your browser with no file uploads, no registration, and no watermarks. Supports page range selection.
Browser-based PDF merger: combine multiple PDFs in your browser with no file uploads, no registration, and no watermarks. Supports page range selection.
Click the file area or drag and drop two or more PDF files onto it. Files are added in the order you select them — drag to reorder them before merging.
For each file, optionally enter a page range (e.g. '1-3, 5, 8-10') to include only specific pages. Leave the range blank to include all pages from that file.
Review the file order in the list. Use the up/down arrows to change sequence. The final merged PDF will follow this order exactly.
Click Merge PDFs. Your browser assembles the combined file locally and immediately triggers a download. No data is sent anywhere.
Every step of the merge process runs inside your browser tab using the pdf-lib JavaScript library. Your PDF files are read into local browser memory, processed, and downloaded — they never touch a server, a CDN, or a third-party API. Works even without internet after the page has loaded.
Include all pages from each file, or specify individual pages and ranges (e.g., '1-5, 7, 9-12'). This lets you extract specific chapters, skip blank pages, or combine selected sections from several source documents into a single output file.
After adding files, reorder them by dragging. The order you set in the list is the order pages appear in the merged PDF — useful when assembling cover sheets, appendices, or multi-chapter documents that must follow a specific sequence.
The merger copies fonts, embedded images, vector graphics, and page geometry directly from the source PDFs rather than re-rendering them. This preserves the visual quality of scanned documents, branded letterheads, and complex layouts without resolution loss.
Once the page and the pdf-lib library have loaded, you can disconnect from the internet and continue merging. This is useful for sensitive document workflows in air-gapped environments or when working on a plane or train.
Most free online PDF mergers upload your files to a server for processing, which creates privacy and data security risks for sensitive documents like tax returns, legal contracts, medical records, and business reports. This tool processes everything locally — your files are loaded into your browser's memory, merged, and saved back to your disk without a single byte leaving your device.
There is no account to create, no email to provide, and no premium subscription required to unlock features. The merged PDF does not include any watermarks, branding, or metadata injected by this service. Daily usage is unlimited. The full feature set — including page range selection and multi-file reordering — is available at no cost.
The tool correctly handles PDFs that mix portrait and landscape pages, multi-column text, embedded fonts, high-resolution images, and scanned pages. Unlike simple merge tools that re-render pages as images, this tool copies page content at the PDF object level, preserving text selectability and search-indexability in the output.
The merge engine uses pdf-lib, a well-maintained open-source JavaScript library with over 6,000 GitHub stars and extensive documentation. The processing logic is fully auditable — there are no black-box APIs or proprietary algorithms involved. If you are a developer, you can review exactly what the library does to your files.
The majority of free online PDF tools work by accepting a file upload, processing the file on a remote server, and returning a download link. This architecture has real privacy costs. When you upload a document to a third-party service, you are trusting that service with the contents of that file. Most terms of service for free tools allow the provider to analyse, retain, or re-use uploaded content for service improvement. For personal documents — tax returns, passports, medical records, legal agreements — this is a significant risk.
Browser-based processing eliminates this risk entirely. The PDF files you load into this tool are read by the browser File API from your local file system into browser memory. They are processed by JavaScript running in your browser tab. The result is written back to your file system via a browser-triggered download. At no point does any content traverse a network connection.
A PDF file is not a single flat document — it is a structured collection of objects: page trees, content streams, resource dictionaries, font descriptors, image XObjects, and cross-reference tables that tie them together. Merging two PDFs requires reading both file structures, copying the page objects from each source document, updating all cross-references so that fonts and images referenced on those pages resolve correctly in the new combined document, and writing a valid new PDF structure.
A naive merge that simply concatenates the raw bytes of two PDF files will always produce a broken output because the cross-reference tables from the two files will conflict. A correct merge must parse both files at the PDF object level and construct a new unified object graph. This is what pdf-lib does, and why it produces reliable output even when merging complex documents with embedded fonts and images.
Fonts in PDF files can be either embedded (the font data is stored inside the file) or referenced (the file lists a font name and relies on the viewer to supply it). When merging, embedded fonts are copied into the output file, ensuring they render identically regardless of which fonts are installed on the viewer system. Referenced fonts are also preserved as references in the output. The merger does not subset, re-embed, or convert fonts — it copies them as-is, which means the output file font fidelity matches the source files fidelity.
When you specify a page range like "1-3, 5, 8-10" for a source file, the tool parses that range string, resolves it against the actual page count of the file, and copies only the specified page objects. Pages outside the range are not included in the output. This is implemented at the PDF object level — only the selected page trees and their referenced resources are copied, which can also reduce the output file size when selecting a small subset of a large source document.
Because all processing happens in memory, the practical file size limit depends on your device available RAM. As a rough guideline: merging files that total up to 100 MB works comfortably on most devices with 4 GB of RAM or more. Files totalling 200-500 MB may work but may cause the browser tab to slow down. Files above 500 MB total may trigger the browser out-of-memory protection on devices with limited RAM. If you need to merge very large files, split the task into smaller batches and merge the intermediate outputs.
PDF encryption exists in two forms: user password (required to open the file) and owner password (restricts printing, copying, or editing). This tool can merge PDFs that have owner restrictions but no user password — meaning files that open without entering a password but have editing restrictions. PDFs that require a password to open cannot be merged without first removing the password in a separate step. This is a deliberate limitation: merging encrypted files without the password would require breaking the encryption, which this tool does not attempt.
No. The entire PDF merging process runs in your browser tab using local resources. Your files are read from your local disk into browser memory, processed by JavaScript, and downloaded back to your disk. No content is transmitted over any network connection. You can verify this using your browser developer tools — no outbound requests are made after the page loads.
You can merge PDFs that have owner restrictions but open without a password. Fully encrypted PDFs that require a password to open cannot be merged by this tool without first removing the password using a PDF editing application. Attempting to load an encrypted PDF will show an error message explaining this limitation.
The tool allows merging between 2 and 20 files at a time. This limit exists to prevent excessive browser memory usage on devices with limited RAM. If you need to merge more than 20 files, merge them in batches and then merge the resulting files together.
Yes. The merger copies page content at the PDF object level, not by re-rendering pages as images. This means embedded fonts, vector graphics, high-resolution images, and most annotation types are preserved with full fidelity. Form fields are supported in most cases but complex JavaScript-based forms may lose interactivity.
No. The tool does not inject any watermarks, branding text, or additional metadata into the output file. The Producer metadata field in the PDF is set to pdf-lib (the name of the open-source processing library), which is standard behaviour for the library.
No installation is required. The tool runs entirely in your web browser — Chrome, Firefox, Safari, and Edge are all supported. The pdf-lib library and all processing code are loaded as part of the web page.
Because processing happens entirely in browser memory, the practical limit depends on your device available RAM. Files totalling up to 100 MB work reliably on most devices. Merging very large files (200+ MB total) may slow the browser tab on devices with limited memory. Split large tasks into smaller batches if needed.
Yes, once the page has fully loaded in your browser. If your browser has cached the page and the pdf-lib library, you can disconnect from the internet and continue using the tool. This is useful for sensitive document workflows where internet connectivity is restricted.