Privacy
Proof that your images never leave your device
Every tool on this site decodes, edits and re-encodes images inside your browser. Nothing is uploaded, so there is nothing to delete later and nothing to leak. You do not have to take our word for it: here is how to check with the tools built into your browser.
Counted in the page: every request with a body of 4 KB or more sent by fetch, XMLHttpRequest or sendBeacon.
Check it yourself in two minutes
- Open any tool, then open your browser's developer tools (F12 or Ctrl+Shift+I) and switch to the Network tab.
- Add a photo and run the tool. Filter the Network tab by method POST or PUT: there is no request carrying your image. The only traffic is the page, its scripts and fonts.
- Turn Wi-Fi or mobile data off, run the tool again, and download the result. It still works, because the work never depended on a server.
- Look at the response headers of any page: the Content-Security-Policy allows connections to this site only, so the browser itself blocks any attempt to send data elsewhere.
Why most image sites cannot say this
Server-side tools upload your file, process it on their machines and keep it for minutes or hours. Their privacy pages explain the deletion schedule; the upload itself is unavoidable for them.
Modern browsers can decode and encode JPEG, PNG, WebP and AVIF, run WebAssembly codecs for HEIC and TIFF, and process pixels in background threads. That is all an image tool needs, so there is no reason to send anything.
Doing the work locally is also faster: a 10 MB photo never travels over your connection, and the result appears in a second or two, with no queue.
What the counter does and does not cover
The counter adds up the bytes of outgoing requests that carry a body of at least 4 KB, which is the size class of an image upload. If you accept ads or analytics, those services send small beacons that stay below that threshold; they never receive your images either.
Opening a shared image from another app brings a file into the site, not out of it, and is not counted. The counter resets when you reload the page.