My blog posts were loading slowly. Not the text — the images.
I had a post with about a dozen photos, all PNGs straight from my phone. A few were 2-3MB each. On my laptop it was okay-ish. On mobile data, the images loaded one by one, and a friend told me he gave up halfway through.
So I tried three free tools I kept seeing mentioned, with the same set of images, and compared them on the things that actually mattered to me: do I have to upload my photos, is there a size cap, and can I get them into WebP for the web.
No sponsorship here, just what I ran into.
The three I tried
1. TinyPNG
The one everyone knows. It works well, and the output looked good.
The catch for me was the upload and the cap. Files go to their servers — they say files are kept up to 48 hours — and the free web version is 20 images per batch, 5MB per image. A few of my phone photos were already over 5MB, so I had to shrink them first somewhere else, which defeated the point.
Good if you have a handful of small files and you don't mind uploading. Not great for a whole post of large PNGs.
2. Squoosh
This one is from Google Chrome Labs. It runs in your browser, nothing is uploaded, and you get a lot of control — you can compare codecs side by side, try MozJPEG, WebP, AVIF, and see the result before you download.
I liked it for one hero image. I spent ten minutes tuning a single photo and it looked great.
The trade-off is that the web interface does one image at a time. There's no batch mode in the browser. For twelve images, that meant twelve separate rounds of open, tune, download. I gave up after the third.
3. zippic
This was the third one I tried, on https://zippic.app/ — I just opened it in my browser, no install, no account.
You drag a PNG in, pick WebP as the output, and try 75% quality first. That's what I did. One 2.8MB PNG came out at a little over 300KB, and I couldn't tell the difference on a blog page. A couple of very detailed photos I tried again at higher quality — bigger file, but still much smaller than the original PNG.
What made the difference for me was that it also runs locally in the browser, like Squoosh, so nothing is uploaded, but the flow is simpler: drag in, pick format, compare, download. There's also a bulk page if you have a lot of images — https://zippic.app/bulk-image-compressor — where you can drop them all in and download everything as a ZIP. I used the single-image page for the blog post, the bulk page for a later batch.
One honest note: there's no "compress to exactly 100KB" button. You check the result and adjust quality or size yourself. And the site suggests keeping individual files under 50MB, since it's all done in your browser's memory.
Quick comparison
| Upload? | Batch | Free cap I hit | |
|---|---|---|---|
| TinyPNG | Yes, to their servers | 20 per batch | 5MB per image |
| Squoosh | No, local | 1 at a time in browser | No cap, but slow for many files |
| zippic | No, local | Single + bulk ZIP page | No fixed count, limited by browser memory |
Limits change, so check each tool's own page if a limit matters to you. The numbers above are what I ran into in November 2026.
What I actually do now
For a blog post, I do this:
- Keep the original PNGs in a folder, don't delete them.
- Open https://zippic.app/, drag in one image, output WebP, try 75% first.
- Compare the before and after before downloading — check the sky for banding, text edges for jaggedness.
- Replace the PNG on the post with the WebP, and check the page loads faster.
If it's one image I really care about and I want to fiddle with codecs, I'll still open Squoosh. If I have twenty images, I'll use the bulk page and download the ZIP.
The post that was loading slowly now loads noticeably faster. Not because I found a magic tool, but because I stopped uploading 3MB PNGs to a web page.
Top comments (0)