Compress JPG, PNG, WebP and other images with a visible quality setting, optional downscaling and before/after file sizes for every image. The entire batch stays on your device.
PNG · JPG · WebP · BMP · GIF · SVG · AVIF
A smaller file is not automatically a better file. Very low quality creates ringing around edges and muddy detail; very high quality can preserve bytes nobody can see. Start near 82, inspect the busiest image in the set, then move the slider.
A 6000-pixel camera image displayed at 1200 pixels wastes more bandwidth than a sensible quality setting can recover. Limit the longest edge first, then compress. The practical sequence and format tradeoffs are covered in our web image compression guide.
Start around 80–85 for web photos. Product shots with text or sharp edges may need 88–92. Check the reported size change and a downloaded result before publishing the batch.
Re-encoding a PNG stays lossless and may not shrink much. For photos, WebP or JPG usually produces a far smaller file; for transparency, use WebP.
No. The browser decodes pixels and creates a fresh image, so camera, location and other embedded metadata are not carried into the result.
Re-encoding a file that is already well compressed can cost more bytes than it saves, and PNG output of a photograph is usually larger than the JPG you started with. Each row reports the size change, so switch the output format or lower the quality when you see a larger result.
Yes, with lossy formats. Each pass encodes the decoded pixels of the previous pass, so artefacts accumulate even at the same quality number. Work from the original file rather than from a compressed copy.