Why You Should Never Upload Sensitive PDFs to Online Tools

Every day, millions of people drag a PDF onto a website, click "Compress" or "Convert," and download the result without a second thought. What most don't realise is that their file — often containing a contract, a payslip, a medical record, or bank statements — just took an invisible round trip to a server they know nothing about.

The invisible journey of your PDF

When you upload a PDF to a typical online tool, here's what actually happens behind the scenes:

1. 1.Your browser sends the entire file as a multipart HTTP request to a server — usually in a data centre operated by a third party.
2. 2.The server processes the file. During this window, the file exists as a readable binary on disk or in memory.
3. 3.The processed file is written back to temporary storage and a download link is generated for you.
4. 4.The original and the result sit on that server until a scheduled cleanup job removes them — typically anywhere from 1 to 24 hours later.

That's four separate moments where your file exists on infrastructure you don't control, operated by a company whose security practices, staff access policies, and data jurisdiction you have no visibility into.

What "we delete files after X hours" really means

Most PDF services claim to delete your files after a set period — often 1 hour or 24 hours. This promise is well-intentioned but provides weaker protection than it sounds:

The risk scales with the sensitivity of the document

Most people upload PDFs that they'd never hand to a stranger on the street:

• Tax returns and P60s containing your NI number, income, and employer details
• Bank statements with account numbers and transaction history
• Medical records, prescriptions, and GP letters
• Legal contracts with pricing, IP clauses, and signatory names
• CVs with your address, phone number, and date of birth
• Passports or driving licences uploaded as identity documents

Each of these has real-world value to bad actors. Identity theft, financial fraud, and corporate espionage all start with data leaks that seemed minor at the time.

The browser-based alternative

Modern browsers are capable of running full compression pipelines locally — no server required. This is made possible by WebAssembly, a binary instruction format that lets native applications (like Ghostscript, a professional PDF engine) run at near-native speed inside your browser tab.

When you compress a PDF using LocalDF's compressor, the entire operation happens in your browser's memory:

1. 1.The file is read from your disk into browser memory using the File API.
2. 2.Ghostscript (compiled to WebAssembly) processes it entirely within your browser tab.
3. 3.The compressed output is offered to you as a download — direct from browser memory to your disk.

Your file never touches a network request. Not even a byte of it.

How to verify your file never leaves your device

You don't have to take our word for it. Here's how to verify it yourself in under 30 seconds:

Practical rule of thumb

Before uploading any document to an online tool, ask: would I hand a printed copy of this to a stranger in exchange for a compressed version? If the answer is no, use a tool that processes the file locally.

Browser-based PDF tools have reached the point where they match — and in some cases exceed — the output quality of server-side tools. The privacy benefit is now available with no trade-off in quality or convenience.