What is Reddit's opinion of PNGGauntlet?

From 3.5 billion Reddit comments

It would've just been easier to reduce the width of the window and then take a screenshot.

In Firefox 17.0.1 (current latest stable release), go to Firefox button -> Web developer -> Responsive design view, which allows you to change the dimensions/resolution of the web page without having to resize the window. Set the width to about 700 pixels. Now go to Firefox button -> Web developer -> Developer toolbar and type in screenshot test.png 0 true as the command and press Enter and it will save a screenshot of the entire web page (even the parts that are not visible) but it should maintain the width at 700 pixels. The image will be saved in your Downloads folder.

Use PNGGuantlet to compress the image (visually lossless compression) and upload.

I managed to reduce it from 624 KB to 366 KB without resorting to PNG-8!

Here's what I did:

You seem to want 24-bit (full color) PNG with transparency (allowing for semi-transparent pixels).

Using some online PNG optimizers I got it from 624 to 615 KB. Not near good enough.

I tried running it through PNGGauntlet and got it down to 593,60 KB

Then I found this useful article:
http://www.smashingmagazine.com/2009/07/15/clever-png-optimization-techniques/

It gave me the idea to fill the color information of all the 100% transparent pixels with pure black for easier compression.
This got the file down to 565 KB out of Photoshop, and down to 540,7 KB after PNGGauntlet.

At this point I have shaved off over 80 KB, but we need more than 40 more!

At this point there is not much to do but to start reducing number of colors, so i apply the posterise-filter. I used 50 levels to not make it too obvious.
This gets it down to 474 KB straight away! Awesome. A trip through PNGGauntlet and the final PNG is only 366 KB! That's way better than I hoped for!

So what I did for the final result would be this:

1. Select all 100% transparent pixels and fill with 0,0,0 (black).
2. Inverse selection and apply as mask.
3. Image > Adjustment > posterise (~50 levels).
4. Run the PNG through PNGGauntlet.

Result is a reduction from 624 KB to 366 KB. A huge saving!

See for yourself: Compressed image

Note: Seeing the final size I could probably have used more posterise levels and still gotten under 500 KB. :)

You can use minus.com to mirror large images without them getting altered. I've already posted a link to a mirror image here for you. Also, use PNGGauntlet (lossless compression) to squeeze the last few bits out of the image.

So true. PNG Gauntlet would tear through all of their images in 30-40 mins on a quad core, even at the highest compression.

- I love the bottom right graph there, what program is that?

I would say something like:

>Please compress your photo to the .zip format.

Though I don't know why would you compress a photo to zip, images formats are designed to be highly compressed. I'd suggest optimizing the photo using something like PngGauntlet (lossless) for PNG, Jpeg-Optimizer (lossy, stick to ~80) for JPEGs.

Just beware that these site use lossy compression techniques:

> What does TinyPNG do?

> TinyPNG uses smart lossy compression techniques to reduce the file size of your PNG files. By selectively decreasing the number of colors in the image, fewer bytes are required to store the data. The effect is nearly invisible but it makes a very large difference in file size!

This is what I would recommend: pnggauntlet, it's a program that collects the best losslessly compression algorithms and then gives you the image with the best compression result.

I'm at 32,154, but this is a bit inflated. I haven't run my duplicate-culling program since downloading the Drawfriend archive, which had 3757 images that I probably already have a significant chunk of.

Though the count is similar, I'd estimate that only roughly half comes from the 26K image torrent - after I downloaded it I went through it and did extensive culling, removing almost all the images that were simply screenshots and most of the macros, as well as a bunch of other stuff I deemed to be cruft (the notion of saving fanfic as jpegs of text... It's hard to comprehend the thought process that would lead to such a thing). I've also sorted most of the images by pony, an ongoing process with about 5000 images currently still in the buffer waiting for review.

Oh, and I've also run every single PNG file through the PNG Gauntlet (a program that losslessly recompresses PNG files very thoroughly). I'd estimate that's saved me maybe a gigabyte of space overall, though it took weeks of processor time.

[](/twicrazy "There's a place for everything and everything in its place. Tidy, tidy. I'm the pony who makes things tidy, I'm a tidying monster.")

If you need to work with video, why not go with Lightworks, an academy award winning NLE.

This is less an editor and more of a swiss-army-knife - Irfanview will open nearly any image format, is lightweight and hella fast at moving through hundreds of gigantic images. Free too.

Finally, if you need to get really good compression on pngs, check out PNG Gauntlet

thanks :)

Just because I'm a bit of a compression fanatic, with pnggauntlet you can lossless compress this 2378KB file down to 449KB, and with tinypng (although a bit lossy) down to 122KB.

The only tool that I use for this is PNG gauntlet, which is what I think /u/manicnimrod is talking about. It removes metadata/other stuff from the icons but doesn't affect the actual appearance of the icons. If memory serves me, it removes maybe 15% of the icon file size. There might be some other versions out there, but I can vouch for this one.

