Image Compressor & Converter
Convert images to JPG, PNG, or WebP and reduce file size. All processing happens in your browser.
Drag and drop an image here or click to select
PNG is a lossless format, so the quality setting does not apply.
If the image is wider than this value, it will be scaled down proportionally.
Image Format Comparison
| Format | Characteristics | Best For |
|---|---|---|
| JPG(JPEG) | Lossy compression, small file size | Photos, general images |
| PNG | Lossless compression, transparency support | Screenshots, logos, icons |
| WebP | Lossy/lossless, most efficient | Website optimization |
To bundle converted images into a single document, use the PDF Generator. To create a site favicon from an image, try the Favicon Generator.
Common Image Format Mistakes
The same image can differ by 5-10x in file size depending on the format, or lose transparency entirely. Here are the most frequent wrong choices and how to fix them.
The "PNG is always better quality" myth
PNG is lossless, so compression never degrades quality - but for photographs with millions of colors, saving as PNG can produce files 5-10x larger than the equivalent JPG. The right rule of thumb: photos go to JPG or WebP; logos, icons, and screenshots go to PNG.
Common format mismatches
- Saving a phone photo as PNG - A 4 MB JPG can balloon to 25 MB as PNG. Inefficient for social media, email attachments, and web uploads.
- Saving a logo as JPG - Flat-color areas show visible 8x8 block artifacts, edges look muddy, and transparency is replaced with white. Use PNG for logos.
- Saving a screenshot as JPG - Text becomes blurry and color boundaries pick up ringing artifacts. PNG is the standard for screenshots.
- Using JPG when transparency is needed - JPG has no alpha channel; transparent areas are filled with white or black. Use PNG, WebP, or AVIF for transparency.
- Using WebP for print - Many print-shop RIP systems cannot read WebP. Use TIFF or high-resolution JPG for print production.
Are WebP and AVIF always the right choice?
- WebP - Roughly 25-35% smaller than JPG and about 26% smaller than PNG. All modern browsers support it, but IE11 and some in-app browsers do not, so a fallback is needed in those cases.
- AVIF - Another 30-50% smaller than WebP. Supported in Chrome, Firefox, and Safari 16+. Encoding is slow, which can increase build times.
- Practical pattern - Use a
<picture>element with AVIF → WebP → JPG fallbacks. If you need a single format, WebP offers the best balance of compatibility and compression.
Pre-upload steps that are easy to overlook
- Skipping resize - Uploading a 4032x3024 photo as-is forces mobile visitors to download 5-10 MB. Resize to 1200-1600 px wide before publishing.
- Leaving EXIF metadata in - JPG and HEIC files embed GPS coordinates, device model, and timestamp. Strip metadata before sharing publicly.
- Color space mismatch - Cameras may shoot in Adobe RGB or DCI-P3, while the web expects sRGB. Uploading without converting can make colors look washed out.
- Ignoring EXIF rotation - Smartphone photos store rotation as an EXIF Orientation tag. Some converters and viewers ignore this tag, resulting in rotated output.
FAQ
Are my images uploaded to a server?
No. All processing happens in your browser (client-side). Your images are never sent to any external server.
Can I convert HEIF/HEIC files?
Yes, if your browser supports HEIF/HEIC decoding. Currently Safari supports it, and Chrome has partial support.
Is WebP the most efficient format?
Generally, WebP delivers the same visual quality as JPG at 25-35% smaller file sizes. It is supported by most modern browsers.