How to merge PDF files without losing quality or privacy
Merging sounds like the simplest PDF operation, and in one sense it is: put file A before file B, press the button, get one PDF. But the details decide whether the result is a clean professional document or a mess of mixed page sizes, duplicated form fields and misplaced covers.
This guide explains what merging actually does to your files, how to get the order right, what to expect from page sizes and interactive elements, and why the Paperly Merge tool — which runs entirely in your browser — keeps your documents private by never uploading them.
What merging does to your files
A PDF page is a self-contained description of its content. Merging takes the page objects from each input document and copies them into a new document, in the order you chose. Because pages are copied rather than re-rendered, the content itself is untouched: text remains selectable and searchable, vector graphics stay sharp, and embedded fonts continue to render as the author intended.
The exception to "nothing changes" is interactive structure that lives at the document level rather than on individual pages. Bookmarks, named destinations, and interactive form fields do not always survive a merge cleanly. Most tools, Paperly included, preserve the pages and their visual content; document-level navigation aids may be lost in the process.
Order matters more than you think
The output PDF follows the exact order of the input files at the moment you press Process. A common mistake is adding files in one order and assuming you can fix it later — with most tools you cannot reorder inside the result, you have to re-run the merge.
- Add all the files you want to combine.
- Check the file list order — it is the output order.
- Move any file that is out of place before processing.
- Process, then spot-check the first and last pages of the result.
Page sizes and orientations
Merging does not normalize page sizes. If you combine a Letter-size document with an A4 one, the output keeps both sizes — each page stays exactly as it was. When printed or viewed full-screen, the smaller pages will show with white space around them.
The same applies to orientation. A document with rotated pages keeps its per-page rotation after the merge. If your combined document must have uniform dimensions, run the Change Page Size tool on the result afterwards.
Forms, metadata and duplicate names
If two merged documents each contain a form field named "Name", the combined PDF can end up with conflicting field definitions. Many PDF readers cope, but some show odd behavior in the merged fields. Flattening the forms before merging avoids the issue entirely.
Metadata is simpler: the merged output carries its own metadata set by the tool. Author, creation date and other original document metadata are not merged together, which is usually what you want for a clean deliverable.
Merging vs binding
A plain merge concatenates pages with no added structure. A bind (the Paperly Bind PDFs tool) goes one step further: it adds a generated cover page that lists every included file and its page range, turning a pile of documents into something that reads like a report or a package.
| Approach | Output | Best for |
|---|---|---|
| Merge | One document, pages concatenated in order | Combining chapters, attachments, or multiple versions |
| Bind | Cover page + contents list + all pages | Deliverables, submissions, document packages |
Common merge mistakes and how to avoid them
Four mistakes account for almost every bad merge result:
- Wrong order — always verify the file list before processing, because the output cannot be reordered afterwards.
- Mixed page sizes — normalize with Change Page Size afterwards if the deliverable must be uniform.
- Forms colliding — flatten forms before merging so field names do not clash in the output.
- Huge output — merging never compresses, so run the merged file through Compress PDF to slim it down.
Each of these is easy to catch if you check the file list before processing and spot-check the output after. The few seconds of verification save the annoyance of discovering a wrong order after you have already shared the file.
Merging different file types first
Merge works on PDFs. If your inputs are images, Word documents or spreadsheets, convert them to PDF first with the JPG to PDF, Word to PDF or Excel to PDF tools, then merge the results. This two-step workflow keeps every input format consistent before combination.
A common pattern is a report assembled from several sources: a cover made from an image, a body exported from Word, and a data appendix from Excel. Converting each to PDF and merging in order produces a single consistent deliverable without any re-typing.
Merging vs compressing: two different goals
Merging combines documents; compressing shrinks them. They solve different problems and are often best used together. If a merge produces a file that is too large to email comfortably, run the result through Compress PDF — but understand that compression works best on image-heavy content, and text-heavy PDFs shrink only modestly.
Privacy and limits
The Paperly merge tool processes everything in your browser. Files are read into memory on your device, combined locally, and downloaded from there — nothing is transmitted to a server, so there is nothing for a third party to intercept or retain.
The practical limit is your browser memory. Very large batches can slow the browser; splitting a huge job into smaller merges is the reliable workaround.
If you merge files that contain sensitive information, the privacy model matters as much as the result: because nothing leaves your device, a merge can be used on contracts, medical forms and financial statements without creating a server-side copy that could be breached later. The downloaded file is the only artifact that exists, and you control where it goes from there.