PNGGauntlet Icon PNGGauntlet Help

« Back to PNGGauntlet

FAQs

Question: What are all these PNGOUT options?
Answer: Check out this PNGOUT tutorial on Ken Silverman's (the creator of PNGOUT, which PNGGauntlet uses for compression) site. In general, the default options will get you the smallest file.
Question: Why does it take so long to compress a file?
Answer: PNGOUT works really hard to compress your images to the smallest possible size. That just takes some time.
Question: Why do the progress bars jump back and forth?
Answer: The progress bars take progress information from PNGOUT. PNGOUT makes several passes over the image trying different techniques to compress the files. What you're seeing is the progress of each of these passes.
Question: Why does PNGGauntlet need the .NET Framework?
Answer: XBList is developed in C#, using the .NET Framework. This means you need to have the framework installed for it to run.
Question: I compressed an image with alpha, and now the alpha doesn't show up in my editor. Why?
Answer: To minimize file size, PNGOUT will compress 32-bit (RGB+Alpha) images down to 8-bit with palletted alpha if it can. While 8-bit paletted alpha images work fine in many editors and in all web browsers that support transparent PNGs, it does not work in Photoshop, Gimp, or Paint Shop Pro. If you want to edit the compressed images in any of those programs, you should choose the "RGB+Alpha" color depth in the Advanced Options panel when compressing files that have an alpha component.
Question: Hey, can you make PNGGauntlet use multiple processor cores to compress images?
Answer: While it would be pretty easy to add multicore support for PNGGauntlet, I will not be doing it. If you want to take advantage of multiple processor cores, go buy PNGOUTWin from the original creator of PNGOUT. PNGGauntlet would be nothing without Ken Silverman's PNGOUT, so I'd rather you support his product than make PNGGauntlet do everything.