Image Compressor

Reduce image size with visible controls

Choose one or more JPG, PNG, or WebP images. Keep the format or convert it, set JPEG/WebP quality, optionally limit width, and optionally request a target size in kilobytes. PNG optimization remains lossless. Processed files stay in your browser and multiple outputs download together as a ZIP.

What actually makes an image smaller

There are three useful levers: fewer pixels, a more suitable format, and stronger lossy compression. A maximum width reduces dimensions only when the source is wider. JPEG and lossy WebP quality discard progressively more detail. PNG optimization searches for a more compact lossless representation, so its savings are less predictable and no pixels are changed.

Target-size behavior

For JPEG and WebP, the target-size field tries several quality settings and keeps the highest tested quality that reaches the requested limit. It is a best effort, not a guarantee. If the image is still too large at the minimum practical quality, reduce maximum width. PNG cannot chase a target by lowering quality because PNG output here is lossless.

Worked example

Suppose a 3000 × 2000 JPEG is 2.8 MB and an upload form allows 500 KB. Set maximum width to 1600, keep JPEG, enter 500 KB, and process it. The tool first resizes to 1600 × 1067, then searches JPEG quality settings. A detailed or noisy photo may still need a smaller width; a simple image may finish comfortably below the target.

Picking a format

JPEG is broadly compatible and effective for photos, but it cannot retain transparency. WebP often stores photos and transparent web graphics efficiently. PNG is appropriate for screenshots, logos, diagrams, and pixel art where exact edges matter. Converting a photographic JPEG to PNG usually makes it larger and cannot restore detail already lost by JPEG compression.

Local codecs and privacy

The compressor uses locally hosted MozJPEG, libwebp, and OxiPNG WebAssembly codecs. The browser performs the decode, optional resize, and encode. No image bytes are posted to AwesomeTools or a third-party API. Most embedded metadata is not copied to the result, including common camera and location fields.

Limitations and assumptions

Files are limited to 30 MB and decoded images to 40 megapixels. Animated PNG and WebP are rejected. Compression results differ by subject: skies, gradients, text, and sensor noise respond differently. Browser color management can affect decoded pixels. Repeated lossy compression compounds artifacts, so start from the best available source.