Image Compressor

Our tool uses the browser's Canvas API to recompress images. Adjusting the quality slider changes the JPEG compression level, reducing file size while maintaining visual quality.

It depends on the format. PNG compression is lossless — every pixel is mathematically identical to the original, so quality never changes. Metadata like EXIF and color profiles are stripped for privacy, but the image data itself is untouched.

JPG and WebP use lossy compression, which does discard some visual data — but at sensible quality settings (70–85%) the difference is usually imperceptible while reducing file size by 50–80%.

Want to see for yourself? Use the Compare button after compression — it opens the full-screen comparison tool with Split and Side-by-side views, a Diff heatmap (neutral gray means no change, colored areas reveal exactly where compression made a difference), and a DSSIM score — a single perceptual-difference number using the same 1/SSIM − 1 metric convention used in our format benchmarks. Values below 0.01 are visually identical to the source.

Keep format (default): Compresses without changing format — JPG stays JPG, WebP stays WebP, AVIF is re-encoded at your quality setting, PNG is losslessly re-compressed to strip metadata and optimize encoding. Best when you just want a smaller file in the same format.

JPG: Converts everything to JPG. Maximum compatibility — works on every device, every browser, every app. The safe choice for sharing.

WebP: Converts to WebP — files are ~30% smaller than JPG at the same quality. Supported by 96%+ of browsers. Great for modern websites.

AVIF: Converts to AVIF — the smallest files, ~50% smaller than JPG at the same visual quality, with transparency support. Supported by every major browser since 2023. Ideal for web images. AVIF encoding is slower than JPG/WebP — large photos can take a few minutes, but the page stays responsive while it runs.

Read our complete format comparison guide and the AVIF vs JPG comparison for detailed benchmarks.

AVIF is the most efficient — roughly half the file size of JPG at the same visual quality, supported by all major browsers since 2023.

WebP is a solid middle ground — 25–35% smaller than JPG with slightly broader legacy support (Safari 14+).

Use JPG when you need maximum compatibility — email attachments, legacy systems, government portals, or sites still supporting Internet Explorer. For the best of both worlds, serve AVIF or WebP to modern browsers with a JPG fallback using the <picture> element.

See real benchmarks in our AVIF vs JPG comparison.

Input: JPG, PNG, WebP, and AVIF (multiple files at once).

Output: JPG (maximum compatibility, works everywhere), WebP (~30% smaller), or AVIF (~50% smaller — the smallest web format, transparency included). Use Keep format to stay in the original format — JPG stays JPG, WebP stays WebP, AVIF is re-encoded at your quality setting, PNG stays PNG (lossless re-encode).

You can open and compress multiple images at once — all processed in parallel in your browser. The exact batch limit adapts to your device's memory.

For web use, 70-85% provides the best balance of quality and file size — usually cutting files by 50-80% with no visible difference. For archival purposes, use 85-92%. Below 60%, compression artifacts become noticeable.

Here's the optimal workflow for website images:

1. Resize first. Never serve a 4000px photo in an 800px slot — use our Image Resizer to match your site's display width first. This alone can cut file size by 90%+.

2. Set quality to 70–85%. This range cuts file size by 50–80% with no visible difference. The quality slider's orange mark shows where your original sits — always drag below it for real savings.

3. Choose WebP as output. WebP images are ~30% smaller than JPG at the same quality. Use JPG only if you need legacy browser support.

4. Aim for under 200KB. Google Lighthouse flags images over 100KB as opportunities. Most content images at 1200px wide should land well under 200KB after following these steps.

📖 For a deeper dive — including benchmark data, side-by-side comparisons, and per-platform recommendations — read our full guide: Best Image Compression Settings for Web.

It shows your original image's estimated quality, found by matching its file size against the browser's encoder. If the slider is above the mark, the file may get larger instead of smaller — drag below the mark to ensure real compression.

The mark disappears for PNG files since they use lossless compression and have no quality level.

Yes! All compression happens locally in your browser using the Canvas API. Your images are never uploaded to any server.

Yes! Once you've visited the page, the compressor works without internet. All processing happens locally in your browser, so you can compress images anywhere — even on a plane.

Yes — it runs in any modern browser (Chrome, Firefox, Safari, Edge) on Windows, Mac, Linux, iPhone, iPad, and Android. All processing is local, so there's nothing to install.