"Free online PDF tool" covers two genuinely different things, and it's worth knowing which one you're using before you drop in a tax form, ID scan, or signed contract.
Server-side tools
Most PDF websites work like this: you upload your file, their server processes it, and you download the result. This is how a lot of the "power" features (real Word/Excel conversion, OCR on scanned text) actually get built, since those genuinely need a full document-rendering engine that only really exists server-side. The trade-off is that your file — even briefly — sits on a server you don't control. Reputable ones delete it after a set time and say so in their privacy policy; less reputable ones may not.
Client-side (in-browser) tools
The other approach loads a PDF-processing library directly into the web page and does the work in your browser's own memory, using your device's own processing power. Your file is read locally, transformed locally, and handed back as a direct download — it's never transmitted anywhere. TechDriven Tools works this way for every tool it offers, which is also exactly why it can't offer real Word/Excel conversion: that specific operation needs the kind of rendering engine that only runs practically on a server, and there's no honest way to fake that in a browser. (OCR text recognition, by contrast, genuinely can run in the browser via WebAssembly — see OCR PDF.)
How to tell which one you're using
- Open your browser's dev tools → Network tab before running a tool, then use it. If your file gets uploaded, you'll see a request with a large payload going out to a server. A genuinely client-side tool shows no such request — only the initial page load and library downloads.
- Check what the tool claims to support. If a "free" tool offers OCR, or Word/PowerPoint conversion, it is doing that server-side — there's no way around needing a server for those specific features, so at minimum your file is passing through one, however briefly.
- Read the privacy policy, specifically the retention section — not just "we take privacy seriously," but what actually happens to uploaded files and for how long.
The practical takeaway
Neither approach is universally "wrong" — server-side processing is a legitimate trade for features that genuinely need it. The point is knowing which trade you're making. For everyday tasks that don't need OCR or Office conversion — merging, splitting, compressing, rotating, watermarking, signing — a client-side tool means that trade-off simply doesn't apply, because there's nowhere for the file to be exposed in the first place.