Plenty of image sites promise privacy, but the mechanics matter more than the promise. This article explains what 'browser-based processing' actually means technically, where your files go — and don't go — and how to check any tool yourself in about a minute.
The two architectures behind online image tools
Most online image tools work one of two ways. Server-based tools upload your file, process it on a remote machine, and send the result back. That architecture is easy to build but means a copy of your image — sometimes a photo of a person, a document or a whiteboard — sits on someone else's server, in logs, backups and caches you can't inspect.
Browser-based tools ship the processing code to your browser instead. The decoding, the pixel math and the re-encoding all run on your device, using standard browser APIs like Canvas and WebAssembly. The file is read from disk into memory and never transmitted.
What 'client-side' means for your files
- No upload step exists — there is no request carrying your image that could be intercepted, logged or retained.
- Processing capacity is your device's, so a large photo takes as long as your CPU needs and no server queue is involved.
- Results are created in browser memory and handed to you as a download; the original file on disk is never modified.
- Closing the tab discards everything. There is nothing stored to delete later.
How to verify any tool in one minute
Open your browser's developer tools (F12), switch to the Network tab, and use the tool with a real image. Watch the requests: a genuinely client-side tool shows no request containing your image data. Load the page, disconnect from the internet, and run the operation again — it should still work.
Where browser tools still touch the network
Loading the page itself, the fonts and (for some formats) a WebAssembly codec are legitimate network requests — they happen before or independently of your files. That's why the honest claim is usually 'your images are processed locally', not 'the site works offline from the first visit'.
Try it with these tools
Related articles
Guides
What Is Base64 Image Encoding?
What Base64 actually does to image data, why data URIs exist, and the size cost that decides when embedding beats linking.
Read articleFormats
JPG vs PNG: Which Image Format Should You Use?
Why JPEG wins for photos and PNG wins for everything else — compression types, transparency, and the simple decision rule.
Read articleEvery tool mentioned in this article runs entirely in your browser — see privacy for what that means.