What the image tools do
The file picker gives the browser a local File object. The image tool decodes it in the current tab and draws pixels to a canvas for resizing, cropping, compression, format conversion, watermarking, or palette sampling.
The tool scripts do not send the selected file, pixel data, or filename to an image-processing server. They also do not save the image into this site's local storage. Closing or reloading the tab removes the in-memory working state.
What happens to metadata
Canvas exports are generated from decoded pixels, not from the original file container. Do not rely on a new download to preserve EXIF, orientation notes, embedded thumbnails, or other metadata.
If metadata matters for a professional workflow, keep the original and use a metadata-aware tool designed for that purpose.
Separate image handling from site requests
The site still makes ordinary requests to its host. It also loads Google's Funding Choices consent script; AdSense code is present on the homepage and editorial pages in this source version.
Google and other providers may process request, device, cookie, advertising, and consent information as described in the Privacy Policy and their own notices. Local image processing does not mean the whole page makes no network requests.
Common questions
Does local processing mean the site has no third-party requests?
No. The image tool does not upload your file, but this site loads Google consent code and advertising code on selected pages.
Should I use these tools for confidential images?
The image bytes are handled by the browser tool in this tab. Consider your device, browser extensions, shared-screen risks, backups, and whether the image contains sensitive information.
References
- MDN: File API
- MDN: HTMLCanvasElement.toBlob()
- Google: How Google uses information from sites or apps that use our services
Sources explain browser behavior or guidance; they do not verify a particular output file.