Client-side vs cloud PDF editors

Most "online PDF tools" work by uploading your file to a server, processing it there, and sending it back. A client-side tool does the work in your browser, so the file never leaves your device. For anything sensitive, that difference is the whole game.

What "upload" really means

When you upload a contract, medical form, or ID scan to a web service, you're trusting that company to: transmit it securely, not keep a copy longer than promised, not train on it, not get breached, and not hand it over on request. Even reputable services carry that surface area. Their privacy policy — not your intent — governs what happens next.

How client-side tools work

Modern browsers can do the heavy lifting themselves with JavaScript and WebAssembly. The PDF is read into memory locally, edited locally, and saved locally. There's no upload endpoint to trust because there's no upload at all. Many such tools also work offline after first load.

Trade-offs

• Client-side pros: privacy by design, works offline, no account, no file-size caps from a server.
• Client-side cons: limited by your device's memory; a few heavy features (like huge-batch server jobs) are better suited to a desktop app.
• Cloud pros: offloads work from weak devices; some advanced processing.
• Cloud cons: your file is on someone else's computer.