Kornel

Yes, libimagequant part of the pngquant project. It does 99% of the work.

I'm unable to reproduce this issue in Firefox 60. But generally that looks like a Firefox bug. It's a bit surprising, since [it worked fine last time I tested it](http://kornel.ski/color)....

Color profile handling in pngquant is optional and has 2 separate back-ends, so you will find builds from different sources behave differently in this area. Exact handling of sRGB chunks...

There is `--skip-if-larger` option. I suppose it would be nice if it was the default, but then such options are usually disabled with `--force` :/

Hmm, so adding `--overwrite` might be the solution

Try adding `--strip` to remove metadata. If the image has lots of pixels, it may just be that big. Expect 0.5 byte per pixel.

When you use stdout & stderr you have to read *both* of them in parallel, while the program is still running. Anything else will deadlock, it's just a matter of...

If you don't read stderr, you also risk deadlocks. When stderr buffer fills up, pngquant will be forced to wait for the buffer to be emptied by your process. If...

It's not possible to know file size without performing the full compression. You can use `-o - > /dev/null` to throw away the compressed data.

All pngoo does is launch pngquant command line. It does nothing else.