Password Generator
Make a strong random password in seconds. Pick the length and the characters you want, then copy it.
Open tool →Shrink your photos in seconds, without uploading them anywhere.
Last updated: 17 November 2026.
This compressor is private and browser-based: your photos stay on your device, nothing is uploaded, and everything runs in your browser.
Photos from a modern phone are often several megabytes each, which is far larger than most websites and email services need. A single photo can be 4 or 5 megabytes, so ten photos can pass 40 megabytes, and that slows down uploads, eats mobile data, and fills storage fast. Compression shrinks the file so it is quicker to send, easier to store, and faster to load on a web page, while the picture still looks good to the eye.
There are two kinds of compression. Lossy compression, used by JPEG and WebP, throws away some image data and cannot get it back. The quality slider controls how much is thrown away: a lower number means a smaller file and a softer picture, while a higher number keeps more detail and a larger file. Lossless compression, used by PNG, keeps every pixel exactly, so the file can only shrink by storing the same pixels in a smarter way.
The tool above draws your image onto a canvas in the browser and then saves it again at the quality you picked. Nothing is uploaded to a server, so your photos stay on your device from start to finish. Always keep the original file too, because a compressed copy cannot be made sharp again later.
JPEG is the oldest of the three and the best choice for photos. It handles smooth colour changes well, which is why cameras and phones save photos as JPEG by default. At quality 80, a JPEG photo usually looks the same as the original on a screen, while the file is much smaller. Lower the quality to 60 or 50 if you need a tiny file and can accept a little softness.
PNG is the best choice for screenshots, logos, and pictures with sharp lines or text. It keeps every pixel exact, so text stays crisp, and it supports a clear background. The trade-off is size: a PNG photo is often much larger than the same photo saved as JPEG, and it cannot shrink much without losing its exact pixels. WebP is the newest format, and it often beats JPEG on size at the same quality, while also supporting clear backgrounds. Most modern browsers and phones open WebP without trouble.
If you compress a PNG photo and the saving is 0 percent, or even a small negative number, nothing has gone wrong. The tool shows the real saving, even when it is zero. PNG files are already stored in a clever way, and a photo with lots of fine detail gives the format little room to work with. Converting that photo to JPEG or WebP at quality 80 would shrink it a lot, but it would also lose the exact pixels and the clear background that PNG keeps.
Screenshots and simple graphics are different. A screenshot with large areas of flat colour can shrink well as a PNG, because the same colour repeats across many pixels. The rule is simple: use PNG for sharp graphics and text, and use JPEG or WebP for photos. If a PNG photo is too large to send, save a copy as JPEG for sharing and keep the PNG original safe.
Quality 80 is a good default for most photos. It cuts the file size by a large amount while keeping the picture looking clean at normal sizes. Quality 90 or above is worth it when the image will be printed or shown very large, or when it holds fine detail such as a face or small text. Quality 60 to 70 works well for thumbnails, chat messages, and web pages where the picture is shown small and speed matters more than fine detail.
Email is the most common reason to compress a photo. Many email services limit attachments to 20 or 25 megabytes, and a handful of phone photos can pass that limit fast. If you need to send several photos as one file, turn them into a single PDF with the JPG to PDF converter first. Compressed copies at quality 80 usually bring a set of photos well under the limit. Upload forms for jobs, schools, and government services often limit each file to 1 or 2 megabytes, and a compressed photo passes where the original would be refused.
Websites are another big use. A page with large images loads slowly, and visitors leave slow pages. Compressing every image before upload keeps a site fast and uses less data for visitors on mobile connections. Social media also shrinks uploads on its own, so sending a pre-compressed copy gives you control over the quality instead of leaving it to the platform.
Compression makes a file smaller, but it cannot make a blurry photo sharp, fix bad light, or add detail that was never there. If the original is low quality, the compressed copy will be low quality too, only smaller. For that reason, keep the original file and compress a copy.
The best habit is simple: keep the original, compress a copy at quality 80, check how it looks, and download it only when you are happy. A photo compressed at quality 80 still shows enough detail for the face shape detector to read it. If the file is still too large, lower the quality a little at a time and check again. With that habit, you get small files, good pictures, and no lost originals, and your photos stay private because everything runs in your browser.
No. The compression happens in your browser with a canvas, and your photos never leave your device. There is no upload and no server copy.
You can compress JPG, PNG, and WebP images. JPG and WebP use the quality slider, while PNG is saved without loss, so the slider does not change a PNG file.
PNG uses lossless compression, which keeps every pixel exact, so a detailed photo gives it little room to shrink. The tool shows the real saving, even when it is zero. Saving the same photo as JPG or WebP would shrink it much more.
Quality 80 is a good default for most photos. It cuts the file size by a large amount while keeping the picture looking clean. Use 90 or above for large prints, and 60 to 70 for small previews.
At quality 80, a photo looks the same as the original at normal sizes on a screen. Below quality 50, most photos start to show blocky patches, so check the result before you share it.