Compress a whole batch of images in your browser with one quality slider, then download them individually or as a single ZIP.
Content last reviewed
Drop images or click to upload
Batch compress JPG, PNG, WebP in your browser
Add a whole batch at once — drag and drop or click to pick files.
One global slider controls the batch; 70–85% is the practical sweet spot for photos.
Grab a single compressed file directly, or the whole batch as one ZIP.
Representative behaviour for camera photos at the default quality — exact savings vary with content.
Input
12 JPG photos totalling 38 MB · Quality 70%Output
Each file re-encoded with its new size in the table; totals typically report well over half the batch size saved, downloadable as compressed-images.zipImage files are almost always heavier than they need to be: a phone photo weighs 4–8 MB, while the version a website, upload form, or email actually needs looks identical at a fraction of that. This compressor handles the realistic case — not one image but a folder of them: drop in the batch, set one quality slider, and watch each file re-encode with its new size reported live.
The compression is the lossy kind that makes photos small. The encoder discards detail your eye barely registers, and the quality slider (10–100%) decides how aggressively. For photos, 70–85% typically cuts file size by well over half before a side-by-side comparison reveals any difference; below about 60%, smudged detail and blocky gradients start appearing in skies and skin. The table shows each file's original and compressed size with a thumbnail, plus running totals for the whole batch, and changing the slider re-processes everything automatically.
Two behaviours worth knowing. PNG files are re-encoded as JPEG — that is what makes them dramatically smaller, but it also means transparency is lost, so keep graphics that need an alpha channel out of this tool (the HEIC & Image Converter gives format-level control instead). And everything runs client-side: no upload queue, no server touching your photos, whether it is three screenshots or forty product shots. When a file is still too heavy after compression, its pixel dimensions are usually the real problem — resize first in the Image Resizer, then compress.
Drag images onto the drop zone or click it to select files — JPG, PNG, and WebP, as many as you need.
Adjust the Global Quality slider (10–100%, default 70). Every file in the batch re-compresses automatically when it changes.
Review the table: each row shows a thumbnail, the original size, and the new size as it finishes. Remove any file with its trash icon.
Check the sidebar totals — original size, compressed size, and total percentage saved.
Click Download All: a single file downloads directly; multiple files arrive as one compressed-images.zip.
Add any number of images at once; they process sequentially with progressive results in the table.
10–100% in five-point steps — change it and the entire batch re-encodes automatically.
Original size, new size, and thumbnail per file, plus batch totals and overall percentage saved.
Multiple results are packaged into one compressed-images.zip; single results download directly.
Compression runs on your device via the canvas API — no upload, no queue, no server.
Shrink gallery and article images so pages load faster and score better on Core Web Vitals.
Get photos under a form's or email's file-size cap without visible quality loss.
Compress a whole shoot's worth of product images in one pass before publishing.
Reduce a folder of oversized photos to practical sizes for archiving or sharing.
Each image is decoded, drawn onto a canvas at its original pixel dimensions, and re-encoded through the browser's own encoder at your chosen quality. Nothing is resized — only the encoding changes, which is why the pixel content stays identical while the byte size drops.
The quality value maps to the encoder's quantization aggressiveness: lower values discard more high-frequency detail (fine texture first, then visible structure). PNG inputs are re-encoded as JPEG, trading their lossless-but-large encoding for a lossy-but-small one; other formats keep their own type. Files process one at a time to keep the page responsive, results appearing progressively, and the batch is zipped in the browser when you download multiple files.
Standard web image formats via drag-and-drop or the file picker. PNG files are re-encoded as JPEG for compression, so transparency is not preserved.
Multiple compressed files download as one compressed-images.zip; single files download directly.
One slider (10–100%, step 5) applied to the whole batch; changing it re-processes every file.
Drop any image from the batch with its trash button before downloading.
PNGs are re-encoded as JPEG, which has no alpha channel, so transparent regions are flattened. Keep transparency-dependent graphics out of this tool — convert them deliberately in the HEIC & Image Converter instead.
It was probably already well compressed — re-encoding an optimized JPEG yields little. If the file is still huge, its pixel dimensions are the real weight; resize it first, then compress.
Files decode and re-encode in your browser's memory one at a time. Dozens of photos are fine; hundreds of very large ones may take a while — let the table fill progressively.
Compression re-encodes at original pixel dimensions — there is no resizing here, so a 6,000-pixel photo stays 6,000 pixels (use the Image Resizer for that, ideally first). PNG inputs become JPEG, losing transparency and the lossless guarantee; there is no per-file format choice or option to keep PNG as PNG — the HEIC & Image Converter covers that need. Quality is global for the batch rather than per file. Processing happens in browser memory, so extremely large batches are bound by your device.
Your images never leave your device: decoding, compression, and even the ZIP packaging run in your browser. Nothing is uploaded, stored, or seen by anyone — which is exactly what you want for personal photos, documents, and client work.
Resize to display dimensions first, then compress — dimensions save more bytes than quality tweaking alone.
Stay in the 70–85% range for photos; drop lower only when a hard file-size cap forces it.
Keep transparency-dependent PNGs out of this tool, since output is JPEG-encoded.
Check results at 100% zoom before publishing — artifacts hide at thumbnail size.
Always compress from originals; never re-compress an already compressed file.
Work the two levers in order. Dimensions come first: an image destined for an 800-pixel slot should be 800 (or 1,600 for retina) pixels wide before quality even enters the conversation — halving both dimensions removes three-quarters of the pixels. Then compression: at correct dimensions, 70–85% quality typically lands photos at a fraction of their original weight with no visible cost.
Batch deliberately: group images with similar content (photos vs. screenshots) since they tolerate different quality levels, and set the slider for the most demanding image in the group.
Keep the originals somewhere safe. Lossy compression is a one-way door — the discarded detail never comes back — so the master files are what you return to when a new size or crop is needed later.
Each file is loaded into an Image element, drawn to an off-screen canvas at native resolution, and re-encoded via canvas.toBlob at quality/100. PNG sources are encoded to image/jpeg; other sources keep their MIME type. Files process sequentially with progressive state updates, and quality changes re-trigger the whole batch. Batch downloads are assembled with JSZip in the browser. All object URLs and processing stay local.
Site owners and bloggers preparing galleries, sellers batch-processing product shots, and anyone whose upload form says "max 2 MB" while their camera says otherwise. It optimizes for the many-files case; for single-image format control (or preserving PNG transparency), the HEIC & Image Converter is the right neighbour.
70–85% for photos — most content shrinks by half or more before differences become visible side by side. Screenshots tolerate lower values. For a hard size cap, start at 80% and step down until it fits, and resize dimensions if you hit ~60% without success.
They are re-encoded as JPEG, which is what produces the large savings — but JPEG has no transparency, so alpha regions are flattened. For PNGs that must stay PNG, use the HEIC & Image Converter, which lets you choose the output format explicitly.
Either it was already compressed (re-encoding an optimized JPEG yields little), or its true weight is pixel count rather than encoding. A 6000×4000 photo at quality 80 is still large — resize it to its display size first, then compress.
No — compression re-encodes the same pixels more efficiently, resizing reduces how many pixels there are. They multiply: resized to the right dimensions and compressed at 80%, a web image is routinely over 90% smaller than the camera original. This tool does the compression half.
Not here — the slider is global for the batch. Process files needing different treatment in separate batches, or use the HEIC & Image Converter, which supports per-file quality.