Additionally, and possibly most importantly, scale your icon size down if necessary. I've found that 144x144 pixel icons are generally high enough quality to be used on top-tier devices, though others prefer 192x192px (you won't need anything larger than this).

Apparently Proguard also reduces apk size (though I believe it's mostly used to keep people from using your source code), though I think that it would probably have a minimal effect if your project isn't tons of libraries/giant java files.

Also clean your project (in Eclipse click the project tab at the top, and then clean) and delete any libraries which you won't use in your final Apk.

An important feature of "Save for web" is that it (by default) throws away all needless metadata (camera info, thumbnail, etc.). I don't know of any other programs that does this, but I'm sure many do.

For JPEG there's not going to be much variation between programs (just use optimized huffman codes, and reduce quality until you get acceptable quality vs. file size)

For PNG once saved out to a PNG (as 8-bit or 24-bit) you can use PNG Gauntlet to crunch them into a smaller file size. This will help even if saved by Photoshop (The way PNG compression works is that each line can have a different compression algorithms, and finding the best one for each line is computationally expensive – photoshop has found a middle ground, while PNG Gauntlet uses considerably more time to try more combinations and will give you smaller files).
An online option (not quite as powerful as PNGGauntlet) is https://tinypng.com/.

Just a tip: save your images in the PNG file format, to prevent visual artefacts due to lossy compression (seen in JPG images). If you want to compress PNG files without losing visual quality, you can use PNGGuantlet.

Yes its pretty swell these days, though there isn't anything wrong with gif. SMBC and a few other major webcomics at least still use gifs.

When you start to deal with larger PNG files you might want to look into compression options. One very popular one is PNG Gauntlet which has very good loss-less compression (smaller file sizes with no pixel data lost)

I also see the difference in Firefox and Chrome in particular the links being darker blue. I have done some poking around and I am pretty sure I know what is going on here. The issue is color profiles as suggested by on_a_moose.

You made your link images in Photoshop which saved them with an sRGB color profile, whereas you made your nav bar images in Adobe ImageReady which did not include any color profile. You can see the color profile information for each image using this tool based on Image Magick.

Firefox, IE9 and Safari respect color profiles, but IE8 and Chrome ignore them. I am guessing that, like me, you have your computer's color profile set to something other than sRGB. This means that when you view the link images through Firefox it helpfully corrects the color from the image's sRGB profile to whatever profile you have set for your computer, the nav bar images have no profile so it just leaves those colors alone. Chrome ignores color profiles, so it does not change the colors of either set of images.

When I altered my color profile from the one supplied by my monitor maker to sRGB and restarted Firefox then the color differences disappeared. I suspect that no one else here sees the problem because they have sRGB set as their color profile.

Due to the inconsistent support for color profiles, I suggest you strip off color profile information from all images put on your website using something like the PNGGauntlet tool suggested by pleasant_peasant, or you could use the underlying command line utility PNGOut, which has Mac and Linux ports. Alternatively ensure everything has the same color profile.

If you have a good multi-pass PNG compression utility (I think PNGGauntlet is a nice example) or some plug-in for Lightroom or Photoshop, you can reduce the size of a PNG by 30% to 75% (depending on image type, of course). Adobe software generally does a rather bad job when exporting PNGs.

1. Use the Posterize adjustment layer, and bring the number of levels as low as possible without starting to visually see the banding. This will cause more neighbouring pixels to become identical, meaning they will compress easier with PNG.
2. Save for web in Photoshop to PNG-24.
3. Run the image through applications like PNGGauntlet for Windows, and ImageAlpha for OSX. They will use a lot of techniques to try to find the optimal PNG compression for the image (it takes a bit of processing time though).

I came across a new issue I've not had before: My .png thumbnails were larger than the allowed 2 MB. I was able to find a number of compression tools, and ended up using PNGGauntlet, with very good results. It was somewhat time intensive at about 2 minutes per thumbnail, but compression seems to be quite efficient in terms of maintaining quality and reducing size.

You might want to compress the files before uploading. Your PNG files have about 1MB each, and you can compress them without any loss of quality to about 20kb each. I use http://pnggauntlet.com/ which is free and works very well.

PNGgauntlet is your friend for further compressing PNGs after if you need to squeeze those extra bytes out of it.

For 24-bit PNGs some posterisation before saving can also really help cut down on the size, and if you are using transparency you might also save further space by making sure the color of the 100% transparent pixels is a solid color (easy to compress). PNGgauntlet afterwards.

Overall great site, keep up the good work! BUT there is one thing I would like to point out: these JPEG artifacts are hurting my eyes. Images look nasty. Placing Your graphics in PNG format would be so much better. You can use PNGGauntlet to compress images. Best regards!

If it's a gamma problem, you may want to strip gamma info of the png images by running them through PNGGauntlet. Just make sure you untick the "Preserve Gamma Information" option in the app.

It also optimises your PNG file size, btw. For example, running your TopMid.png file through the app shaves around 7KB of the original.