Are online PDF tools safe?

A key question: is your file uploaded?

One important safety question is whether your file leaves your device. Local and server processing involve different kinds of exposure, but neither alone proves that a tool is private or safe.

• Browser-side (client-side): the work is done on your own device by JavaScript running in the page. The file is opened, processed and saved locally without uploading it for processing. You still need to trust the site code, its dependencies and your browser extensions.
• Server-side: your file is sent to the company's servers, processed there, and (you hope) deleted afterwards. This can be perfectly reasonable, but it means placing your data, and your trust in their deletion policy, in someone else's hands.

For a great many everyday tasks, such as merging, splitting, rotating, adding page numbers, counting pages and filling forms, a modern browser is fully capable of doing the job on its own. In those cases there is simply no technical reason for a file to be uploaded at all.

Why browser-based processing is safer for sensitive files

When a document is processed locally, the server does not receive the document in the main processing request. That reduces upload, retention and breach exposure, but it is not complete proof of privacy: the page code, extensions and dependencies still need your trust. For documents like contracts, identity papers, bank statements and medical records, inspect the implementation and network behavior rather than relying on reassuring wording alone.

How to tell whether a tool really runs locally

These checks help assess a client-side claim, but neither is a complete privacy audit:

• The offline test. Load the page, then disconnect before selecting a non-sensitive test file. Success shows that run can work locally, not that data could never be sent later. Failure may mean a lazily loaded dependency needs an initial connection, not a file upload.
• Watch the network. Open your browser's developer tools, go to the Network tab, and run the tool. A large document upload is evidence that the file is sent, but its absence does not prove that no data leaves the page. Review requests and loaded code together.
• Weigh the honesty. A trustworthy site states plainly, per tool, whether the file stays local or is uploaded, rather than waving a vague "we respect your privacy" banner over everything.

A quick checklist before you upload anywhere

• Does the tool clearly say whether files are uploaded or processed locally?
• If uploaded, does it state how long files are kept and when they are deleted?
• Does it use HTTPS? This protects data in transit, not privacy after arrival.
• Does it explain what account or payment information it collects and why?
• Are the privacy policy and terms genuinely readable, not just present?

How this site handles it, honestly

We think the honest answer is more useful than a blanket promise, so here it is: most of our tools run entirely in your browser, and a few use server implementations, so they upload. We label every tool accordingly rather than pretending they all work the same way.

The browser-based tools, such as Merge, Split, Rotate, Compress, Fill PDF Forms, Sign PDF, PDF Metadata and Compare PDF, never send your file anywhere. Six tools use server implementations and therefore upload the file: Word ↔ PDF conversion (Word to PDF and PDF to Word), password protection, unlocking, repair, and OCR. For those, the file is sent over HTTPS and processed using temporary server files in a separate job directory; cleanup is attempted when processing ends, but immediate or secure deletion cannot be guaranteed. Uploads are size- and rate-limited.

Frequently asked questions

Is a browser-based tool automatically safe? No. Local processing avoids a document upload for that task, but you still trust the site code, dependencies and browser extensions. Offline and network checks provide evidence, not a complete privacy guarantee.

What should I know about the server-side tools here? They upload because their implementations run on the server. Files are sent over HTTPS and processed using temporary server files in a separate job directory; cleanup is attempted when processing ends, but immediate or secure deletion cannot be guaranteed. The point is that we identify these tools so you can decide.

Why do some tools here use a server? Their implementations use LibreOffice, qpdf, or Tesseract and PDF utilities on the server. That does not mean conversion, encryption, repair or OCR are universally impossible in a browser.

Does HTTPS mean my file is private? No. HTTPS helps protect an upload while it travels, but it says nothing about what happens after arrival. A locally processed file avoids that document upload, but the page code, extensions and dependencies still need trust.

The bottom line

Online PDF tools can be safe, but "online" is not automatically "private." For anything sensitive, favour tools that process files locally, use offline and network checks as evidence, and when a tool uploads, insist that it says so plainly. If you want to see this in practice, start with a client-side task like Merge PDF, or read our step-by-step guide to removing PDF metadata and guide to signing a PDF.