
I’ve been using this trick for years but it seems it’s never really been blogged about. When saving JPEG files using the “Save for Web” feature (”Save for web & devices” in CS3), the quality slider exhibits some strange behavior. Increasing the quality setting by a single percent usually adds only a little extra file size (about half a kB for the test file I used). Going from 50 to 51 with the same file added a full 10 kB. There’s also quite a difference in image quality between 50 and 51. In fact I feel 51 looks pretty good and is the optimal setting for most web projects. Anything above that is a waste of bandwidth, except perhaps for photography portfolios and such.
So the slider appears to have a little ’speed bump’ in the middle. Anything up to and including 50 will definitely get you visible artifacts and mediocre image quality at best, anything above 50 looks OK, with 51 being an ideal trade-off between file size and quality. It is definitely true that tweaking these settings for each individual output file will get you the best possible results, but for batches, droplets and brainless image saving, JPEG 51 works better than any other setting.
(Thanks to Anko Elzes for discovering this and telling me about it)












Heeej, still designing for bandwidth?
Wel een goeie vondst; the jpeg quality tipping point…
Hoe’st nou?
Comment by Roy Scholten — July 25, 2007 @ 8:25 am
Maybe you should study the JPEG compression procedures and report to us what the mathematical reason for this kind of behaviour is…
Lot’s of information in this article: http://en.wikipedia.org/wiki/JPEG
Comment by Sint — July 26, 2007 @ 9:28 pm
huh for all my life I used a brainless 80, only on sundays 65. But it seems like I’m now gonna switch to 51.
kudos roy!!
Comment by Max — October 25, 2008 @ 10:57 am