Image Compressor

When to use this

You're about to upload a hero image to your site and it's 4.7 MB straight from the camera. Your email newsletter platform caps images at 1 MB. Shopify is warning you that your product photos are slowing down your store. These are compression moments — you need the same image, just smaller.

The other common trigger is a platform-specific upload limit. Check the current requirement at the destination, then compare the compressed file with that limit rather than relying on a generic target.

If the source is much larger than its displayed dimensions, resize a copy before the final compression pass. This avoids encoding pixels the destination will not show.

Good to know

Quality values are encoder-specific. Start with a high setting, lower it in small steps, and inspect gradients, text, faces, and sharp edges at the intended display size.

Results vary by source. Dimensions, existing compression, detail, transparency, and output format all affect the final size. An already optimized image may change very little.

Compare accepted formats. If the destination supports both WebP and JPG or PNG, export copies and choose the smallest result that preserves the detail you need.

Compression is lossy and one-way. Once you compress, the discarded data is gone. Always keep your original files. Compress copies, not sources.

Everything stays on your device. No server upload, no account, no tracking. Your images never leave your browser tab.

Quick Reference

Image type	Inspect closely	Possible output
Photo	Faces, texture, gradients	Compare JPG and WebP
Screenshot	Small text and hard edges	Compare PNG and WebP
Transparent graphic	Edges and alpha blending	Use a format that preserves transparency