Batch compression behavior
This page applies one compression setup to a queue of images and reports file size changes for each result.
The queue runs in the browser, so selected files are not sent to an ImgShrink application server.
Batch Compress Images Online
Drop a set of images, apply one compression setup and download each result or a ZIP file. Processing stays in your browser.
Multiple image queuePer-file size savingsSingle and ZIP downloadsNo server upload
Batch image 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, PNG, WebP or AVIF images. | |||||
Only need one image?Use the single image compressor
How it works
- 1Choose or drop multiple images.
- 2Set quality, max width and output format for the whole queue.
- 3Process locally, then download individual files or a ZIP.
Privacy and limits
- Images stay in your browser and are not uploaded.
- You can process up to 20 images, 25 MB each and 200 MB total.
- Very large batches depend on browser memory, especially on mobile devices.
Common use cases
- Shrinking a folder of blog images
- Preparing several form uploads at once
- Creating smaller image sets before sharing
Format notes
- WebP is often the smallest output for mixed web images.
- JPG is useful for broad compatibility.
- PNG output may be larger but can help preserve crisp graphics.
Original test sample
- Try five mixed JPG and PNG files, then compare per-file savings before downloading the ZIP.
- If a batch is slow, reduce max width or split it into smaller groups.
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.