Add your JPEGs
Drag them in. Mixed folders are fine — PNG and WebP get handled too.
Most online compressors upload your photos to their servers. This one does not. Batch-compress up to 20 files free, locally.
Drop images here
or · JPG, PNG, WebP, GIF
Drag them in. Mixed folders are fine — PNG and WebP get handled too.
Around 70–80 is the sweet spot for photos: usually 60–85% smaller with no visible difference. Go lower for thumbnails.
You get a per-file report showing exactly how many bytes each image lost.
Those services upload your images to their servers and process them there. That means your files sit on someone else's disk, and you hit upload limits. This tool processes everything inside the browser tab.
Typical photos compress 60–85% at quality 75. Screenshots and graphics often reach 90%+. The exact number depends on the source image.
Yes. Choose WebP as the output format for the best results on PNG sources, or keep PNG lossless.
No artificial limit. Very large images (50 MP+) may be slow on older machines because everything runs on your own CPU.
The quality slider is the JPEG quantisation factor, not a percentage of "how good it looks". These are the empirically useful bands.
| Case | Value | Why it matters |
|---|---|---|
| 95–100 | Archive / print master | Roughly 2–4× smaller than the raw file. Indistinguishable at any zoom. |
| 85–92 | Web hero images | Safe default for large photos. No visible artefacts at 100% zoom on a retina display. |
| 70–82 | General web / product photos | 60–85% smaller. Slight softening visible only when zoomed. This is where most sites should live. |
| 55–68 | Thumbnails, previews, email | 80–90% smaller. Blocking appears in smooth gradients like skies. |
| 30–50 | Aggressive, form uploads | Only when a hard KB cap forces you. Visible artefacts, but readable. |
| Below 30 | Not useful for photos | Destroys detail. Crop or downscale the pixels instead. |
Saving a JPEG at 75 that was already saved at 75 compounds the damage. Always compress from the original, once.
Resizing down already removes most of the bytes. Compress second and you can often use quality 85 instead of 60 and still hit the same file size.
A 6000 px wide photo at quality 90 is still 4 MB. Halving the pixel dimensions cuts file size by 75% with almost no perceptual loss.
Artefacts hide at reduced zoom. Always check at 100% before accepting.
For flat graphics and screenshots, PNG or WebP beats JPEG badly. For noisy photographs, a high-quality JPEG is still competitive.
| Free, this page | Bulk Image Kit $19 | |
|---|---|---|
| Batch limit | 20 images | Unlimited |
| Quality control | Slider 30–100 | Slider + per-image override |
| Output formats | JPEG, WebP, keep original | All of the above + PNG |
| Before/after report | Per file | Per file + batch totals |
| Runs offline | After first page load | Always |
Re-encoding a file that was already aggressively compressed can increase size, because the encoder rewrites tables your source had stripped. It also happens if you output PNG from a source that was a small JPEG — PNG cannot compress photographic noise.
Yes. The re-encode drops EXIF, including GPS coordinates and camera model. For sharing photos publicly that is usually a privacy win.
Not with a single pass. Set a low quality, check the reported output size, then adjust and re-run. Two or three passes gets you under almost any cap.
The browser encoder writes baseline JPEG. Progressive is marginally smaller for large images but is not exposed by the canvas API.
Bulk Image Kit is the same engine as a single offline file — unlimited images, resize + compress + watermark + rename, one-time $19, no subscription.
See Bulk Image Kit — $19