Merge PDF Files Without Uploading Them
Combine any number of documents into one file. Page order is set before the merge runs and nothing is transmitted.
Document tooling from OnlinePCApps since 2013
Three Cases That Require a Single PDF
Each is a routine document task rather than a fault to be repaired.
Submission as a Single File
Applications, tenders, invoices and court filings frequently require one document. Separate PDFs for the form, the evidence and the legal annexes have to be combined before submission.
Scans Produced in Batches
Sheet-fed scanners and mobile capture apps write one PDF per pass. A twelve-page contract scanned in three passes arrives as three documents.
Documents Under Confidentiality
Contracts, medical records and financial statements cannot be sent to a third-party server for processing, whatever the retention policy states.
Combine PDF Files in 3 Steps
Add the Documents
Select the PDF files to combine. Each is read from local storage and parsed in the browser.
Set the Order
Drag documents into sequence. Individual pages can be reordered, rotated or removed before the merge runs.
Merge and Save
The combined document is assembled on the device and written straight to disk.
PDF Merging on Any Operating System
The tool is a web page, so platform support follows browser support rather than an installer.
On Mobile
Small documents merge without difficulty. Total size rather than page count sets the limit.
On a Tablet
Tablet browsers on Android and iOS run the same code. No application store step is involved.
On a Managed Device
Managed devices that prohibit installation still provide a browser, which is the only requirement.
On a Shared Machine
No installation occurs and no file is written outside the chosen output location.
The OnlinePCApps PDF Merger is a free browser-resident tool that combines two or more PDF documents into a single file. Documents are read from local storage, assembled on the device and written back to disk. Page order is set before the operation runs, bookmarks and form fields are preserved, and no file is transmitted at any stage. Folder-level batches and documents beyond available memory are handled by the desktop build.
Local Processing vs Upload-Based Mergers
Every major PDF merger transfers documents to a server, holds them in a processing queue and deletes them on a timer. The constraints below follow from that model.
| Property | This page This tool Runs in the browser | A typical upload-based merger Transfers documents for processing |
|---|---|---|
| Where processing occurs | On the device | On the provider's servers |
| Free tier size ceiling | Device memory | 10 MB to 15 MB per file |
| Free tier task cap | None | 2 to 3 tasks per day or hour |
| Watermark past the limit | Never applied | Applied by some providers |
| Point of failure | None, work is local | At download, once quota is spent |
| Retention after processing | Nothing is held | Deleted after one to two hours |
| Suitability for confidential files | Unrestricted | Constrained by policy |
| Speed by location | Independent of distance | Depends on distance to the servers |
The comparison describes the model the category shares rather than any single named service.
No PDF Document Reaches Our Servers
Retention policies are the standard reassurance in this category. A one-hour deletion window is typical, and it is only as strong as the operator behind it.
No retention policy applies here because no document is received. Nothing on this site accepts a file, and nothing runs on our side for this tool. The network panel in the browser developer tools records no transfer while a merge runs.
→ external requests ....... 0
→ document upload ....... 0 requests
What a Merge Does to Each Element
A merge rewrites document structure while leaving page content untouched. The table sets out what is carried, what is remapped and what cannot survive the operation.
| Part | Header | What it holds |
|---|---|---|
| Page content | carried unchanged | Content streams, fonts and XObjects are copied byte for byte. No re-encoding occurs, so nothing is degraded. |
| Page order | as arranged | Documents follow the sequence set before the merge. Pages within a document can be reordered independently. |
| Page size | retained per page | Mixed A4 and Letter documents keep their original dimensions. Nothing is scaled to a common size. |
| Rotation | retained per page | A page rotated in the source stays rotated in the output, and rotation can be changed before merging. |
| Bookmarks | merged and nested | Each document's outline is preserved and placed under its own top-level entry in the combined file. |
| Internal links | remapped | Cross-references to pages inside the same document are rewritten to the new page numbers. |
| External links | carried unchanged | Link annotations pointing outside the document are copied as they were. |
| Form fields | carried, names checked | AcroForm fields are preserved. Where two documents use the same field name, the second is renamed so values stay independent. |
| Digital signatures | invalidated | A signature certifies one specific byte sequence. Merging produces a new document, so any existing signature no longer validates. |
| Tagged structure | carried where present | PDF/UA tagged structure is preserved when the source documents carry it. A merge cannot create tags that were never there. |
| Document metadata | reset | Title, author and keywords are not inherited from any one source. The output carries no metadata unless it is set afterwards. |
| Attachments | carried | Files embedded in a source document remain embedded in the output. PDF/A conformance, by contrast, is a property of each source and cannot be assumed to survive a mixed merge. |
Specifications this tool follows
PDF is an open standard maintained by ISO rather than a proprietary format, currently at PDF 2.0 with PDF 1.7 still the version most documents declare. The sources below cover the structures a merge has to rebuild correctly: the page tree, the outline hierarchy and the interactive form dictionary.
Signature behaviour is set out in the PDF specification, which is why a signature cannot survive the operation.
Cases This Tool Will Not Handle
Four conditions block a merge or change the result. Each is stated with the reason and the correct sequence to follow.
Encrypted Documents
Signed Documents
Duplicate Form Fields
Very Large Documents
Confirm Order Before Merging
Run Preview against page thumbnails, which shows the assembled sequence without producing a file. Checking there costs nothing and avoids a second pass.
Compress After, Not Before
Run Compress PDF against the output, which reduces size once, on the finished document. Compressing each source first re-encodes images twice.
Where a PDF Merge Exceeds the Browser
Two constraints apply to browser processing: available memory and the absence of filesystem access.
What the Desktop Build Covers
Each source document is held in memory while the combined file is assembled, so total size is the binding constraint rather than the number of documents. Several hundred megabytes is routine on a laptop and considerably less on a handset.
The desktop build streams from disk and writes incrementally, which removes the memory constraint entirely.
No connection is opened after installation, which suits isolated networks and controlled environments.
Documents are streamed from disk rather than held in memory, so total size stops being a constraint.
Point it at a directory and merge every document in it under a naming rule.
Directories of documents processed under one rule, past the memory ceiling a browser applies.
Save an order and a set of rules, then apply the same operation to a new set of files.
No connection is required after installation, which suits restricted networks.
PDF Merge Questions
Related Document Tools
Each operates under the same constraint: processing on the device.
Who Maintains This PDF Tool
Combine Documents Without Transferring Them
No installation, no registration and no server transfer. Page order is set before the merge runs.