When this tool is useful
Joining reports, receipts, scans, appendices, or chapters while reviewing each real page before export.
How local processing works
PDF.js renders bounded local thumbnails for identification. The chosen page sequence is then copied as page objects into a new PDF, so the output is not rasterized.
How to use it
- Choose the source files.
- Review the available settings and page order.
- Process locally, inspect the result, and download it.
Important limitations
Interactive forms, signatures, bookmarks, attachments, annotations, and advanced document structures may not survive a page-object rewrite.
Verify the downloaded result
Reopen the downloaded file in its destination application, check dimensions or page count and visible content, and keep the source until the result has been accepted.
Private by design
Your files stay in this browser. The tool does not upload the source or output to our servers.
Questions and answers
Does this tool upload my files?
No. Processing happens in your browser; closing the page clears the working session.
Will the output always match the source exactly?
Interactive forms, signatures, bookmarks, attachments, annotations, and advanced document structures may not survive a page-object rewrite.
What should I check before using the result?
Reopen the downloaded file in its destination application, check dimensions or page count and visible content, and keep the source until the result has been accepted.
Which browsers and devices are supported?
Use a current browser with JavaScript, workers, canvas, WebAssembly where the format requires it, Blob downloads, and enough memory. Reopen important downloads in the destination application.
Concrete input and output example
Input a two-page cover PDF, a ten-page report, and a one-page appendix in that order. The result should contain 13 pages; verify forms, signatures, bookmarks, and attachments separately.
Browser compatibility notes
Reviewed against the visual page workspace and required web APIs on 2026-08-19. Use a current browser and verify important output on your device.
- Chrome / Edge (current desktop)
- Requires local PDF parsing, worker/canvas APIs where applicable, document creation, and Blob download.
- Firefox (current desktop)
- Uses the local PDF workflow; always verify the generated download in its destination viewer.
- Safari (current desktop)
- Uses the same local workflow; large page sets can have a lower practical memory ceiling.
A tool-specific question
Why should digital signatures be checked after merging?
Copying pages into a new document changes document bytes and structure, which can invalidate or omit signature-related data.