Why We Never Upload Your Files: The Case for Client-Side Conversion

Search for "merge PDF online" and you'll find dozens of free services. Almost all of them work the same way: you upload your document to their server, they process it, and — hopefully — delete it afterwards. It's convenient, and for most people that's where the thinking stops.

But "hopefully" is doing a lot of work in that sentence.

What actually happens to uploaded files

When you upload a file to a web service, it typically passes through several systems you've never heard of: a load balancer, an application server, temporary disk storage, sometimes a third-party processing vendor, and often cloud storage buckets with retention policies written by someone else.

• Retention: "We delete files after 1 hour" is a promise, not a guarantee. Backups, logs, and error dumps often keep copies far longer.
• Access: Server-side files can be accessed by employees, contractors, or attackers who breach the system.
• Jurisdiction: Your files may be stored in data centers under legal regimes you didn't choose.

None of this is necessarily malicious — it's simply the architecture of server-side processing. The file must leave your device for the work to happen.

The client-side alternative

Modern browsers changed the equation. Three technologies now make full file processing possible on your own device:

1. The File API — lets a webpage read a file you select, entirely in memory.
2. Canvas & WebAssembly — provide near-native speed for image and PDF manipulation.
3. Mature open-source engines — libraries like pdf-lib, jsPDF, and PDF.js do the heavy lifting without a server.

At ConverterTools, when you drop a file onto a tool, the browser reads it from your disk, processes it in local memory, and hands the result straight back to your downloads folder. No network request ever carries your file's content.

What this means for you

• Sensitive documents are practical. IDs, contracts, medical and financial papers can be converted without ever existing on someone else's machine.
• It's faster. No upload queue, no server round-trip — conversion starts immediately.
• It works offline. Because the code runs locally, our PWA keeps working without internet once installed.

An honest limitation

Client-side processing uses your device's CPU and memory. Extremely large files (hundreds of megabytes) will run slower than on a data-center server, and very old devices may struggle. For everyday documents and images, though, local processing is both faster and safer — which is why we built ConverterTools this way from day one.