PDF tools that never see your files

Every other online PDF tool follows the same pattern: you upload your file to a server, the server processes it, and you download the result. Somewhere in the middle is a copy of your document on someone else's infrastructure, and you have to take their word for it that the copy is deleted after a few hours and that nobody else looked at it. That model is fine for a random web receipt. It is uncomfortable for a signed contract, an ID scan, a payroll stub, a medical record, or a tax return.

yourpdfeditor takes a different approach. Every tool — merge, split, organize, sign, edit — runs entirely inside your browser tab using JavaScript and WebAssembly. Your PDF is read into memory locally, processed in place, and the result is handed back to you as a download. There is no upload endpoint, no temporary file in a server bucket, no audit log of who touched what. The privacy guarantee is structural rather than policy-based: even if we wanted to receive your PDFs, the code in the page does not contain anything that would send them.

You can verify this for yourself. Open your browser's DevTools, switch to the Network tab, and run any of the tools. You will see the page load (HTML, JavaScript, WebAssembly), but no request that contains the bytes of your PDF. You can even disconnect from the internet after the page loads — the tools still work.

A direct comparison, with the differences that actually matter:

yourpdfeditor was built for the situations where uploading a PDF to a random website feels off:

• Freelancers and contractors signing NDAs, contracts, and invoices — documents tied to client identities and payment details.
• Job seekers assembling resumes, cover letters, and writing samples into a single PDF for an ATS upload.
• Renters and homebuyers dealing with bank statements, IDs, pay stubs, and lease documents.
• Small business owners handling vendor contracts, invoices with bank details, and customer information.
• Healthcare patients and providers moving medical records and consent forms between clinics.
• Students and researchers compiling reading packets and signed permission forms.
• Anyonewho does not want a copy of their document sitting on someone else's server, even briefly.

PDF tools that run in the browser became practical in the last few years thanks to two things: WebAssembly (which lets the browser run near-native-speed code for parsing PDFs) and well-maintained open-source libraries like pdf-lib and pdf.js (which encapsulate the messy details of the PDF format).

When you open one of our tool pages, your browser downloads a JavaScript bundle that includes those libraries. Drop in a PDF and the file becomes an in-memory ArrayBuffer. From there, every operation — extracting pages, embedding images, placing text, rotating, merging — is a function call in the browser tab. The output PDF is built the same way, then handed back to you via a download. There is no step at which the file would be transmitted; there is no code in the page that would transmit it.

The upside is genuine privacy. The trade-off, for honesty: very large PDFs use your browser's memory rather than a beefy server's, so file size limits are about your hardware. In practice, modern laptops handle PDFs of several hundred megabytes without complaint.