Compress Image

Use Compress Image to reduce the file size of a JPG, JPEG, PNG, or WebP image.

You can compress an image by choosing an encoding quality from 10% to 100%, or use Target Max Size mode when you want the tool to try to create an image below a specified file size in KB.

The current Compress Image workflow processes one image at a time. If you need to compress multiple images, use the dedicated Batch Image Compression tool.

Compress Image provides two compression workflows.

"Compress by Quality (%)" lets you choose an encoding quality between 10% and 100%. The default quality setting is 80%. For formats that use lossy encoding in the active processing pipeline, lowering the quality setting can reduce file size but may also reduce visible image detail. The resulting size depends on the source image, format, dimensions, image content, and selected encoding quality.

"Target Max Size (e.g. 20 KB)" is designed to try to produce an image at or below the selected target size. Available quick presets include: 20 KB, 50 KB, 100 KB, 200 KB, 500 KB, and 1 MB. You can also enter a custom target size in KB. The tool first tries different encoding quality levels. If reducing encoding quality is not sufficient to meet the requested target, the target-size workflow can progressively reduce image dimensions. Because image compression depends on the source file and browser encoding behavior, review the generated result after processing.

In Quality mode, the image is processed using its original pixel dimensions.

In Target Max Size mode, the tool initially attempts compression at the original dimensions. If the requested target cannot be reached through encoding adjustments alone, the image dimensions may be reduced progressively to help meet the target file size.

If maintaining the original pixel dimensions is important, use Quality mode and review the generated output.

Compress Image accepts JPG, JPEG, PNG, and WebP images.

JPG and WebP images can use the browser's corresponding image encoding with the selected quality setting.

PNG behaves differently because browser PNG canvas export does not use the quality value in the same way as lossy JPG or WebP encoding. Depending on the source file and selected compression workflow, some PNG files may be converted to JPEG as part of the compression process. In particular, the current processing workflow may use JPEG output for larger PNG files or when required by the target-size compression process.

Review the downloaded file when output format, transparency, or image appearance is important.

Target Max Size mode uses repeated compression attempts to try to create an output within the selected size limit.

The tool tests different encoding quality levels at the image's original dimensions first. If necessary, it can progressively reduce image dimensions and try again.

This makes Target Max Size useful when you need to work toward a file-size requirement, but the resulting quality and dimensions can vary depending on the source image and requested target. Always verify the actual downloaded file size and image appearance before using it for an important submission.

The compression workflow redraws the source image through browser canvas processing before creating the output image. This process does not intentionally preserve source-image metadata such as EXIF or GPS information.

Transparency behavior depends on the output format. PNG and WebP output can support transparency, while JPEG does not support an alpha transparency channel.

If a transparent source image is converted to JPEG during processing, review the resulting image carefully before use.

Compress Image is designed for processing one image at a time with quality or target-size controls.

Batch Image Compression is intended for workflows where multiple images need to be compressed in one session.

Use the tool that matches the number of images you need to process.

Compression performance can depend on the source image file size, pixel dimensions, format, selected compression mode, requested target size, available browser memory, and device resources. Target-size compression can require multiple encoding attempts and may take longer than a straightforward quality-based compression. Large or high-resolution images can require more browser memory during decoding, canvas processing, and encoding.