I Stopped Uploading My Files to Random PDF Sites. Here's What I Do Instead.

A few months ago I had to send a scanned ID and a signed contract to someone, and the PDF was too big to email. So I did what most of us do. I searched "compress pdf", clicked the first result, and uploaded the file.

The compression worked fine. But while the little progress bar was spinning, a thought hit me: I have no idea whose server this is. I don't know how long that file stays there, who can see it, or what happens to it next week. And I had just handed it a copy of my ID.

That was the last time I uploaded a personal document to a converter site.

The thing I didn't know: the browser can do it all locally

Here's what surprised me when I started digging. Modern browsers are quietly very capable. Between the File API, Canvas, and WebAssembly, most everyday file jobs can run right on your own machine:

• Merging, splitting and compressing PDFs
• Converting HEIC photos from an iPhone to JPG
• Shrinking images for a website or a form upload
• Converting between PNG, JPG, WebP and AVIF

No upload. No server. You pick the file, the work happens in the tab, you download the result. If you open your network tab while one of these tools runs, you'll see your file never leaves the machine. That's the part that sold me.

My boring, practical workflow now

Nothing fancy here. This is just what my week actually looks like:

1. PDF too big for email or a portal? I compress it locally first. Government and job portals in my part of the world are strict about file sizes (50 KB to 200 KB limits are common), so this comes up a lot. I use this free PDF compressor — it runs in the browser, so the document never gets uploaded anywhere.
2. iPhone photos that nothing else opens. HEIC files still break half the websites I use. Converting them to JPG locally is a ten-second job now.
3. Images for the web. A quick pass through an image compressor before uploading to a site, instead of shipping a 6 MB photo and hoping the platform deals with it.

Full disclosure, because DEV deserves honesty: I run VIPToolsKit, the site those tools are on. I built it around this one rule — files are processed on the user's device, not on my server. Partly for privacy, and partly because I'm cheap: processing files for thousands of strangers gets expensive fast, and browser-side processing costs me almost nothing in comparison. Everybody wins.

How to check if a "free tool" is handling your files properly

You don't have to take any site's word for it, including mine. Three quick checks:

• Read the privacy line before you upload. If a site can't say clearly what happens to your file, that's your answer.
• Watch the network tab. Process a test file with dev tools open. If megabytes are flowing up to a server, your file is on that server.
• Start with a dummy file. Never test a new tool with the one document that actually matters.

The trade-off, honestly

Browser-based tools aren't magic. A huge PDF can make a low-end phone struggle, and some heavy jobs (OCR on a 200-page scan, say) still genuinely need a server. But for the everyday 90% — merge this, shrink that, convert this photo — local processing is faster than uploading, and you keep your files to yourself.

I'm curious how other people here handle this. Do you still use the big upload-based converters out of habit, or have you moved your everyday file chores into the browser too?