Bulk Image to WebP Converter
Convert batches of images to optimized WebP files in your browser. No uploads, no server storage, and no signup.
Your images are processed in your browser and never uploaded to our servers.
Target size per image
Compression mode
Filename format
Drop images here
or click to browse — JPG, PNG, WebP
Your images are processed locally in your browser and never uploaded.
How to Convert Images to WebP in Bulk
- Choose or drop your jpg, png, webp image file.
- Use the prefilled 100KB target and adjust compression mode if needed.
- Review the compressed size, quality, and output dimensions in your browser.
- Download the WebP file when the result is within the selected target.
What Bulk WebP Conversion Changes
100KB is the single most common image size limit on the internet. It appears in upload forms, content guidelines, performance budgets, and platform specifications more often than any other round number, which makes it the default target most people are looking for.
The budget is generous enough for real quality. A photograph at 1200×800 to 1600×1000 pixels typically fits at a quality level where compression is not visible in normal use, and graphics or screenshots can go considerably larger because flat colour costs very little to encode.
Bulk WebP conversion is useful for preparing website images, product catalogs, image libraries, and blog assets.
Converting a Whole Image Library to WebP
Batch conversion is usually part of a migration rather than a one-off task: an existing site, catalogue, or asset library needs to move from JPG and PNG to WebP. That context changes what matters. You need to know what happened to every file, not just that the batch finished, which is why the tool produces a CSV report of the original and final size of each image.
Keep your source files after converting. WebP output is a delivery format, and if you later need different dimensions, a different quality level, or a format some legacy system demands, you want to regenerate from the originals rather than from an already-compressed copy.
What Each Format Gains in a Batch
| Source image | What to expect |
|---|---|
| Folder of JPG product photos | 25–35% smaller each, as WebP |
| Folder of PNG screenshots | Often 70–90% smaller; the largest batch win |
| Mixed JPG and PNG library | Both converted; PNG files show the bigger drop |
| Files already in WebP | Re-encoded only if a smaller target is set |
Who Converts Libraries to WebP
Whole-library WebP migration
Converting an entire asset library in one pass is the usual path when a site adopts WebP, and it needs a record of what happened to each file.
Build and deploy pipelines
Teams preparing a static site or theme release often convert assets in bulk as a pre-deploy step rather than one at a time.
Agency asset handover
Delivering a client's image set in a modern format is a straightforward improvement that does not require touching their site's code.
How Each Input Format Behaves
This page accepts JPG, JPEG, PNG, and WebP inputs, which covers essentially every image you are likely to encounter outside of specialist workflows. Each behaves a little differently under compression, and the tool adapts to what you give it.
Output is always WebP. That choice is deliberate: WebP reaches a given target size at higher visual quality than JPG or PNG can, which means the file you download looks better than the equivalent-sized file in an older format would.
Upload multiple JPG, JPEG, PNG, or WebP images. Downloads are WebP files.
JPG sources are already lossy
A JPG has been compressed once already. Converting it to WebP is a second lossy pass, so always start from the highest-quality version you have.
PNG sources compress dramatically
PNG is lossless and therefore large. Converting a PNG to WebP frequently produces the biggest reduction you will see, especially for screenshots and graphics.
WebP sources have less to give
An existing WebP is already efficiently encoded, so reaching a much smaller target usually requires reducing dimensions rather than quality alone.
Recommended Settings for Batch Conversion
Balanced mode with resize at around 1600px wide is the general-purpose answer. For images that will be displayed small, drop the resize width and you will land far below 100KB with excellent quality — there is no benefit to using the whole budget if you do not need it.
If a batch contains large photos, enable resize before compression to improve success rates and keep quality consistent.
What Goes Wrong in Batch Conversion
No record of what changed
Without a per-file report, a failed or badly-compressed conversion in a large batch is easy to miss until it is live.
Source files discarded too early
Regenerating at different dimensions later requires the originals. WebP output is a delivery format, not an archive.
Legacy consumers break
If any downstream system reads the folder directly and does not support WebP, converting in place will break it.
Other Image Size Compressors
Same-size pages
FAQs
Can I convert multiple images to WebP at once?▼
Yes. Upload up to 20 images and convert successful files to WebP in one batch.
Are bulk images uploaded?▼
No. Bulk processing runs in your browser, so image files stay on your device.
Can I choose 50KB or 100KB output targets?▼
Yes. The bulk tool includes target-size controls for common WebP output limits.
What happens if one image cannot compress enough?▼
That image is marked as failed, while successful files remain available for ZIP download.