← Back to Tools Home | Olutil Image Tools
🌐 English

Image Compressor

Shrink one photo before sending it, or drop a folder of product shots and watch each file get lighter. Both jobs live on the same page: single mode gives you a compare slider, batch mode builds a table with the old size, the new size and the saving for every image.

Quality, maximum width and output format can be set per file, and anything that has no headroom left is flagged instead of being quietly inflated. Originals on your disk are never touched. All processing runs locally in your browser. Your data is not uploaded to any server. 100% Local

🖼️ Upload an image to compare the before and after

How to Use Image Compressor

  1. Pick single or batch — single mode compares one file in detail; batch mode keeps a queue and reports every result.
  2. Load images — click the dropzone, drag files in, or paste a screenshot. Batch mode accepts multi-select and adds each picture separately.
  3. Choose an output format — JPG for photographs, WebP for modern pages, PNG when transparency or lossless output is required.
  4. Set quality — drag the slider from 10 to 100 or use a preset. The value is ignored for PNG because that encoder stays lossless.
  5. Limit dimensions — keep the original pixels or cap width and height, with an aspect-ratio lock and an exact-pixel override.
  6. Compress — single mode re-encodes as soon as a setting changes; batch mode waits for Compress all so a large queue is not started twice.
  7. Review the result — single mode offers a draggable before-and-after slider; batch rows list old size, new size and the percentage saved.
  8. Download — save one file from its row, or use Download all to save every finished image one after another.

What the quality setting really changes

JPG and WebP divide the image into blocks, transform each block into frequency coefficients and then round those coefficients more coarsely as quality falls. At 75 to 85 most photographs look identical at normal size while losing a large share of their bytes. Below 60 blocking and colour bleeding become visible around edges, and repeated saves stack the damage because each one re-quantizes an already degraded image. The slider never changes the pixel grid, only how precisely those pixels are stored.

Why PNG often refuses to shrink

PNG uses lossless DEFLATE, so the encoder cannot discard detail the way JPG can. A screenshot exported by a design tool is usually optimised already, and re-encoding may add a few bytes for a fresh header. Real reductions come from changing the pipeline instead: convert to WebP, flatten a mostly photographic PNG into JPG, or reduce the dimensions. Keep PNG for logos, interface captures and anything that needs an alpha channel.

Features

When to Use Image Compressor

Online shop product photos

A catalogue of two hundred shots at four megabytes each will slow every collection page. Batch mode with a 1600 pixel width cap and quality 80 typically brings each photo under three hundred kilobytes while keeping zoomed detail acceptable. Rename nothing before exporting; the rows keep the original file name and append a suffix, so the mapping back to your spreadsheet stays clear.

Email newsletters and attachments

Mail servers reject or delay messages with oversized attachments, and readers on mobile data abandon heavy newsletters. Compressing hero images to JPG at quality 75 and capping width at 1200 pixels keeps a full issue in a few hundred kilobytes. Keep the logo as PNG if it needs transparency, and remember that some clients still ignore WebP.

Blog posts and Core Web Vitals

Large images are usually the heaviest part of a page and the main cause of a poor Largest Contentful Paint score. Export at the widest size the layout actually uses, compress to WebP where supported, and keep a JPG fallback. A batch run over the whole media library makes the improvement measurable instead of fixing one hero image at a time.

FAQ

Does compression change the pixel dimensions?

Only when you choose a custom maximum width. With the default keep-original setting the canvas keeps every pixel and the saving comes from the encoder alone. Setting a width of 1600 pixels does both jobs at once, which is usually the cheapest way to prepare photos for a website.

Why does my PNG stay the same size or grow?

PNG is lossless, so the encoder cannot throw away detail the way JPG can. Screenshots that were already optimised often gain a few bytes because the browser writes a fresh header and colour profile. Convert those files to WebP or JPG, or resize them, instead of compressing the PNG again.

Is EXIF metadata removed?

Yes. Every image is redrawn on a canvas and re-encoded, so EXIF fields such as camera model, GPS position and capture time do not survive. Orientation is applied to the pixels before that step, so rotated phone photos still appear upright. Keep a copy of the original if the metadata matters.

Does batch processing freeze the page?

No. Encoding runs inside a Web Worker so the interface keeps scrolling while images are processed. One or two files are handled at a time to keep memory in check, and the queue reports progress. Very large panoramas can still take a few seconds each on a laptop.

What quality setting should I use?

For photographs, 75 to 85 removes most invisible weight and is hard to distinguish from the original at normal viewing size. Use 90 or higher for artwork with fine gradients, and lower values only when a thumbnail is the final destination. Check each important result on screen before publishing.

Related Tools