Image Compressor
Try a smaller file without changing its pixel dimensions. Re-encode a JPEG, PNG or static WebP as JPEG or WebP and compare the real output before you save it.
How to use it.
- Choose one JPEG, PNG or static WebP image.
- Select JPEG or WebP output and adjust quality. JPEG fills transparent areas with white.
- Compress, inspect both previews and compare the byte counts. Download only if the result suits your needs.
A practical example.
A detailed photograph may tolerate a lower quality setting when displayed as a small blog image. Start around 80, inspect text and faces, then adjust. If dimensions are much larger than the display area, use the resizer first.
Explore website performance basics →What changes in the file.
This is quality-based, lossy re-encoding, not a lossless PNG optimizer. PNG inputs are converted to the selected output format. JPEG output uses a white background; WebP can carry transparency. The quality number is a browser encoder hint, not a percentage of the original visual quality.
Know the limits.
One static PNG, JPEG or WebP, up to 15 MiB, 16 million pixels and 8192 pixels per side. Animation is rejected. There is no exact KB target. An already efficient image may become larger; the comparison says so. Metadata/color profiles may change. Dimensions stay the same; use the resizer to change them.
File processing runs locally in this browser tab. Normal website resources still load from the site. Reset clears the selected image and result. Browser extensions and your device’s security are outside this tool’s control.
Website privacy policy →Common questions.
Is this lossless image compression?
No. JPEG and quality-based WebP encoding can discard visual detail. A PNG converted to either format is not lossless PNG compression. Keep your original.
Why did the compressed file get bigger?
Encoder choices, existing compression and image detail affect size. Lower quality or try the other format, inspect the result, and retain the original if it is better.
Will it make an image exactly 100 KB?
No. It reports the actual size after encoding. It does not guarantee a particular byte target.
Does this improve my whole website’s speed?
It can help prepare smaller assets, but loading also depends on layout, image dimensions, caching, scripts and hosting. A smaller file alone does not guarantee good Core Web Vitals.
Working on a business website?
Explore my technical SEO services for help with the wider project.