Home / Images & PDF

Merge PDF Files

100% client-side processing: your files never leave your browser.

or drop PDFs here. They stay on your device.

    Add two or more PDFs, then put them in order.

    A PDF merger combines every page from several documents into one new file. Add files in batches, arrange them in the required order, name the output, and download it without sending the originals to a server. Page content, text, and images are copied, but internal links and document-level features such as outlines, metadata, forms, and signatures need separate review.

    How to Use the Merge PDF Tool

    Arrange complete documents before creating the new combined file.

    1. Select Add PDFs, or drag and drop multiple PDF files onto the drop area. You can use Add PDFs again to add more files in several batches.
    2. Check each file name, page count, and size in the file list.
    3. Use Move up and Move down on each file until the list matches the intended document order.
    4. Use Remove for any file that should not be included.
    5. Set the File name (defaults to merged- plus the current Unix timestamp in milliseconds), then select Merge PDFs to copy every page in list order and download it.
    6. Review the status for the total page count and output size, then open the downloaded file to verify transitions between documents.

    How PDF Page Merging Works

    The tool uses the open-source pdf-lib library in the browser. It opens each source, copies all pages into a new PDF document, and appends them in the sequence shown in the list. If the list contains a two-page cover, a twelve-page report, and a one-page appendix, the output has fifteen pages in that order.

    Copying pages retains the visible page content, text, and images. External web links usually keep working; links to other pages in the original document may not. It does not rasterize the document into screenshots. Searchable text generally remains searchable because the existing page content is transferred rather than photographed.

    The output is nevertheless a new document. PDF contains features at both page and document level, and moving pages does not mean every document-level structure can be reconciled automatically. Plan to inspect bookmarks, forms, metadata, and signatures instead of treating a successful page count as complete validation.

    No compression is applied. The output size may resemble the combined inputs, but object reuse and PDF structure can affect the exact number. Use a dedicated optimization step if byte reduction is required.

    Choosing and Verifying the Correct Page Order

    The list order is the merge order. Give filenames meaningful numeric prefixes before selection when a package has many parts, such as 01-cover.pdf, 02-report.pdf, and 03-appendix.pdf. The tool still relies on the displayed list, so verify it rather than assuming operating-system selection order is authoritative.

    Package part Verification point
    Cover First page and correct title
    Main document Starts after cover and has complete page count
    Attachments Follow the referenced sequence
    Terms or appendix Appear at the expected final location

    After download, inspect the first and last page of each source boundary. Page numbers printed inside documents do not change automatically, so a report whose footer begins at page 1 will still say page 1 even if it becomes page 3 of the merged file. Adding or rewriting visible page numbers requires a separate editing workflow.

    Page content is kept as part of copied pages, but the outline or bookmark tree is not carried into the new document. A long merged handbook may therefore need bookmarks rebuilt with a PDF editor if navigation is important. Document-level metadata such as the original title and author is also not preserved.

    Interactive form fields may not survive the copy reliably, especially when separate files reuse field names or depend on document-level scripts. Flatten a form through an appropriate trusted workflow when the final package only needs the visible values, or test every interactive field in the merged output when it must remain fillable.

    Links on a page come along with it, but their destinations deserve inspection. External web links should continue to target their URLs. Internal links that point elsewhere in the original document can be sensitive to page copying and changed structure. Test table-of-contents links and cross-references after merging.

    Why Digital Signatures Become Invalid

    A digital signature covers specific bytes and document state. Merging copies pages into a newly constructed PDF, so the original signed byte sequence is no longer the downloaded document. A visible signature appearance may remain on a copied page, but it must not be treated as a valid signature on the merged file.

    If legal or operational trust depends on signatures, preserve the individually signed originals and follow the organization’s approved signing process. A typical workflow is to assemble the final document first and sign that final artifact afterward. Whether that is acceptable depends on the signature policy and jurisdiction; the merger itself does not validate or renew signatures.

    Encrypted PDFs, Sensitive Documents, and Memory Limits

    Password-protected or encrypted PDFs cannot be merged. The tool shows an error naming the affected file rather than skipping it silently. Remove protection only when you are authorized to do so, using an appropriate application, then retry with the permitted unencrypted copy.

    All merging occurs locally in the browser. Files are never uploaded, and the page continues to work offline after it has loaded. Local processing reduces exposure to an additional document service, but it does not replace careful handling of downloaded files, browser storage, backups, or shared devices.

    The browser must hold input data, parsed PDF structures, copied objects, and the new output in device memory. Peak memory can be much larger than the final file size, particularly when documents contain many high-resolution images. There is no universal maximum because browsers and devices differ.

    For a very large package, close memory-heavy tabs and use a desktop device. If the page becomes unresponsive, combine smaller groups first only when that workflow does not create unacceptable repeated processing or navigation loss. A command-line or desktop PDF system may be more appropriate for hundreds of large documents.

    Because no compression occurs, merging is not a remedy for oversized scans. Optimize scan resolution and compression separately, while retaining any archival originals required by policy.

    Frequently Asked Questions

    Are my PDF files uploaded when I merge them?

    No. pdf-lib reads and combines the documents locally in the browser. Once the page has loaded, the tool also works offline.

    Can I change the order before merging?

    Yes. Use Move up and Move down for each entry. Every page is copied according to the final file-list order.

    Will PDF bookmarks be preserved?

    No. The document outline or bookmarks are not carried into the new PDF. Rebuild them separately when the combined document needs structured navigation.

    Can I merge a password-protected PDF?

    No. Encrypted PDFs are unsupported, and the tool reports an error naming the file. Use an authorized unencrypted copy instead.

    Does merging compress the PDFs?

    No. Pages are copied without a compression pass. The merged size can reflect the source data, and large image-heavy documents remain large.