Two hundred files per batch
No counter, no trial limit, no license prompt after the first hundred. The ceiling is your device's memory, and we say so.
Drop a whole folder, set the quality once, download the lot as a ZIP. No signup, no file counter, no upload.
Drop your folder of images
JPG, PNG, WebP, AVIF, HEIC, GIF, BMP, TIFF · up to 200 files · 100 MB each
Compressing images one at a time is the actual problem here. The work is not hard, it is repetitive: open a file, pick a quality, save, repeat eighty times. This page collapses that into a single pass. Drop everything, choose the quality once, and every file is re-encoded with the same setting and handed back as one ZIP.
The queue is per-file even though the setting is shared. Each row shows its original size, its new size and whether it succeeded, so an image that was already well compressed is visible as a small saving rather than being averaged away. If one file in two hundred is corrupt, that row fails with a reason and the rest of the run continues.
What actually limits a batch is your device, not a plan. Files are processed one after another so the WebAssembly encoder never holds more than one image at a time, but the queue does keep each source file and its compressed result in memory until you download. Two hundred is comfortable on a laptop and ambitious on an old phone. If a very large batch slows to a crawl, split it in half and run it twice.
No counter, no trial limit, no license prompt after the first hundred. The ceiling is your device's memory, and we say so.
One quality, format and metadata choice applied across the whole queue. Mixed formats in the same batch are fine.
Download the finished batch as a single archive, or grab individual files from the queue when you only need a few.
Moving a site and inheriting years of unoptimized uploads. Compress the whole media folder before it goes anywhere near the new host.
Dozens or hundreds of product shots at identical settings, so the grid loads evenly instead of one image at a time.
Export the library, compress the batch here, re-upload. No plugin, no server load, no per-image credits.
A shoot folder that is too heavy to email or share. Drop the quality a step and the whole set becomes sendable.
Email clients punish heavy images. Run every asset for the send through one pass at the same setting.
Texture and sprite folders where bundle size matters. Convert and compress the batch in one go.
Select up to 200 files or drag a folder straight in. Nothing is uploaded — the whole run happens on your device.
Pick a quality for the batch, or an output format if you want everything converted on the way through.
Watch the totals as the queue runs, then take the whole set as one archive when it finishes.
Quality 75 to 80 is the sweet spot for photographs. Most people cannot see the difference, and the size drop is substantial.
Check the aggregate total before downloading. If the batch barely shrank, the folder was already optimized and there is nothing to win.
Mixed formats are fine in one batch. Leave the output on source to keep each file's format, or pick one format to convert everything.
If a very large batch stalls, split it. Memory is the real limit, and two runs of a hundred behave better than one of four hundred on a modest device.
Need every file under an exact size like 100 KB rather than a shared quality? That is a different job — use the KB-target tool.
The single-image compressor with the same engine and controls.
Resize a whole folder to the same dimensions and download as a ZIP.
WebP-specific compression with a lossy or lossless choice.
Make a single image smaller when you do not need the batch queue.
Hit an exact file size target instead of sharing one quality setting.
Two hundred images, one setting, one archive. Free, and nothing leaves your device.