Batch JPG to WebP behavior
This page creates WebP copies from multiple JPG files with a shared quality and width setting.
It is useful when replacing several heavy JPG assets for a modern website.
Batch Convert JPG to WebP
Create WebP copies for a group of JPG photos without uploading the originals to a server.
Multiple JPG inputWebP outputQuality sliderBatch ZIP download
Batch JPG to WebP converter
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 to WebP converter
How it works
- 1Choose JPG files.
- 2Set WebP quality and an optional max width.
- 3Convert locally and download the WebP files.
Privacy and limits
- WebP export requires browser support.
- Animated sources export as a still frame.
- Metadata is not preserved by Canvas export.
Common use cases
- Preparing responsive website images
- Converting product photo sets
- Creating lighter blog media folders
Format notes
- WebP is broadly supported in modern browsers.
- Older upload forms may still require JPG.
- Animated sources are handled as still images.
Original test sample
- Convert ten JPG photos at WebP quality 82 and compare total bytes before ZIP download.
- Inspect detailed areas before replacing production assets.
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.