Image Compressor

How to compress an image

1. Choose a static JPG, PNG, or WebP image up to 20 MB.
2. Select the original, JPG, WebP, or PNG output format.
3. For JPG or WebP, choose Maximum quality, Balanced, Smallest file, or a custom quality value.
4. Compress the image locally in your browser.
5. Compare the actual file sizes and inspect the result preview.
6. Download the result when its quality and size meet your needs.

Compression and resizing are different

Compression changes how image data is encoded and stored. Resizing changes the number of pixels in the image. This compressor preserves the original width and height while asking the browser to encode a new file with the selected format and quality behavior.

If pixel dimensions also need to change, use the Image Resizer first. Reducing dimensions can produce a much larger size reduction than encoding quality alone because fewer pixels need to be stored.

Understanding the quality setting

JPG and lossy WebP quality values balance visual detail against file size. A higher value usually keeps more detail and produces a larger result. A lower value usually discards more detail and produces a smaller result. The relationship is not linear, and browsers may encode the same source differently.

• Maximum quality uses 92%.
• Balanced uses 80% and is the default.
• Smallest file uses 60%.
• Custom quality ranges from 10% to 100%.

These values are encoder instructions, not visual-quality scores or exact target sizes. Always inspect the downloaded file in its intended context.

Choosing an output format

JPG

JPG is a lossy format commonly used for photographs. It does not support transparency, so transparent pixels receive a white background during JPG export.

WebP

WebP supports lossy encoding and transparency in modern browsers. It can provide a smaller result than JPG or PNG for many images, but the outcome depends on the source and browser encoder.

PNG

Standard browser PNG export is lossless and does not use the Canvas quality argument meaningfully. Re-encoding can remove metadata or change file structure, but it may produce limited savings or even a larger file. The tool therefore hides lossy quality controls for PNG and explains the limitation before processing.

Why can a compressed file be larger?

File size depends on format, image complexity, transparency, source encoding, and browser behavior. A source may already be efficiently compressed, while converting a small JPG to PNG can add substantially more data. When a result is larger, the tool reports the increase and suggests WebP or a lower lossy quality instead of presenting it as a saving.

Privacy and processing limits

File inspection, decoding, Canvas rendering, preview, and download all happen in the current browser tab. Yellow Tools does not receive the image, and neither the source nor result is saved to your account.

• Maximum input file size: 20 MB.
• Maximum decoded image area: 25 megapixels.
• One image is processed at a time.
• Temporary preview URLs are released after replacement or reset.

Important limitations

• Animated PNG and animated WebP files are rejected.
• GIF and HEIC/HEIF input are not supported.
• Pixel dimensions remain unchanged.
• Canvas export may not preserve EXIF details, camera metadata, embedded color profiles, or other source metadata.
• The tool cannot guarantee an exact target size such as 200 KB or an exact visual-quality level.
• Browser support and encoding output can differ, so the generated Blob type is verified before a download is offered.

Frequently asked questions

Does compression change image dimensions?

No. This version preserves the original width and height. Use the Image Resizer when you need different pixel dimensions.

Can I compress without losing quality?

JPG and lossy WebP compression can discard visual data. PNG uses lossless pixel encoding, but a Canvas round trip can still remove metadata and does not guarantee a smaller file. “No quality loss” would therefore be an unsupported promise.

Why is there no exact target-size field?

Browser encoders do not map one quality value to one predictable byte count. Repeatedly encoding a full-resolution image to chase a target can also use substantial memory and processing time on a phone. Version one uses transparent presets and reports the actual output instead.

Need a production image pipeline?

Compressing individual files is useful, but a fast website also needs responsive image sizes, modern formats, caching, lazy loading, accessible alternatives, and performance measurement. Yellow Solutions can help design and implement that complete workflow.