PDF guide

How to merge PDF files safely

To reduce unnecessary exposure when merging PDFs, use a tool whose file handling you can verify, check file order and limits before processing, and review the downloaded result. PDFandDOC's Merge PDF tool runs in your browser, so selected PDF files are not uploaded to PDFandDOC for merging.

What safer merging means here

A careful merge workflow has two separate goals: keep document handling understandable and make the combined result easy to verify. Browser-local processing reduces the need to transfer selected PDF bytes to a remote conversion service, but that alone does not make every PDF, website, browser, device or downstream sharing workflow risk-free. Before you merge, decide which documents belong together, remove unrelated copies, and confirm the intended reading order. After the merge, compare the output page count with the source files and inspect the sections where one document changes to the next. This matters especially for contracts, applications, reports and records where an accidental duplicate page or a misplaced appendix can change meaning. Keep the originals until you have checked the combined file, and apply your own handling requirements to confidential or regulated material rather than assuming that a browser-local tool satisfies every organizational policy.

Current Merge PDF limits

Up to 10 PDF files
Up to 25 MiB per file
Up to 50 MiB total
Up to 200 total pages
Encrypted or password-protected PDFs are not supported by this tool.

Steps

Choose the PDF files you need to combine and avoid adding unrelated sensitive documents.
Confirm how the tool processes files and check its current file-size and page-count limits.
Put the files in the order you want them to appear in the merged PDF.
Run the merge, download the result and review the page order before sharing it.
Use the selected-file cards to remove an accidental file and change the order before processing. If order is important, confirm it from the filenames, page counts and available previews rather than relying on the order in which files happened to be chosen.
Compare the expected total page count with the result metadata. A simple count check can catch a missing input, an unintended duplicate file or a selection mistake before the merged document is distributed.
Open the downloaded PDF in a trusted viewer and check the first and last page of each source-document boundary. For a long merge, spot-check tables, signatures, attachments rendered as pages and any section where page orientation changes.
Keep the original PDFs until the merged copy has been reviewed and accepted for its intended use. Merging changes the document package you distribute even when the visible page contents are preserved, so the combined file should be treated as a new output that needs its own review.

Example

Example: suppose you have a two-page project summary, a six-page technical report and a one-page approval sheet. Put the summary first, the report second and the approval sheet last. Before processing, confirm that the selected-file list shows 2 + 6 + 1 pages. After merging, expect nine pages, open the result, verify that page 3 begins the report and page 9 is the approval sheet, and keep the three source files until the nine-page combined PDF has been checked.

PDFandDOC Merge PDF processes the selected files in your browser, so those PDFs are not uploaded to PDFandDOC for the merge operation. Ordinary site assets and network requests can still occur, and a file imported from an HTTPS URL is fetched directly by your browser subject to the source site's CORS policy. Browser-local processing reduces one class of document transfer; it does not certify the file, browser, device, network or later sharing channel as safe. This description applies to the current PDFandDOC Merge PDF implementation and should not be generalized to unrelated online PDF services.

Questions

Does PDFandDOC upload my PDFs when I use Merge PDF?

No. The current Merge PDF workflow is browser-only and local-only, so selected PDF files are not uploaded to PDFandDOC.

Can I merge password-protected PDFs?

No. Encrypted/password-protected PDFs are not supported by the current tools, and there is no password prompt or decryption flow.

Does browser-local processing guarantee that a PDF is safe?

No. Local processing reduces the need to send document bytes to PDFandDOC, but you still need to trust your browser and device and review the output before sharing it.

How should I check a large merged PDF before I send it?

Start with objective checks: confirm that every intended source file appears once, the total page count matches the sum of the inputs, and the file order matches the selected-file list. Then inspect the transition between each source document and spot-check pages with unusual orientation, forms, signatures, tables or graphics. Keep the originals until the combined file has been reviewed so you can compare any questionable page without trying to reconstruct the source later.

Will merging preserve every advanced PDF feature exactly?

Do not assume that every advanced PDF feature has identical semantics after files are combined. The purpose of the current tool is to combine supported PDF pages in the selected order; it does not make a blanket promise about every bookmark, interactive form behavior, attachment, script, digital-signature state or application-specific feature a PDF might contain. If one of those features matters, inspect the downloaded file in the software and workflow where it will actually be used.

What happens if one selected PDF is malformed or outside the current limits?

The current workflow is designed to reject unsupported, malformed, encrypted or out-of-bounds input rather than silently move the job to a different processor. Remove or replace the problem file, confirm the tool's file/page limits, and try again with supported inputs. A failure does not trigger a hidden Secure Cloud merge fallback, so you can reason about the processing boundary shown on the page.

Evidence used for this guide

Reviewed by PDFandDOC product review. Last reviewed 2026-09-18.