Core tool
Squoosh alternatives with more than one tool
Same codecs, more jobs.
Squoosh compresses one image beautifully. Here's what to use when you need more than that.
Compression
How did this tool do?
Side by side
How they compare
Squoosh is the honest benchmark here, so let's be clear about it: it's made by Google's Chrome team, it's open source, and it does all its work locally — in its own words, "images never leave your device since Squoosh does all the work locally". On compression quality it is genuinely excellent.
ImgKit uses the same two encoders. MozJPEG for JPEG and OxiPNG for PNG are what make Squoosh's output smaller than a browser's built-in save, and they're what ImgKit encodes with too. On a single image at the same quality setting, expect comparable results.
The difference isn't compression. It's that Squoosh is deliberately one tool: one image at a time, a quality slider, no batches, and no way to say "get this under 50 KB". If that's all you need, Squoosh is a fine answer and you should use it.
| ImgKit | Squoosh | TinyPNG | iLoveIMG | |
|---|---|---|---|---|
| Images sent to a serverThe one row that can't be undone — once a file is uploaded, you're trusting a retention policy. | No — everything runs in the browser | No — runs in the browser | Yes — kept up to 48 hours, in its own words | Yes |
| Account required | No | No | Not for the free web tool | Needed for larger files and some tools |
| Batch processing | Yes, unlimited | No, one image at a time | Up to 20 images at a time | Yes, with limits on the free tier |
| Compress to an exact sizeWhat you need when a form rejects anything over 50 KB. | Yes — compress to an exact KB | No — quality slider only | No | No |
| Third-party trackersOpen devtools, reload, and read the Network panel — it takes about ten seconds. | None. Cookieless page counts only | Google Analytics | Google Analytics | Google Analytics via Google Tag Manager |
| Price | Free | Free | Free tier, paid API | Free tier, paid plans |
Checked in September 2026 by loading each site and reading its network panel, and by quoting each tool's own description of what it does with your files. Features and pricing change — if you spot something out of date here, tell us and we'll correct it.
Being fair about it
What each one does better
For a single image where you want to pore over the settings and compare encoders side by side, Squoosh is the better experience — it's built for exactly that, and it can output JPEG XL and QOI, which ImgKit can't.
- ImgKit
- Weaker than the desktop apps on very large batches, since a browser tab has less memory to work with than a native program.
- Squoosh
- Simpler for a single image, made by Google's Chrome team, and the only one here that can write JPEG XL and QOI. Its compression is excellent — ImgKit uses the same two encoders.
- TinyPNG
- A well-regarded API, official Photoshop and Figma plugins, and a WordPress plugin — none of which a browser-only tool can offer.
- iLoveIMG
- Mobile apps for iOS and Android, a full PDF toolkit alongside the image tools, and an interface translated into far more languages.
Guide
How to use it
- 01Drop your images — they stay in this tab.
- 02Pick a quality level, or switch to Target size for an exact number of kilobytes.
- 03Tap Compress and download. Nothing is uploaded at any point.
Good to know
Questions, answered
How do I make a photo exactly 50 KB?
Switch to Target size and enter 50 KB. ImgKit tries quality levels until the file lands just under your number, and shows the quality it used.
What if quality alone can't reach my size?
The image is scaled down step by step until it fits, and the new dimensions are shown on the file. If a form also requires exact dimensions, resize to those first.
Will the photo look bad?
Below roughly 20 KB you'll see some softness. Use Compare on any finished file to check it against the original before you download.
Why did a file come back the same size?
Some images are already well compressed. With the Auto format, ImgKit keeps the original rather than hand you a bigger file.
Is there a limit on how many I can do?
No limit, no signup, no watermark. Your device does the work, and several files download together as a ZIP.
Which is better: lowering quality or reducing dimensions?
Quality first, because it keeps the picture the same size on screen. Dimensions are the stronger lever though — halving the width and height removes three quarters of the pixels — so for a tight limit like 20 KB, resize first and compress after.
Does compressing remove the location data?
Yes. The image is re-encoded from its pixels, so EXIF — including GPS — isn't carried over. If you only want to strip metadata and leave the image untouched, use the EXIF remover instead, which edits the file without re-encoding.
Why does the same size look fine on one photo and poor on another?
Detail is expensive to store. A portrait against a plain wall compresses far harder than a photo of foliage, a crowd or fine text, because there's less variation to encode. Busy images need either more kilobytes or fewer pixels.