No PDF content is uploaded
Every PDF you add is read into your browser as an in-memory ArrayBuffer. Merging runs inside a Web Worker on your own device. At no point is your file content sent over the network to any server.
Private by design
This tool was built around one promise: your files are processed on your device, not on a server. Here is exactly what that means in technical terms.
How it works
Every PDF you add is read into your browser as an in-memory ArrayBuffer. Merging runs inside a Web Worker on your own device. At no point is your file content sent over the network to any server.
File names appear only in your browser tab, so you can recognize your files and name the output. They are never transmitted, logged, or stored on a server.
Your PDF data is never written to localStorage, IndexedDB, cookies, or any other persistent store. Everything lives in memory for the session and is cleared when you close the page.
Once the page has loaded, you can turn off your internet and still add, reorder, and merge PDFs. The result downloads to your device. This is the strongest proof that nothing is uploaded.
The page only loads static assets: the HTML, CSS, JavaScript, the merge Web Worker script, and the pdf.js worker for previews. You can confirm this yourself in your browser's network tab — no request ever carries your PDF content.
Verified by you
Open your browser's developer tools and switch to the Network tab. Add your PDFs and merge — you will see only static asset requests, never your file content or file names. For the strongest proof, disconnect your internet before merging. The merge still completes and downloads to your device, because nothing was ever sent anywhere.
FAQ
Open your browser's developer tools, switch to the Network tab, then add and merge your PDFs. You will see only static asset requests. For an even stronger check, disconnect your internet before merging — the merge still completes and downloads.
No. The merged file is created in your browser memory and offered as a download to your device. There is no server-side copy, and closing the page clears everything from memory.
No cookies, localStorage, or IndexedDB entries are created for your files. The tool does not track what you merge, and no document data is sent to any analytics service.
They are gone. Because everything stays in your browser's memory and nothing is persisted, closing the tab or navigating away discards all file data immediately.
For any sensitive document — bank statements, contracts, medical records — yes. Online mergers receive your files on their servers, where they can be stored or exposed in a breach. A browser-only merger never sends your files anywhere, so there is nothing for a third party to access.