How image processing works

You open files locally

When you pick an image, the browser reads it from your device into memory (typically via the File API). We do not operate a remote upload queue for those core editor workflows: there is no server-side folder where your private photos wait to be processed.

You choose when to download results. Exports land in your downloads folder like any other file you save from the web.

Processing uses browser APIs

Tools decode images with standard browser image decoders, manipulate pixels on a canvas or equivalent in-memory surface, then re-encode to JPG, PNG, WebP, AVIF, or other supported output formats. Resize, crop, compression quality, and color adjustments are applied in JavaScript on your machine.

Icon and density generators follow the same model: scale variants are computed locally and packaged into a ZIP you download—still without sending your artwork to our servers for that step.

What still touches the network

• The website itself — HTML, CSS, JavaScript bundles, and fonts load from our host like any static or server-rendered site.
• Optional analytics or ads — If enabled, third-party scripts may send their own telemetry under their policies (see privacy).
• Support email — Only if you contact us; that is separate from opening a file in a tool.

None of the above is the same as uploading your image file to us for editing.

Practical limits

• Very large sources are bounded by available RAM and browser tab limits.
• Some formats (for example HEIC) depend on what your browser can decode.
• Shared or public computers may retain files in cache or downloads—you control that environment.

What we recommend

For confidential documents, use a trusted device and clear downloads when finished. For product and marketing workflows, pair these tools with our guides and the FAQ for format-specific tips.