Image Compressor for JPG, PNG, WebP, and BMP
This tool uses browser-image-compression to process supported images in your browser. Processing depends on format: JPG, WebP, and BMP use browser image APIs; PNG follows the library's PNG path and may be quantized. Re-encoding can change pixel values or dimensions. Results may be smaller or larger, so review the output before use. The original file remains unchanged.
How to compress an image
- Choose or drop a JPG, PNG, WebP, or BMP image.
- Adjust the available settings for the selected format.
- Review dimensions, appearance, and file size; results vary and may be larger.
- Download the copy if it meets your needs. The original is not modified.
Common use cases
- Create and review an image copy for a website or message.
- Compare compression settings on a copy of an image.
Frequently asked questions
Will compression preserve every pixel and the dimensions?
Not necessarily. Re-encoding may change pixel values; dimensions can depend on the selected settings. Review the output.
Will the output always be smaller?
No. Results depend on the image, format, and settings. The output can be larger.
Does quality affect every format?
Its effect depends on the input and output format. Check the result rather than assuming the setting is inert or guarantees a particular quality.
Are Compress Image and Compress PNG the same tool?
No. Compress Image uses browser-image-compression. Compress PNG uses Canvas with an optional scale setting that changes dimensions.
Is my image uploaded?
Processing runs in your browser; the image is not sent to a compression server.
Check the output before replacing the original
The quality setting does not guarantee a particular file size or visual result. Re-encoding may change source pixels. PNG input on this route uses browser-image-compression; the separate Compress PNG page uses Canvas with optional scaling. Processing runs in the browser.
- Supports JPG, PNG, WebP, and BMP inputs
- Adjustable quality for supported output formats
- Before-and-after size comparison
- Browser-side processing; no image upload
Free. No signup. No file uploads. Ads via AdSense (consent required).
Sources (2)
- Donald (Donaldcwl) (live). browser-image-compression. npm package v2.x (github.com/Donaldcwl/browser-image-compression, MIT license) — the general image compressor's implementation; format-specific processing may re-encode or resize images, so output pixels and dimensions are not universally preserved and output size is not guaranteed to shrink.
- WHATWG (live). HTML Living Standard — Canvas 2D Context + HTMLCanvasElement.toBlob(). html.spec.whatwg.org/#2dcontext — browser image decode, Canvas processing, and output encoding used by the general JPG/WebP/BMP paths; re-encoding results depend on browser and settings.
These are the W3C, ISO/IEC, ITU-T, and IETF specifications the tool implements or builds on. Locate them on w3.org, iso.org, itu.int, or datatracker.ietf.org.
Related guides
- EXIF metadata: inspect the file you actually shareCheck location and camera metadata, keep an original and verify the exported copy.
- Images and Core Web Vitals: diagnose before compressingFind the actual LCP element, reserve image space and verify changes without treating file-size savings as measured speed gains.
- Remove a background: inspect the mask and the exportCheck cutout edges, transparency and file format without assuming an automatic mask is exact.
- Responsive Images with srcset — Explained Properlysrcset and sizes without the confusion. How the browser actually picks an image, what w vs x descriptors do, and the patterns that work in production.