Batch JPG compression behavior
This page focuses on multiple JPG photos, where quality and width controls usually drive the final size.
Each file is encoded independently, so savings vary by photo detail and dimensions.
Batch Compress JPG Online
Shrink multiple JPG photos for websites, forms and email while keeping every source file on your device.
JPG batch inputJPG or WebP outputPer-file progressZIP download
Batch JPG compressor
Up to 20 images, 25 MB each, 200 MB total.
0 files selected
Total original: -
Total result: - · Saved: -
| File | Original size | Result size | Saved | Status | Download |
|---|---|---|---|---|---|
| Choose JPG images. | |||||
Only need one JPG?Use the single JPG compressor
How it works
- 1Select multiple JPG files.
- 2Choose JPG or WebP output and adjust quality.
- 3Run the batch and download each file or the ZIP.
Privacy and limits
- JPG files are processed locally.
- Canvas export may remove EXIF metadata.
- The batch queue is limited to protect browser memory.
Common use cases
- Compressing product photo sets
- Preparing many JPG attachments
- Reducing article photos before upload
Format notes
- Lower quality can introduce visible artifacts.
- WebP output may be smaller when accepted by the target workflow.
- EXIF metadata is usually removed by Canvas export.
Original test sample
- Run a group of phone photos at quality 76 and max width 1800.
- Use ZIP download when all rows finish successfully.
Frequently asked questions
Are my images uploaded?
No. ImgShrink processes selected images in your browser and does not upload them to a server.
Do batch tools upload files or save history?
No. The queue runs locally in your browser, and ImgShrink does not create an account, database record or saved image history.
Why is an output format unavailable or different?
The browser controls image decoding and export support. Some browsers may not export AVIF or may flatten unsupported transparency.
Source and compatibility notes
Batch limits are based on the current local browser workflow and are set to reduce memory failures on typical devices.
Last checked: 2026-09-07
Notes
- Files are processed locally in the browser queue.
- Large batches depend on available browser memory.
- Downloaded ZIP files are created on the device.