Compress images
Make JPG, PNG, WebP and AVIF files smaller, or convert them to another format, without uploading anything. The encoders run inside this page, so your photos stay on your device.
Loading the tool…
Files are processed on this device and never uploaded.How to check
Compress or convert, on your own device
This tool re-encodes images with the same open-source encoders that power Google’s Squoosh: MozJPEG for JPG, libwebp for WebP, libavif for AVIF and oxipng for PNG. They are compiled to WebAssembly and run in a background worker inside this tab, so the page stays responsive while a batch is processing and no file is ever sent over the network.
With Keep original format selected, each file is compressed in its own format. A JPG stays a JPG, a PNG stays a PNG. Choose a format from the list to convert the whole batch instead.
Which format to pick
- JPG works everywhere and is the safe choice for photos you email or upload to other services. It has no transparency.
- PNG is lossless: every pixel is kept exactly. It suits screenshots, diagrams and logos, but it is a poor fit for photos, which come out several times larger than a JPG.
- WebP is usually 25–35% smaller than a JPG of similar quality and supports transparency. Every current browser displays it, though some older desktop software does not.
- AVIF usually gives the smallest files, often around half the size of a comparable JPG. Encoding is slower, so a large batch takes a while. Chrome, Edge, Firefox and Safari 16 or newer can display it.
How much smaller will my files get?
It depends on the source. Photos straight from a phone or camera are often saved at a very high quality and shrink a lot, sometimes by 60–80% at quality 75. Images that were already optimized for the web may barely change. PNG compression is lossless, so typical savings there are smaller, around 10–40%. Each result shows the before and after size, so you can compare before you download.
If you only need smaller files for a website, combining a moderate quality setting with a maximum width (1600 or 2000 pixels covers most layouts) usually saves more than lowering the quality alone.
Frequently asked questions
Are my images uploaded anywhere?
No. Decoding, resizing and encoding happen in your browser with WebAssembly versions of MozJPEG, libwebp, libavif and oxipng. The page only downloads the encoders from this site; it never sends your files to a server.
What quality setting should I use?
75 is a good default for photos on the web: most people cannot tell it apart from the original at normal viewing size. Go up to 85 or 90 for images you plan to print or edit again, and down to 60 for thumbnails. PNG ignores the slider because it is always lossless.
Why did a file get bigger?
An image that was already compressed well can come out larger when it is encoded again, especially at a high quality setting. When that happens and the format did not change, the tool tells you and offers the original file instead, and the .zip uses the original too.
Does compressing remove the photo's metadata?
Yes. The new files do not carry EXIF data such as GPS location, camera model or date. The picture is rotated upright first, so photos taken sideways still display correctly. Embedded color profiles are not kept either, so wide-gamut photos can look slightly less saturated.
Can I make the images smaller in pixels too?
Yes. Enter a maximum width, a maximum height or both. Larger images are scaled down to fit while keeping their proportions; smaller ones are left at their original size, never enlarged.