Pick a quality and a maximum width. See how many percent each file shrank; batches come as a ZIP.
🔒 This file never leaves your device — nothing is sent to a server
Two things: pixel count and compression quality. Shrinking a 4000px photo to 2000px quarters the pixels and cuts most of the size on its own; quality 75–80 is hard to tell from the original on screen. Using both is the most effective.
JPG is simply re-compressed as JPG. PNG is lossless, so the quality slider does nothing for it; only the width helps — if a photo was saved as PNG, choosing to JPG makes it far smaller. PNGs that need transparency shrink well with to WebP, which keeps it.
Application forms usually say something like 'under 2 MB, about 1200px wide'. Use the preset and check the KB in the result list; the −% shows how much each file shrank.
The result is redrawn through a canvas, so EXIF location and device data are not carried over. To strip metadata without touching quality, use Remove Photo EXIF & GPS.
No. Shrinking and saving happen in your browser. Load the page, go offline, and it still works.
A phone photo of 3–5 MB usually lands at 300–600 KB at 2000px and quality 78. Already-small files barely change; if one gets larger (+%), keep the original.
Below about 70, gradients and edges around text start to smear. Use 75–82 for screens and 90+ for print.