A narrow fetch boundary
Only public HTTP/HTTPS destinations and supported image responses are accepted; this is not a generic open proxy.
Fetch one public JPEG, PNG, WebP or static AVIF URL, then compress it locally in your browser.
Fetch one public image, then compress and download it locally.
Direct browser fetch is tried first. The fallback blocks private networks, validates redirects and never forwards credentials.
Paste one direct public image address. The tool validates the URL and content, imports the bytes, then hands the file to the same browser worker used for local uploads.
Only public HTTP/HTTPS destinations and supported image responses are accepted; this is not a generic open proxy.
Direct-image intent has one canonical route. Wording variants are kept as on-page language rather than duplicate indexable pages.
URL mode must contact the remote image host and may use the limited fetch service. It does not turn local file compression into a server upload workflow.
Enter an HTTP or HTTPS URL that points directly to a supported static image.
A direct browser request is preferred. The constrained proxy is used only when CORS prevents access and revalidates redirects and public destinations.
The imported file enters the normal preview, settings, worker and download flow; encoding is not moved to the server.
Paste the URL of one image file, not a webpage containing images. Use the Website URL mode when you want to discover candidates from a page.
The browser tries a direct CORS-enabled fetch first. When that is blocked, the limited server fallback validates the public destination and response before returning image bytes to the browser.
Compression, resizing, conversion, comparison and ZIP creation happen locally after the requested bytes reach your browser. The remote host necessarily receives the image request.