Merge PDF Files: Order, Bookmarks & Quality

Build the packet around the reader's job

A useful merged PDF has a deliberate order, an understandable filename, and every page the recipient needs. A tax packet might put a cover sheet before invoices and receipts. A research packet might group scanned chapters by topic. Neither job is finished merely because several files now open in one window. Check navigation, legibility and completeness before sharing the result.

ExactPDF's Merge PDF combines PDFs in your browser. A merge requires two to twenty PDFs, with a 150MB limit per file and a 200MB combined input limit. These are validation ceilings rather than a promise that every permitted collection will fit your device's memory. Source files, previews and the output all need resources. For a large packet, start with a small representative group and keep the original documents separately.

Prepare the inputs before selecting them

Make a short inventory: filename, expected pages, desired position and whether any pages should be excluded. Use names that identify the document without exposing unnecessary personal information. The names also matter if you enable the option that creates a bookmark for each input file. A name such as April invoices is more useful in a reader's navigation panel than final-final-v3.

Create a cover sheet in your preferred document application and export it as a PDF first. The standard merge page expects PDFs. A cover image or photograph is not a PDF simply because it belongs in the packet. Convert it separately with Images to PDF, then add the resulting PDF alongside the other documents.

If a file needs a password, unlock a copy using its known password before adding it. Merge rejects encrypted inputs rather than asking for a password inside this workflow. You should also open each source in a reader to check that it has pages and displays correctly. A file extension alone does not establish that a document is readable.

Merge, order and inspect

Open Merge PDF and select the documents for your packet. Selecting local files lets the browser read them; this merge operation does not upload their contents for conversion.

Wait for analysis and previews to finish. The tool checks that every page can be previewed before accepting a selection.

Arrange the input files in the intended reading order. Put a cover PDF first, followed by the supporting material.

Open the page preview for any input that contains irrelevant pages. Review its selected pages before proceeding.

Check the bookmark option and output quality. For the first attempt, keep Original quality so you can assess the assembled document before choosing image compression.

Set a custom filename if needed, then press Merge. Download the completed PDF and reopen the downloaded copy in your normal reader.

Count the pages you intended to include, rather than relying only on the original file totals. If you excluded a blank page or an outdated attachment, the expected output total changes. Check the boundaries between inputs: the last invoice before receipts, the cover before the report, and the final page of each chapter. These are useful places to catch an ordering mistake.

What the bookmark option actually does

The option is labelled Add a bookmark for each input file. It creates a top-level outline item for an included document, pointing to that document's first selected output page. This can make a long packet easier to navigate when your PDF reader displays outlines. The option is enabled by default, so review the resulting names before sending a client-facing file.

This is not a promise to preserve an existing nested bookmark tree. If a source book has chapters, subchapters and cross-references, do not assume those structures survive the merge. The merger builds its own file-level outline. When detailed outlines are essential, use an editor with explicit outline editing and verify its saved result. Keep the original bookmarked publication available as the reference.

Invoice and tax packets

For an invoice packet, order documents by a rule the recipient can follow, such as reporting period and supplier. Put an index on the cover if there are several categories. Use the merge preview to exclude duplicate copies, but retain a separate record of what you removed. The merger does not reconcile invoices, identify tax categories or determine whether an expense belongs in a return.

Merging a scanned receipt does not recognize its words. If the recipient needs copyable text, treat recognition as a separate job. The free OCR tool extracts English text into text-based downloads; it does not add a searchable layer to your merged packet. Share the PDF and any checked text extract as separate artifacts when that arrangement meets the recipient's needs.

Before applying compression, ask whether the recipient needs selectable text or interactive fields. Original-quality merging copies selected pages without rendering the entire packet into new page images. Compression is a different transformation with different tradeoffs. Keep the merged original so you can produce another delivery copy without repeatedly degrading the same file.

Scanned chapters and reading copies

Put scanned chapters in reading order and inspect their orientation before merging. A combined PDF remains a fixed-page document: merging does not reflow its text for an e-reader or make small print comfortable on a narrow screen. Test a representative page at the size you expect to read. If it requires constant zooming, keeping chapters separate may be more useful than creating one large book.

Bookmarks can provide a chapter-level entry point when each chapter is a separate input. They cannot repair missing pages, inconsistent scans or incorrect printed page numbers. Use the actual preview positions when selecting pages; the printed number on a chapter opening may differ from its position inside the file. Check an opening page and a dense interior page before assembling the whole collection.

Quality and file-size decisions

Original, High, Medium and Low are output-quality choices in this merger. The non-original settings can recompress supported embedded images. That may reduce bytes, but the effect depends on the input's image representation. Do not infer a fixed percentage reduction from a setting name. Original is the appropriate starting point when you want to separate assembly decisions from compression decisions.

If the assembled file exceeds a recipient's upload ceiling, compare two options: a compressed delivery copy, or smaller packets made with Split PDF. Splitting may retain useful detail when an image-heavy packet cannot meet the ceiling legibly. Confirm that the recipient accepts multiple files before splitting; a smaller file is not helpful if the submission requires a single document.

The merge path adds no watermark step. That does not mean it removes marks already present in a source. A scanned logo, evaluation watermark or stamp is part of the supplied page content and should be expected to remain. Check the output rather than interpreting watermark-free conversion as permission or a mechanism to remove existing marks.

Recover from an unsuccessful selection or merge

If selection reports that no files from this selection were added, inspect the named input. The tool treats a selection as a group and rejects that group when a member is unreadable or encrypted. Retry with readable, unlocked copies. Adding the same questionable group repeatedly will not establish that every page was accepted.

If merging reports that no merged PDF was created, preserve the inputs and retry a smaller set to locate the problematic file. Do not distribute a partial-looking result as if it were complete. If all pages were deselected, select at least one page before merging. Browser memory pressure is another reason to assemble smaller groups rather than continually retrying a very large packet.

Use a dedicated document editor when you must preserve signatures, form behavior, tagged reading order or complex navigation with a contractual level of fidelity. This guide makes no certification claim for those properties. For ordinary packets, a careful check of the downloaded pages and file-level bookmarks is the practical final step.