What this compressor does
This page compresses images directly in your browser. You pick the files, choose whether you want the smallest possible file or a specific target size, and the compressor re-encodes each image on your own device. Nothing is sent to a server, and there is no account to create.
Most people arrive here with one of three problems: a photo that is too large to attach to an email, a screenshot that has to fit under an upload limit, or a folder of product shots that loads too slowly on a website. All three are the same job: make the file smaller without making the picture useless.
How to compress an image
- Add your images. Click Choose images or drag files onto the box. You can add up to 20 images at once, and each one can be up to 20 MB. JPG, PNG, WebP and HEIC files are accepted.
- Choose a target. Leave it on Automatic when you want the smallest file that still looks clean. Pick Under 100 KB, Under 200 KB, Under 500 KB or Under 1 MB when a form or a platform gives you a hard limit, or type your own size.
- Compress and download. Press Compress images. Each row shows the original size, the new size and the percentage you saved. Download the images one by one, or press Download all as ZIP to get the whole batch in one file.
What the result looks like
Every finished file gets a row with the two numbers that matter: what the image weighed before and what it weighs now. A photo that started at 4.2 MB and came out at 780 KB is shown as 4.2 MB → 780 KB with a −81% marker next to it. If you asked for a target size and the compressor could not reach it without destroying the picture, the row says so instead of pretending the job is done.
The original file is never modified. The download is a new file with -compressed added to its name, so you can compare the two side by side and keep the one you prefer.
Compressing to a target size
Size limits are the reason most people search for a compressor. A 100 KB limit on a job application form, a 200 KB limit on a passport portal, a 2 MB limit on a marketplace listing — the number is arbitrary, but the form will reject anything larger.
When you choose a target, the compressor does not simply squash the image once and hope. It re-encodes the file, checks the result against your limit, and tries again with a different quality and, if needed, a smaller pixel size, until the file fits or the options run out. Quality is spent before pixels are, because a sharp image at a lower quality setting usually looks better than a blurry one that kept every pixel.
Two honest limits: a PNG is a lossless format, so its savings usually come from reducing dimensions rather than from re-encoding, and a photo cannot be squeezed into 10 KB without visible damage. For very small targets, converting to JPG gives you more room.
Why the images never leave your device
Every step — reading the file, redrawing it on a canvas, encoding the new version — happens inside your browser tab using JavaScript and WebAssembly. There is no upload endpoint. There is no storage bucket. There is no queue where your holiday photos wait to be processed.
That matters for more than privacy. It also means there is no waiting for a server to accept a 15 MB file over a slow hotel Wi-Fi, no daily quota, and no “your files are deleted after one hour” promise to take on trust. Close the tab and the files are gone, because they were never anywhere else.
The site still needs to load its own code — the fonts and the compression libraries come from public CDNs — but your images are never part of any request.
Supported formats
| Format | What happens |
|---|---|
| JPG / JPEG | Re-encoded at a lower quality, and resized if the picture is larger than 4096 pixels on its longest side |
| PNG | Kept as PNG; savings come from re-encoding and from reducing dimensions when you set a target size |
| WebP | Re-encoded as WebP, which is usually smaller than JPG at the same visual quality |
| HEIC / HEIF | Converted to JPG first, because most browsers cannot display HEIC; this is the format iPhone cameras produce by default |
The 4096-pixel ceiling exists because mobile browsers cannot reliably draw larger images on a canvas. Shrinking first avoids the blank or black output that some compressors produce on very large photos.
Good to know before you start
- You can run as many batches as you like. The limit is 20 images per batch, not 20 images per day.
- Very large batches use a lot of memory. If a batch stalls on an older phone, split it into smaller groups.
- The download button appears as soon as a file is ready, so you can start saving while the rest of the batch is still being processed.
- The ZIP file is built in your browser too; it is not assembled on a server.
- If a file is rejected, the message under the buttons tells you why — usually it is larger than 20 MB or it is not an image.
Frequently asked questions
Is this compressor really free?
Yes. There is no account, no watermark, no per-day limit and no paid tier. You can compress 20 images per batch, each up to 20 MB, as many times as you need.
Are my images uploaded to a server?
No. The compression runs inside your browser tab. Your files are never sent anywhere, which is also why there is no upload progress bar to wait for.
How much smaller will my image get?
It depends on the file. A photo straight from a camera usually has a lot of room to shrink, while a file that was already compressed has very little. The percentage shown next to each file is the real result for that file, not an average.
Can it compress an image to exactly 100 KB?
It aims for the limit and reports the closest size it reached. If the picture cannot fit without visible damage, the row tells you that instead of silently delivering a file that still breaks the limit.
Does it work with iPhone photos?
Yes. HEIC and HEIF files are converted to JPG in your browser before compression, so you can use the results anywhere that expects a normal photo file.
Will compressing ruin the quality?
Automatic mode is tuned to keep the picture clean. Target-size mode will trade detail for size, because that is what a hard limit requires. Keep the original file until you have checked the result.
Does it work on a phone?
Yes, on modern iOS and Android browsers. Processing happens on the device, so a very large batch will be slower on an older phone than on a laptop.
Do I need to install anything?
No. There is nothing to download or install, and no browser extension is required.