I recognized that some files, especially photo-like images seem to be a bit off regarding saturation and/or hue when being saved through the pngquant plugin.

I saved a photo through the old "save for web" - way and through pngquant to compare them, they look as following:

(save for web above, pngquant below).

In order to reproduce the case I uploaded the files here for download:
"original": https://dl.dropboxusercontent.com/u/81358/temp/2013-08-31-11.19.52.jpg
"pngquant result": https://dl.dropboxusercontent.com/u/81358/temp/2013-08-31-11.19.52-libquant.png
"save for web result": https://dl.dropboxusercontent.com/u/81358/temp/2013-08-31-11.19.52.png

It would be great to see a preview of the image with the settings applies
(including settings proposed here: #4).
Instant feedback and avoiding the 'min' parameter (as the CLI requires) is something a GUI could offer.

Hi there!

Great plugin, would it be possible to include options for the number of colours used in the optimisation?

vplw_fleche-copy.png is the file produced by the plug-in.

Picolo:Desktop Fred$ pngcheck -vv vplw_fleche-copy.png
File: vplw_fleche-copy.png (6136 bytes)
chunk IHDR at offset 0x0000c, length 13
129 x 200 image, 8-bit palette, non-interlaced
chunk PLTE at offset 0x00025, length 768: 256 palette entries
chunk tRNS at offset 0x00331, length 146: 146 transparency entries
chunk IDAT at offset 0x003cf, length 5141
zlib: deflated, 32K window, superfast compression
row filters (0 none, 1 sub, 2 up, 3 avg, 4 paeth):
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
(200 out of 200)
chunk IEND at offset 0x017f0, length 0
No errors detected in vplw_fleche-copy.png (5 chunks, 76.2% compression).

Picolo:Desktop Fred$ pngout vplw_fleche-copy.png vplw_fleche-copy-pngout.png
In: 6136 bytes vplw_fleche-copy.png /c3 /f0 /d8
Out: 5944 bytes vplw_fleche-copy-pngout.png /c3 /f0 /d8, 254 colors
Chg: -192 bytes ( 96% of original)

Picolo:Desktop Fred$ pngcheck -vv vplw_fleche-copy-pngout.png
File: vplw_fleche-copy-pngout.png (5944 bytes)
chunk IHDR at offset 0x0000c, length 13
129 x 200 image, 8-bit palette, non-interlaced
chunk PLTE at offset 0x00025, length 762: 254 palette entries
chunk tRNS at offset 0x0032b, length 145: 145 transparency entries
chunk IDAT at offset 0x003c8, length 4956
zlib: deflated, 32K window, fast compression
row filters (0 none, 1 sub, 2 up, 3 avg, 4 paeth):
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
(200 out of 200)
chunk IEND at offset 0x01730, length 0
No errors detected in vplw_fleche-copy-pngout.png (5 chunks, 77.0% compression).

zopflypng also did the same kind of palette reduction (only 254 entries at the end).

Original file:

Wondering if I am doing something wrong here. I am using the plug-in for PS CS6 on OS X. I have a 50x50px 24bit PNG file without transparency. That file right now using regular 'save for web' is 831 bytes.

Using this plug in and doing 'save as' with pngquant, results in a file that is 6000 bytes...

Isn't pngquant supposed to make smaller files?

After installing the plugin, launching PS CS5, opening an image and doing a Save As, the indicated option is not in the drop down menu.

The console does not display any messages different from a standard PS start up process.