Three straightforward steps
- Choose or paste the input requested by this tool.
- Configure the options and run the operation locally.
- Review and download or copy the result.
Combine multiple PDF files into one PDF locally in your browser.
On-device processing means the input is handled by browser APIs on the device running this page. Closing or refreshing the page normally clears the active in-memory working session.
Read the Privacy Policy →Arrange the selected documents in the exact reading order before creating the merged file. The operation copies pages into a new PDF; it does not edit the text or guarantee that existing forms, signatures, or advanced document features remain interactive.
Open the downloaded PDF and check page order, orientation, links, forms, and signatures before sharing it.
Merging creates one document from the selected PDFs in their displayed order. It combines pages; it is not a PDF editor or document repair service.
Open the downloaded result and review the first page, last page, page order, orientation, links, forms, and signatures. Complex interactive features can behave differently after pages are copied into a new document.
Rename source files or arrange them before merging when sequence matters. Keep the originals until the final document has been reviewed and accepted by its recipient.
A protected PDF may require its password or may block page copying. Remove protection only when you are authorized to do so.
No. The tool combines pages and does not promise file-size reduction. Images and embedded assets normally remain part of the resulting PDF.
Build one PDF from selected documents and verify complex features afterward.
Combine a cover sheet, twelve-page report and appendix into one client-ready PDF in that sequence.
Complex document navigation may not be retained; verify the result.
Yes, if each scan is a valid readable PDF.
Yes. This tool is labelled On-device, so the selected input is processed in your browser and is not sent to a ForgeMyFile processing API.
The tool shows a readable error and stops. It does not silently fall back to a cloud upload.
The browser is doing the work locally, so speed and practical file size depend on available memory, CPU and browser capabilities.