Compress images with a live preview, sharp-grade download

Yes. No account, no signup, no watermark, no trial period. The slider preview runs locally; the final download is encoded by our server (sharp + libvips). The infrastructure cost is small enough that we cover it as a free tier.

The slider preview is computed in your browser — no upload there. The final download is different: when you click Download, the original file is sent over HTTPS to our compression service so the output gets a sharp + libvips encode (smaller than what a browser can produce). The file is held in a short-lived tenant-isolated cache, never used for training, and removed after the TTL. If the network is offline or the service is unreachable, the tool falls back to the browser-encoded version automatically; you can also right-click the live preview to save the in-browser version directly.

Yes. WebP is a supported input format on all modern browsers. You can compress a WebP and export it back as WebP (smaller), or convert it to JPG or AVIF while you're at it.

JPG, PNG, WebP, and AVIF on every modern browser. GIF works in Chrome and Firefox but only the first frame is kept — animation isn't preserved. HEIC from iPhones works in Safari only (Safari has a native HEIC decoder); in Chrome or Firefox, convert HEIC to JPG first using our Convert tool.

It depends on the input. A typical unoptimized photo at quality 80: WebP is usually 25–35% smaller than the JPG equivalent; AVIF is usually 40–60% smaller than JPG. PNG with Oxipng saves 30–50% on unoptimized PNGs, up to 70% on freshly-rendered ones. The live size counter shows you the exact number for your file before you download.

80 if you're not sure — it's the default and matches Photoshop's 'high quality' JPEG. Drop to 60 for web uploads where size matters more than print-quality detail. Drop to 40 only for thumbnails. Raise to 90–100 if you're editing the file further and don't want to stack compression losses.

Quality 100 doesn't mean no compression — it means 'minimize visible artifacts.' If your input was already an optimized JPG, re-encoding at quality 100 with MozJPEG can produce a larger file because the two encoders made different internal trade-offs. The fix: lower the quality slider until the size counter turns positive, or switch to WebP or AVIF, which compress smaller at the same visual quality.

PNG output runs through Oxipng, which picks better filter and deflate parameters than a standard canvas export would. Typical savings: 30–50% on unoptimized PNGs, up to 70% on freshly-rendered ones. It stays lossless — every pixel is byte-identical to the input. If you want a dramatically smaller file and don't need transparency, WebP at quality 80 usually beats any lossless PNG run — try both with the live format comparison.

No. Width and height are preserved exactly. If you also need to downsize the image (e.g., from 4000 px wide to 1200 px wide), use the Resize tool first or after.

No. The re-encoded file is stripped of EXIF, GPS, and camera metadata because both encode paths (browser preview and server-side download) drop source metadata by default. That's a privacy win for most users (no GPS coordinates leaked in the file), but if you need to preserve metadata, this isn't the right tool.

Not yet — one image at a time. Drop them in one by one: each run takes well under a second for JPG and WebP, a couple of seconds for AVIF on the first encode.

Encoding: yes — the download path uses libavif on our server, so AVIF output works regardless of whether your browser has a native AVIF encoder. Viewing the output: Chrome, Firefox, Safari, and Edge all support AVIF. If you're sending the file to a specific recipient, test once first; WebP is the safer universal choice.

There's no hard cap — it's limited by your device's RAM. A modern laptop handles 50-megapixel photos in a second or two. Very large files (raw input files over ~200 MB) may exhaust memory on phones — resize first if that's your situation.