Image Compressor & Converter
Drop your images here
Supports JPG, PNG, WebP.
We'll crush them locally. Unlimited size.
0 bytes
- Processed on this device
- 0 bytes
- Files opened here
- 0
- Requests carrying a file
- 0
About Bulk Image Compressor
Working through images one at a time stops being reasonable somewhere around the twentieth file. Preparing product photographs for a store, images for a website, or a folder of holiday pictures for sharing is fundamentally a batch job.
This is a bulk image compressor built for the whole set in one pass. Compress to a target size, resize to fixed dimensions, convert formats, and rename with a consistent pattern, applied across every file you add.
Because processing runs on your device rather than a server, there is no upload queue to wait through and no file count limit. Several hundred images is a normal batch. The work is spread across Web Workers so it uses more than one core, and the results come back as a single ZIP.
The comparison with server based batch tools is straightforward: those upload every original, process them remotely, then send everything back, which for a large folder of high resolution photographs is most of the total time. Here the images never make that trip.
How to use bulk image compressor
- Add the folder
Drop in as many images as you have. Mixed formats are fine.
- Set the rules
Choose a target size or quality, output dimensions, format and any renaming pattern.
- Process
Images are handled in parallel across Web Workers with progress shown.
- Download the ZIP
Everything comes back as one archive assembled in your browser.
Frequently asked questions
How many images can I process at once?
There is no imposed limit. Several hundred is routine; the practical ceiling is your device's memory rather than a plan.
Can I resize and compress in the same pass?
Yes, and it is the better order. Resizing first means compression has less data to work with, so hitting a target size costs less visible quality.
Can I rename files as part of the batch?
Yes. Apply a consistent pattern with sequential numbering, which is usually what a store or content system expects.
Is this faster than an online batch compressor?
For large batches, considerably. Server based tools spend most of the time uploading originals and downloading results. Here nothing is transferred, and processing runs across multiple cores on your own machine.