Batch PNG compression behavior
PNG files may not shrink much unless dimensions change or the output format changes to WebP or JPG.
The batch list shows which files benefit from the selected output settings.
Batch Compress PNG Online
Prepare a set of PNG screenshots, graphics or transparent assets with one local browser batch.
PNG batch inputWebP, JPG or PNG outputPer-file savingsLocal ZIP download
Batch PNG 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 PNG images. | |||||
Only need one PNG?Use the single PNG compressor
How it works
- 1Choose multiple PNG images.
- 2Pick output format, quality and optional width limit.
- 3Process the queue and download results.
Privacy and limits
- PNG quality behavior depends on the browser encoder.
- WebP or JPG output often reduces size more than PNG output.
- Transparent areas become white when exporting to JPG.
Common use cases
- Optimizing documentation screenshots
- Reducing transparent web graphics
- Preparing multiple UI captures
Format notes
- Use WebP for smaller transparent web assets when supported.
- Use JPG only when a white background is acceptable.
- Keep PNG when exact edges or transparency matter most.
Original test sample
- Convert several screenshots to WebP and compare text edges before publishing.
- For logos, check transparency before downloading the full ZIP.
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.