Make your images smaller, without the upload

No. The files are read by your own browser and re-encoded on your device with the canvas API. Nothing is uploaded, so nothing can be stored, logged or leaked on the way. You can confirm it by going offline after the page has loaded — compression still works.

Compressing reduces the file size while keeping the same pixel dimensions, by re-encoding the image with a lower quality or a more efficient format. Resizing changes the pixel dimensions, which also reduces the file size. This tool can do both at once, so you can cap the width at 1600 pixels and still choose a quality level.

WebP gives the smallest file at a quality most people cannot tell apart from the original, and every current browser supports it. Choose JPEG when something else has to read the file — older software, some print services, some upload forms. Keep PNG only when you need lossless quality or transparency.

PNG is a lossless format, so the quality slider does not apply to it: the same pixels always produce roughly the same bytes. To shrink a PNG meaningfully, convert it to WebP or JPEG — both are offered in the output format selector. Keep PNG when a screenshot needs perfectly crisp text or a transparent background.

Yes. The image is redrawn onto a canvas and then re-encoded, which drops the metadata block entirely — camera model, timestamps and GPS coordinates included. That is usually what you want before publishing a photo, but it also means extracted images will not carry their original capture information.

There is no server limit, because nothing is uploaded. The practical ceiling is your device's memory: extremely large images, or hundreds at once on a phone, can be slow or fail. Process them in smaller batches if a very large set stalls.