Skip to main content
Privacy & Security 4 min readUpdated January 5, 2026

How Image Processing Works (Client-Side Privacy)

Learn why your images never leave your browser when using Kamili Toolbox image tools.

One of the core principles of Kamili Toolbox is that **your files stay on your device**. Here's how that works. ## The Canvas API For most image operations (resize, crop, rotate, compress, filters), we use the browser's built-in **Canvas API**. This means: 1. You select an image file 2. Your browser loads it into memory (not uploaded anywhere) 3. JavaScript applies the transformation using Canvas 4. The result is available to download — still in your browser No data ever touches our servers. ## WebAssembly (WASM) Processing For more complex operations like HEIC conversion, PDF processing, and advanced compression, we use **WebAssembly** (WASM) modules. These are compiled binaries that run inside your browser at near-native speed. The code executes locally — your files are never transmitted. ## When Does Data Leave My Browser? Only for **AI-powered tools** (marked with an "AI" badge). These tools require sending your data to an AI API for processing. In those cases: - Data is transmitted over HTTPS - It is not stored after processing - You must be signed in - The tool clearly indicates that server processing is used ## Verifying Privacy You can verify our claims using your browser's Developer Tools (Network tab). For client-side tools, you'll see zero uploads when you process a file.
Back to Knowledge Base
How Image Processing Works (Client-Side Privacy) — Kamili Toolbox