Every time you drag a file into an online converter or compressor, it is worth asking a simple question: where does my file actually go? For most tools, the answer is “up to a server you have never heard of.” But there is a better way. Client-side tools do all of their work inside your own browser, so your files never leave your device at all. Here is why that matters for your privacy, how the technology works, and how to tell a genuinely private tool from one that is quietly uploading your data.
What “client-side” actually means
In web terms, the “client” is your device and its browser, while the “server” is the remote computer that sends you a web page. Client-side simply means the work happens on your side — locally, in your browser — rather than on that remote server. When a file tool is client-side, your image or document is opened, read, and processed right there on your own machine. The website’s server only ever sends you the page and its code; it never receives your file. Server-side tools do the opposite: they take your file, send it across the internet, process it on their hardware, and return the result.
The privacy problem with most online tools
The trouble with the server-side approach is that it puts a copy of your file on a computer you do not control. For a casual image that may not matter, but think about what people actually run through these tools: signed contracts, bank statements, passport scans, medical letters, tax documents, private photos. Every upload means trusting an unknown company to store your file securely, to delete it when promised, and never to be breached. Even well-meaning services can leak data, and not all of them are well-meaning. The moment your file leaves your device, you have lost control over where it goes and how long it lasts.
How client-side processing keeps your files private
Client-side tools sidestep the entire problem by never sending your file anywhere. Because the processing happens in your browser, the data simply stays put. There is no upload, so there is nothing to intercept in transit; there is no server copy, so there is nothing to store, leak, or subpoena; and when you close the tab, whatever the tool was working on is cleared from memory and gone. This is not a promise to handle your data carefully — it is an architecture in which the sensitive data never reaches anyone else in the first place. For genuinely private files, that is the strongest guarantee there is.
The technology that makes it possible
It might sound surprising that a browser can do this kind of work on its own, but modern browsers are remarkably powerful. The Canvas API lets a page read and manipulate image pixels directly. WebAssembly allows high-performance code — the same kind of compression engines that used to require a desktop program — to run at near-native speed inside the browser. And Web Workers let that heavy lifting happen on a background thread, so the page stays responsive even while it crunches a large file. Together, these technologies make it possible to compress photos, convert formats, and merge documents entirely on your device, with no server round-trip and no waiting for an upload to finish.
How to tell if a tool is really client-side
Not every tool that claims to be private actually is, so it helps to know the signs. First, read what the tool says: a genuinely client-side tool will state plainly that your files are processed locally and never uploaded, and it will back that up with a clear privacy policy. Second, notice the behaviour: client-side tools usually work instantly with no upload progress bar, and they often keep functioning even if your connection drops mid-task. Third, for the technically curious, check the network tab in your browser’s developer tools — load the tool, process a file, and watch whether any large upload request is sent. If your file never appears in the outgoing network traffic, the work is happening locally.
Privacy is a feature, not an afterthought
We built our tools around a single promise: your files never leave your device. The image compressor shrinks your photos in the browser, and the merge PDFs tool combines your documents the same way — locally, with nothing uploaded, no account required, and no copies left behind on a server. We can make that promise confidently because of how the tools are built, not because of a policy we ask you to take on faith. You can read exactly how we handle data, cookies, and advertising in our privacy policy. Privacy should be the default for everyday tools, and with client-side processing, it finally can be.
Frequently asked questions
What does client-side mean? Client-side means the work happens on your own device — in your browser — rather than on a remote server. For file tools, it means your files are read and processed locally and never uploaded.
Are client-side tools as powerful as server-based ones? For most everyday tasks — compressing images, converting formats, merging PDFs, generating QR codes — yes. Modern browsers are surprisingly capable, and you also avoid upload waits and server file-size limits.
How can I be sure a tool isn’t uploading my files? Check that it states files are processed locally, look for a clear privacy policy, and for the technically curious, you can open your browser’s network tab and confirm no file upload request is sent.