You have a scanned copy of your passport or a signed contract that needs compressing before uploading. But before you hit upload — stop. Where does your image go? Who can see it?
Honestly, I wrestled with this question myself when I started building this tool site. I found many online image compressors that worked well, but every time I dragged an image onto a webpage, I wondered: is this image being saved on their server? Could someone else see it?
This is a question worth taking seriously. Especially when you are dealing with sensitive images — ID scans, contract screenshots, product design drafts. If these leak, the consequences can be serious.
Two types of online compression
Online compression tools fall into two categories:
Server-side compression: Your image is uploaded to a remote server, compressed there, and sent back. Most traditional tools work this way. The advantage is support for more formats and more complex algorithms. The downside is that your image leaves your device — and you have no control over what happens on the server.
Client-side (browser) compression: The image is read into browser memory, processed entirely in JavaScript, and compressed — all without any network transfer. This is the approach YoolBox and a few modern tools use. The image never leaves your device, so privacy is guaranteed. The limitation is browser memory — very large files (over 50MB) may be slow to process.
How to tell which type a tool uses? Open the browser developer tools (F12), switch to the Network tab. When you upload an image, if you see a POST request to a remote server, it is server-side. If there are no network requests, it is client-side.
What information could leak?
Even if you trust a tool not to misuse your images, there are invisible risks: EXIF data (GPS coordinates, camera model, timestamp), file names (like "ID-card-front-ZhangSan.jpg"), and metadata (editing software, author info). These can all expose sensitive information.
5 security signals
1. Privacy policy explicitly states "local processing" or "no server upload."
2. The tool works even when disconnected from the internet.
3. The website uses HTTPS.
4. The Network panel shows no POST/PUT requests during compression.
5. Clear data retention policy — are images deleted immediately after processing?
How Canvas compression works
YoolBox's image compressor uses Canvas API technology. The flow is: you select an image → the browser reads it into memory → JavaScript draws it on a Canvas element → re-encodes it at your chosen quality → outputs Blob data → triggers a browser download.
Throughout this entire process, the image data never leaves your browser's memory. That is why it works offline — all computation happens locally. I chose this approach because I wanted users to use my tool without worrying about privacy.
Summary
Online image compression itself isn't dangerous. What is dangerous is not knowing where your images go. Before using a tool, confirm whether it processes images client-side or server-side. For sensitive images, always choose client-side processing. YoolBox's Image Compressor is fully local with zero network transfer — feel free to verify by disconnecting your internet.