Image Compressor · Resizer · Converter
Make images lighter. Keep them looking good.
Drop up to 20 JPG, PNG, WebP, or AVIF images. They are processed in your browser and never uploaded by this application.
Start here
Add your images
Processing starts with the recommended Balanced setting. Adjust the output below and reprocess whenever you want.
Browser-only processing
Maximum 25 MB and 40 megapixels per file, 250 MB per batch. Images are processed in this browser.
Output settings
Choose what should change
Choose images to start. Nothing is uploaded by this application.
A useful result, not a mystery slider
Choose the change that actually saves space.
Compression removes unnecessary bytes, resizing lowers the pixel count, and conversion changes how those pixels are stored. You can use one or all three without sending the source image to an application server.
Keep the original format first
It is the safest default for a mixed batch. Convert only when you know where the result will be used.
Resize oversized photos
A 4,000-pixel photo rarely needs all those pixels in an email, article, or product card. Fewer pixels can save more than quality changes alone.
Compare before downloading
Check dimensions, file size, savings, and the visual preview. The original is kept when another same-format encode would only make it larger.
Which format should I use?
JPEG is broadly compatible for photos. PNG preserves sharp graphics and transparency but may stay large. WebP is a practical smaller web format, while AVIF can be smaller still when your destination supports it.
What happens to metadata?
Re-encoded results apply image orientation and remove embedded metadata. A source is kept unchanged only when it is already smaller and known not to carry metadata that should be removed.
Why does PNG behave differently?
PNG optimization is lossless by default, so decoded pixels stay the same. For photographic PNG files, WebP or AVIF usually offers a more meaningful reduction.
Your images stay in this tab
File bytes, names, previews, and results are not put in a URL, cookie, or local storage. Reloading clears the queue. Only your tool preferences may remain.