Less weight, same photo
Compress images
Cut the weight of your photos and see the saving file by file. Choose a quality level or set the exact size you need.
100% private. Your images are processed inside your own device and are never uploaded to any server. You can go offline after the page loads and the tool will keep working.
Up to 30 images per batch and about 60 MB per file. If an image does not get smaller, we hand back the original.
How it works
Drop the images
Up to 30 at once. They run one after another with their own progress bar.
Quality or target size
“By quality” for a fixed level; “By file size” to land under 200 KB, 500 KB or whatever you need.
See the saving and download
Every row shows before, after and the percentage saved.
What compressing an image really means
Compressing an image is deciding what information can be thrown away without the eye noticing. JPG and WebP work by grouping areas of similar colour and simplifying the detail human vision is least sensitive to. The more aggressive that simplification, the lighter the file and the more the image degrades. The trick is not to compress as hard as possible, but to find the point just before it shows.
The two modes in this tool
By quality is the default: you set a level (75 is an excellent value for almost anything) and every image slims down as much as it can at that level. This is what you want when the point is that all your photos look equally good.
By file size solves a very specific problem: “this photo has to be under 200 KB because the form will not take more”. The tool tries several quality levels until it lands just under your target. It is the mode for CVs, applications, profile pictures and property listings.
Where the savings actually come from
Plenty of people crush the quality of a 4032 × 3024 pixel photo to publish it in a space 800 pixels wide. They are throwing away quality where it shows and keeping pixels nobody will ever see. In almost every case, reducing pixel dimensions saves far more than squeezing quality, with no visible effect.
That is why the “Maximum size” selector sits right next to the quality slider. A quick guide:
| Destination | Longest side | Quality | Typical size |
|---|---|---|---|
| Email attachment | 1920 px | 75 | 200–400 KB |
| Article image | 1280 px | 75 | 120–250 KB |
| Product photo | 1600 px | 82 | 250–450 KB |
| Profile picture | 800 px | 80 | 60–120 KB |
| A4 print | Keep as is | 92 | 2–5 MB |
What a compressor cannot do
A PNG with many colours (a photograph saved as PNG) barely shrinks if you keep it as PNG: lossless compression has a floor. The answer is to convert it to JPG or WebP, which is why this tool lets you change the output format. And if a file was already heavily compressed, it may not shrink at all: in that case we hand you back the original and say so, rather than giving you a worse file of the same size.
Frequently asked questions
Can I compress an image without losing quality?
With no loss whatsoever, only using lossless formats like PNG or lossless WebP, and the saving is small. What you can do is compress with no visible loss: at quality 80–85, and resized to the dimensions you will actually use, you typically save 60% to 90% of the weight without anyone spotting the difference.
How do I get a photo under exactly 200 KB?
Switch to “By file size” mode and choose 200 KB. The tool works through quality levels until it lands under that ceiling. If it still cannot get there, also drop the maximum size to 1280 px: that is almost always where the excess is.
Can I see the before and after?
Yes. Each file shows its original size struck through, the final size and the percentage saved. A summary for the whole batch appears underneath.
Why did one image come out bigger than the original?
It usually happens when converting a JPG photo to PNG, or when compressing something that was already heavily compressed. When we detect the result is no better than the original, we hand back the original and flag it, so you never leave with a worse file.
Is EXIF and location data preserved?
No. Re-compressing writes a new file with no metadata. That is good for privacy, but if you need the capture date, keep the originals too.
Are there file or size limits?
Up to 30 images per batch and about 60 MB per file (50 MB for HEIC). The limit comes from browser memory, not from us: beyond that the tab would close on its own.