What local browser image processing means for your files

Selecting a file is not the same as uploading it

Our crop, compress and split tools read the selected image in your browser, decode it, draw it and export the result on your device. These tools do not send originals or results to our server. Speed and capacity still depend on device memory, image dimensions and browser support; local processing cannot guarantee unlimited file sizes.

The website still makes network requests

Loading pages, scripts, styles and locally hosted fonts requires website requests. Infrastructure may receive your IP address, requested path and browser information. Sign-in, verification and billing pages communicate with their respective services. No image upload describes the local editing workflow, not an entirely offline website or an absence of all network data.

The workspace is not long-term storage

The image, selection and results exist in page memory rather than a cloud draft synced to your account. Reloading, navigating to another tool or changing language clears the workspace. Download completed files first; they are saved where your browser or operating system places downloads. Leaving the page does not erase downloaded files, including on a shared device.

Cloud services have a different boundary

Watermark, people, object, text and logo removal use cloud tasks. Submitting uploads the image and creates server records, so the local image no-upload description does not apply. Check the relevant use and retention terms before submitting, and download completed results promptly. Identify the tool before processing sensitive material and read the privacy policy. Never send support verification codes, access tokens or full payment details.

Checklist

• Confirm whether you are using a local or cloud feature
• Download before reloading, navigating or changing language
• Check downloaded files and sign-out status on shared devices