About this tool
Compressing an image means two things: lowering the quality setting so the encoder discards detail the eye cannot see, and reducing the pixel dimensions so there is less to store. Doing both turns a 6 MB phone photo into a 200 KB file that still looks sharp on any screen.
This tool does both in your browser. Set a maximum size, such as 1920 px for web or 1280 px for email attachments, and a quality around 75. The photo is decoded directly at the smaller size, encoded once, and offered for download. For the smallest result choose WebP; choose JPEG when the recipient's software may not support WebP.
Nothing is uploaded, so compressing a hundred vacation photos costs you nothing but a few seconds of CPU time, and no copy of them exists anywhere else.
How it works
- Drop the photos you want to shrink.
- Set a maximum size (1920 px for web, 1280 px for email) and quality around 75.
- Pick JPEG for compatibility or WebP for the smallest files, then Save.
Looking for a different conversion? Try PNG to WebP, JPG to WebP, WebP to PNG, Compress image or DOCX to PDF.
Frequently asked questions
- How do I compress a photo for email?
- Set the maximum size to 1280 px and quality to 75 with JPEG output. A typical phone photo drops from 4–8 MB to 150–300 KB, well under any attachment limit.
- Compress or resize: which reduces size more?
- Resizing usually wins. Halving the dimensions cuts pixels by 75 %. Lowering quality from 95 to 75 cuts another 50–70 %. Use both for the smallest files.
- Can I compress a PNG without losing transparency?
- Yes. Choose WebP output, which keeps the alpha channel while compressing far better than PNG.
- Which quality setting should I use?
- 80 is the sweet spot for photos: file size drops by 60–90 % compared with PNG and the difference is invisible at normal viewing sizes. Use 90–95 for print or archival copies, and 60–70 for thumbnails and previews.
- Are my images uploaded to a server?
- No. Decoding, resizing and encoding happen inside your browser using a background worker. The file is read from your device, converted locally, and the result is saved from your browser's memory. Nothing is transmitted.