ImageFlowPrivacy by architecture
How ImageFlow processes images in your browser.
ImageFlow’s current tools decode, transform, encode, and package files with browser APIs on your device.
Reviewed by ImageFlow · Last verified
- source or output image bytes;
- filenames, thumbnails, or embedded metadata;
- text or image watermark assets.
What the browser does
A Web Worker handles decoding, pixel changes, and encoding outside the main interface thread. The result returns to the page as an in-memory file, and object URLs are revoked when results are replaced or the page closes.
How we verified local processing
We inspected browser network traces for image conversion, PDF extraction, and failed image decoding. Processing used the same-origin ImageFlow worker and local blob URLs. The traces showed no external image-service requests, file uploads, or request bodies.
Where the limit is
Files with unsupported signatures, files above 50 MB, and unsafe output dimensions are rejected. Format availability can differ by browser; if a requested codec is unavailable, the tool reports that instead of changing the format silently.
What about future AI actions?
Local-first does not mean every future operation must fit inside a browser. AI upscale, generative backgrounds, or another compute-heavy action may eventually need a remote processor. None is available today.
Before upload, it will say that the file leaves your device, who processes it, when temporary files are deleted, and whether the operation uses a quota or costs money. A local action will never switch to remote processing silently.
Try a local tool
- Convert images to JPEG, PNG, WebP, or AVIF.
- Compress a batch while keeping each image’s source format by default.
- Remove image metadata from a new downloadable copy.