Combining multiple PDFs into a single file is one of the most common document tasks in professional environments. It also does not require a server, an account, or a subscription — it is an operation that can run entirely in the browser using a library like pdf-lib. Many platforms that charge for PDF merge, or require an account, are charging for convenience rather than capability.
How PDF merge works
PDF merge concatenates the page objects from multiple PDF files into a single output file. The operation is straightforward when the source files are standard PDFs: the merger reads the page tree from each file, appends them in order, and writes a single document with a combined page tree.
Complications arise with encrypted PDFs (which cannot be merged without removing encryption first), PDFs with conflicting font names (where the same font name maps to different font data in different files), and PDFs with interactive form fields (which can produce unpredictable results when merged because form field names must be unique within a document).
For standard non-encrypted PDFs without forms, merge is a clean, lossless operation. The resulting file is exactly as large as the sum of its parts, minus any shared resources that can be deduplicated. Page content, images, and fonts are preserved exactly.
Free options that work without an account
Filum performs PDF merge entirely in your browser using pdf-lib. No file is uploaded to a server at any point — the merge happens on your device and the output downloads directly from your browser's memory. No account is required, and there is no task limit: your device does the work, so there is nothing for anyone to meter.
PDF24 offers unlimited free PDF merges with no account. The merge is server-side. PDF24 has been a reliable option for high-volume merge tasks where the no-limit policy matters more than specific quality considerations.
Smallpdf allows PDF merge within its two-tasks-per-hour free limit. If merge is the only task you need, two merges per hour is adequate. If you need to merge and then compress or convert in the same session, you will hit the limit after the first two operations.
Common merge problems and how to fix them
If a merged PDF has blank pages, one of the source files likely had blank pages that were part of the document structure. Open each source file and identify any blank pages before merging, then remove them using a PDF editor or by splitting the file to remove the blank pages before re-merging.
If text in the merged output looks different from the source — different weights, slightly different spacing — the merge process encountered conflicting font data. This is most common when merging files that came from different source applications or were converted through different paths. The merge operation itself did not change the fonts; conflicting font data in the source files resolved ambiguously.
Merged PDFs with form fields often have non-functional fields because field names collide across merged documents. If the forms need to remain functional, use a tool that handles form field renaming during merge, or flatten the form fields before merging so they become regular text.
Getting the page order right
Most merge tools allow you to reorder files before merging. The output page order matches the file order you specify. If you need pages from different files interleaved — alternating pages from file A and file B, for example — this requires either a tool that supports interleaved merge modes, or splitting each source into single pages, reordering them manually, and merging the resulting singles in order.
For a two-sided scan workflow — where front sides and back sides were scanned in separate passes — the interleaved merge operation produces the correct bound-document order. Some tools label this operation specifically; others require the manual split-and-reorder approach.
If the final merged file has pages in the wrong order and the source files were correct, the most likely cause is that the merge tool processed the files in alphabetical order rather than the order you specified. Rename the source files with a numeric prefix — 01_intro.pdf, 02_body.pdf, 03_appendix.pdf — before uploading if the tool does not let you drag files into position.
Merging PDFs on a phone or tablet
Most browser-based PDF merge tools work on mobile, but the experience varies. The main constraint on phones is memory: merging large PDFs in a mobile browser uses the same JavaScript memory available to any browser tab, which is typically 512 MB to 1 GB depending on device and OS. For files under 10 MB combined, this is rarely a problem. For larger merges on a phone, prefer a tool that processes the files server-side rather than in the browser tab.
On iOS, the Files app can combine PDFs without any third-party tool. Open a folder containing the PDFs you want to merge, select all of them, tap Share, and choose Create PDF. The combined file is saved to the current folder. This works for a simple sequential merge and requires no upload, no account, and no network connection.
On Android, there is no equivalent built-in option. A browser-based tool is the most straightforward path. If the files are on Google Drive, Google Drive's PDF viewer has limited merge functionality via third-party integrations, but a dedicated browser tool is more reliable for clean, unattended merges.
What happens to your files when you merge online
Most PDF merge platforms process files server-side, which means your documents are uploaded, processed, and stored on a remote server. The critical question for any sensitive document is: how long does the platform keep the file after you download it, and what triggers deletion?
Filum's merge happens entirely in your browser using pdf-lib. The files never leave your device. No network request is made during the merge — only your local JavaScript processes the page trees and writes the combined output. Filum ships an automated browser test that captures network traffic during a real merge and fails if any request carries file data, so this claim is continuously verified rather than promised.
There is no server-side path to reason about: Filum has no upload endpoint for merge at all. The privacy questions most converters force you to ask — how long is my file retained, who can access it, what triggers deletion — have no object to apply to. A file that is never transmitted cannot be retained, breached, or subpoenaed from a server.
This matters for documents that contain confidential information. A contract, a financial report, a medical record — these are exactly the kind of documents that appear in PDF merge workflows. Understanding where they go is not a secondary concern, and with a fully client-side merge the answer is structural: they go nowhere. Files never leaving your device is the strongest privacy guarantee a converter can make.
File size, performance, and what to expect at the limits
PDF merge is computationally straightforward for standard files, but the performance characteristics change with file size and page count.
In the browser, pdf-lib performs the merge in the main thread. Filum's own automated test merges a five-page batch in about one to two seconds, and a few hundred pages stays comfortably interactive. With very large batches, particularly on slower devices, you may notice a brief pause while the JavaScript engine works through the page trees. This is normal and is not a sign that anything has failed.
Because the merge runs on your device, there is no upload time to wait for at any size — the step that dominates total time on server-based converters simply does not exist. The practical limit is your device's memory rather than a plan tier: very large batches can exhaust browser memory on low-end hardware, in which case merging in smaller groups and then merging the results works reliably.
There is no file size tier and no page count limit. The operation runs on your hardware, so the only constraint is your device's available memory — the same constraint as opening the same files in any desktop application.
If a merge produces a larger output file than expected, the most common cause is embedded high-resolution images. PDF merge is a lossless concatenation — it does not compress images during the operation. Three 10 MB image-heavy PDFs produce a 30 MB merged output. To reduce the final size, compress the individual source PDFs before merging rather than attempting to compress the merged result afterward. Compressing after the merge works but gives you less control over which images are downsampled.
If a merge fails or stalls, the source is almost always a file that is corrupted, password-protected, or structured in a non-standard way. Test each source file by opening it in a PDF viewer before attempting the merge. A file that cannot be opened cannot be merged.