How to Batch Compress Images Online Free — All Formats at Once
· 5 min read
To compress many images at once, add the whole selection rather than one file at a time, set the quality once, and download the results as a single ZIP. The saving per image is identical whether you do one or a hundred — what changes is your time. Everything runs in your browser, so nothing is uploaded.
Compressing images one at a time is fine for one image. For forty product photos it is an afternoon. Here is how to do the whole folder at once, in your browser, without uploading any of it.
On this page
Why batch matters more than the compression itself
The saving on any single image is the same whether you do one or a hundred. What changes is your time. Most people give up on optimising images not because the tools are bad but because the loop of open, upload, wait, download, repeat is unbearable past about the fifth file.
Doing it in the browser removes the two slowest steps. There is no upload and no download queue — the files are already on your device, and the results land straight back there.
How to compress a whole folder at once
Open Compress Image, then drag the entire selection in at once rather than one at a time. Every file appears in a list with its own size. Set the quality once and it applies to all of them.
Quality 75 is the right starting point for photographs. Screenshots and flat-colour graphics survive lower settings; images with fine gradients or text want higher. If you are unsure, run one file first, look at it, then do the rest with the setting you settled on.
- Photographs: 70–80 is usually indistinguishable from the original
- Screenshots and UI captures: keep PNG, or use 85+ if converting
- Images with text: 85+, or the text edges start to smear
What to expect from the numbers
A typical camera JPEG drops 60–80% at quality 75. A PNG screenshot converted to WebP often halves. Images that were already run through an optimiser will save much less, because the redundancy has already gone — that is not the tool failing, it is the file already being efficient.
Anything that would come out larger is handed back untouched, so a batch can only ever shrink.
| Source | Typical saving | Why |
|---|---|---|
| Camera JPEG | 60–80% | Phones export at a generous quality setting |
| PNG screenshot converted to WebP | 40–60% | Flat colour compresses extremely well |
| PNG photo converted to WebP | 80–90% | PNG is the wrong format for photographs |
| Already-optimised JPEG | 0–15% | The redundancy has already been removed |
Sorting the batch before you run it
One quality setting applies to every file, which is what makes batching fast and also what makes a mixed folder come out uneven. Photographs and screenshots want different settings, and a value that suits both does not exist.
Splitting the folder in two takes a minute and is the difference between a consistent set and one where the screenshots have smeared text. Photographs in one pass at 75, anything with text or flat colour in another at 85 or as lossless WebP.
Why the browser is faster than a server for this
A server-based batch has to upload every file, wait in a queue, and download every result. On a home connection the upload alone dominates: a hundred 4 MB photos is 400 MB going out, which takes several minutes before any work begins.
Processing locally skips both transfers entirely. The files are already on the device, and the results are written back to it — so the only time spent is the compression itself, which runs across your processor cores.
Batching on a phone
It works, with one caveat: memory. Each image has to be decoded into raw pixels to be re-encoded, and a 12-megapixel photo occupies roughly 48 MB decoded regardless of how small the file is.
That is why a phone handles a hundred small images comfortably and struggles with fifty large ones. If a large batch stalls, split it into groups of twenty rather than assuming the tool has failed.
Common questions
How many images can I compress at once?
FileCrisp sets no hard limit on batch size. The practical ceiling is your device RAM. Most modern computers handle 100–200 images per batch without issues. For very large batches, process in smaller groups of 50–100 files.
Can I batch compress different image formats together?
Yes. FileCrisp handles PNG, JPEG, and WebP in the same batch. You can also choose to convert all output to WebP format for maximum savings, regardless of the input format.
Will all my images have the same quality setting?
Yes — one quality setting applies to the whole batch. If you need different settings for different images (e.g., 90% for hero photos, 70% for thumbnails), process them in separate batches.
Does batch compression upload my files?
Never. FileCrisp runs entirely in your browser. Your images are processed locally and never sent to any server. This also means batch compression is fast — no upload time, no server queue.
What format are the output files?
By default, the output format matches the input format (PNG → PNG, JPEG → JPEG). You can optionally convert everything to WebP for the smallest possible output.
Can I batch compress images on mobile?
Yes, in any modern mobile browser. The limit is memory rather than speed: every image is decoded to raw pixels to be re-encoded, so large photos are far more demanding than their file size suggests. Split a stalling batch into groups of twenty.
Should I sort my images before batching them?
Yes, if the folder mixes photographs with screenshots or graphics. One setting applies to everything, and a value that suits a photograph will smear text. Two passes at different settings takes a minute and looks far better.
Why did some images barely shrink?
They were already optimised, so the redundancy had been removed before you started. That is the file being efficient rather than the tool failing — and anything that would come out larger is returned untouched.