I think I like that. Normally, I compress my pngs with gimp (by indexing them). That works fine, and as I do most of my screenshots as well with it, it is not

I think I like that. Normally, I compress my pngs with gimp (by indexing them). That works fine, and as I do most of my screenshots as well with it, it is not too cumbersome. But it's not perfect either. The results of tinypng are a bit better. In my tests the images are almost the same size, text becomes equally blurry, but the gradients are a bit better preserved and the colors less distorted. With the Api, i can build a small tool which compresses the image for me without having to start gimp. Like (beware, crappy code): #!/bin/bash API_KEY="" wget -O "${1/.png/_tiny.png}" $(curl --user api:$API_KEY --data-binary @"$1" https://api.tinypng.com/shrink | JSON.sh | egrep '\["output","url"\]' | sed -e 's# [.*\]\t*##' -e 's#"##g') I won't become a paying customer though, 500 is perfectly fine for me, and I still have gimp. But I can imagine professional CMS-systems (or wordpress setups) including this in their workflow to automatically compress the .pngs inserted by their authors, instead of having to find the best compression method on their own (and rely on the server setup). PS: If that assumption turns out to be true, it could be worthwhile to build a wordpress plugin using the API to try to push that.