Bulk Image Compressor

Yes, though your browser does the work sequentially, one file at a time in a web worker. Keep the tab in the foreground while it grinds through, and if the gallery is enormous, split it into runs of around 100 files so ZIP assembly stays comfortable in memory.

The target max size applies per file, not to the batch total. Setting 1 MB means each photo is squeezed until it fits under roughly 1 MB, so a 200-file run aims for about 200 MB overall. Small files already under the target are barely touched.

With the format control left on original, each file keeps its own type and just gets recompressed. Choosing WEBP or JPG instead normalizes the whole batch to that format, which is usually what you want when the outputs feed one website.

Not here. The compression library runs entirely in your browser using a web worker, so the files never leave your device. That matters when the batch is client work you're not allowed to push through third-party servers.

Every processed file is renamed, for example compressed-IMG_2048.webp, so nothing can silently overwrite an original when you extract the ZIP into the same folder. The extension also updates to match whichever export format you selected.

Yes. Images are capped at 4096 px on the longest side during compression, so a 8000 px panorama will come out smaller in pixels as well as bytes. For most web galleries that ceiling is generous; for print masters, compress copies rather than originals.

Always. Drop a single representative image first, since one file downloads directly and shows you the result in seconds. Once the quality preset and target size look right on that sample, load the remaining files and reuse the exact same settings.