Phone cameras now save 3–8 MB pictures by default. Mailboxes bounce them, contact forms reject them, and a homepage full of them fails the speed test Google actually uses. This image compressor is built for that job: batch, drag-and-drop, paste, a quality slider, a target size, and a resize box.
Unlike upload tools, the photo never crosses the network. MozJPEG, WebP, AVIF, PNG and GIF encoders run here as WebAssembly. You can work offline after the first load. There is no account and no file-size cap imposed by us; the only limit is the memory of the browser you are using.
How to compress an image
Add the photos
Drop them on the panel, click to browse, or paste from the clipboard. Add as many as you need. Mixed JPEG, PNG, WebP, AVIF and GIF files are fine in one batch.
Choose quality, size or pixels
Leave quality at 80 for a web photo, or pick a target such as 100 KB. Set a max width if the picture is also too wide. Change the output format when you want WebP or AVIF instead of JPEG.
Compare and download
Drag the comparison control to see the original against the result. Download one file or a ZIP of the whole batch. The original stays on your device.
Why compress before you publish
Pages get faster
Images are usually most of a page’s weight. A photo that drops from 4 MB to 250 KB improves Largest Contentful Paint on slow phones, which is the loading signal Google measures in the field.
Attachments go through
Many mail hosts still choke near 10–25 MB. A batch of holiday pictures fits again once each file is under a few hundred kilobytes.
Private by design
Upload compressors keep a copy, often for hours. Here the pixels are decoded and encoded in the tab. EXIF, including GPS, is dropped because the picture is redrawn.
You stay in control
Automatic compressors hide the quality setting. The slider and the target-size mode let you decide whether a product photo needs 90 or a chat thumbnail can live at 60.
What an image compressor changes
A photo compressor throws away detail people rarely see, or packs the same pixels more tightly. JPEG and WebP do the first. A high-quality PNG stays lossless and only gets smaller when the encoder is careful, or when you allow fewer colors.
AVIF usually wins on size at the same visual quality, with slower encoding. GIF is for short animations and simple graphics; a photograph should not stay a GIF. Start with the original, export once, and avoid re-saving a JPEG again and again.
Quality, target size and resize
Quality 80 is the default because it is the point where most photographs still look clean and the file has already fallen by half or more. Go higher for a portfolio crop. Go lower for a preview.
Target size searches for the highest quality that lands under the limit. If the picture cannot reach it, you get the smallest successful encode and a note that says so. Resize is separate: a 4000-pixel photo displayed at 800 pixels should be 800 pixels wide, not merely a heavy file with a low quality number.
Which output to pick
| Output | Best for | Suggested quality |
|---|---|---|
| JPEG | Photographs, email, older sites | 75–85 |
| WebP | Modern pages that need smaller photos | 75–85 |
| AVIF | Smallest photographs when encode time is fine | 50–70 |
| PNG | Logos, screenshots, transparency | 100, or lower to limit colors |
| GIF | Short animations and flat graphics | Use fewer colors |
Image compressor questions
Does this image compressor upload my photo?
No. Compression runs in your browser with WebAssembly codecs. The photo is not sent to PhotoCompressor, and there is no account to store it.
What is a photo compressor used for?
A photo compressor shrinks a picture so email, forms, shops and web pages accept it and load it faster. The goal is a smaller file that still looks right at the size you display.
Which quality should I use?
Start at 80 for JPEG or WebP photographs. Use 90 or more when you need a cleaner crop, and a target size when a form asks for a maximum weight such as 100 KB.
Can I compress more than one image?
Yes. Drop a batch, paste extra images, and download them one by one or as a ZIP. We do not cap the count or the file size; a very large photo may need a smaller max width if the browser runs out of memory.
Will GPS and camera data stay in the file?
No. The image is drawn onto a canvas before encoding, so EXIF, GPS and camera metadata are removed. That is useful before you post a photo publicly.
Does it work offline?
After the first visit the app shell and codecs can be cached as a progressive web app. You can then compress without a connection. Analytics and ads need the network; the compressor does not.