Fortunately, and _I can't emphasize this enough_, we're now in a situation where the major browsers support Webp or can have fast decoding support easily added. Webp is based on the I-frame encoder of VP8, and for lossy encoding represents a several-generations improvement over Jpeg. And it's here today. Sure, we'll all be using Avif in a HEIF container one of these days, but that isn't relevant to people building systems today.
Use WebP! For everything! Check out some comparisons between WebP and MozJPEG here: https://xooyoozoo.github.io/yolo-octo-bugfixes/#buenos-aires...
I now upload WebP and HEIC images to Google Photos, where they are both supported.
> Use WebP! For everything!
Jyrki Alakuijala, one of the creators of WebP, on WebP vs JPEG [1]:
>> For high quality photography, I (and butteraugli) believe that JPEG is actually better than WebP.
>> Below JPEG quality 77 WebP lossy wins, above JPEG quality 77 JPEG wins (for photography).
>> This was based on the maximum compression artefact in an image -- averaging from 1000 images.
Better meaning here [2]:
>> Faster decode (up to around 6x faster) and less bytes needed at high quality (in comparison to butteraugli scores).
[1] https://encode.ru/threads/2905-Diverse-third-party-ecosystem...
[2] https://encode.ru/threads/2905-Diverse-third-party-ecosystem...
That's interesting. Of course, the subjective part of that is one person's take, and the "objective" part of it is pointless because the whole point of Guetzli (the jpeg encoder) is to try to maximize the Butteraugli score, so saying that WebP gets a lower score is not significant.
Personally, WebP looks a lot better to me in the direct tests of equal file size that I've seen. It even looks better than Pik, which is Google's experimental successor to Jpeg that also uses Butteraugli.
And it would be odd, to say the least, if a codec from the early nineties could beat a modern one on Intra-frame coding, which has been a subject of immense research over the years.
Take a look at some of these for yourself. https://wyohknott.github.io/image-formats-comparison/
So my advice is encode in multiple formats to achieve the broadest browser support and the best image quality/size trade off that you’re willing to allow. That said... it does sort of bug me that every couple years we have to revisit which codecs we’re using because the implementations keep marching on...
That's the sort of faux-professional hyper-contrarianism that is "bordering on detrimental".
I just checked Magnum, a somewhat professional photo agency. They use JPEG. So do the NYT, flickr, and probably the vast majority of professional and totally unprofessional websites.
It seems there is some use left in the format. Not being able to print to billboard sizes doesn't diminish this. Because (a) that use case is a rounding error, and (b) WebP is still not safe for such purposes – TIFF is.
That you find web using hardcore old style JPEGs when they've been replaced by better formats long ago also doesn't mean that JPEG is really suitable way to store or share photos - especially when your display is good hi-dpi stuff. Also - do you find GIFs technologically OK for sharing animations today when there is stuff like h.265...?
In addition, all modern browsers support the <picture> element, which allows them to automatically download image the best meets their needs.
The <picture> element is great but using it means not, as you wrote, "Use WebP! For everything!" Maybe you meant "Use WebP! For everything! With Fallbacks!"
I can get behind that. :-)
What I meant by "for everything" was to use it for both photographic images and illustrations instead of using two different formats.
Until it does people will probably still be shipping jpg/png as standard.
I’ve literally never seen anyone do that, leave alone this being done “often”.
Cases on the flipside includes developers using JPEG for everything. 100KB highly artifacted illustrations used throughout web layouts, which would be infinitely better as clear 10KB PNGs.
Because cameras and phones give you JPEGs. The common user doesn't shoot RAW. I cannot see any not-highly-technical user convert JPEGs to anything else.
I occasionally archive some imagery from web and while viewing them in Irfan I am frequently confronted with "This image is JPG with .png extension, would you like to rename it?" prompt, without what I'd probably had no idea how frequently this discrepancy occurs.
> All too often I’ve seen people encoding 8MP photos as PNGs...
And now apparently it's some CMS that was doing that... which doesn't make much sense either. Either way this is just such a patently and obviously dumb thing to do that it makes me doubt your experience is anywhere close to being statistically significant.
All too often I’ve seen people encoding 8MP photos as PNGs and wondering why they’re all 50MB in size.
Next on the hit list is outputting images at the right size. If the image is never going to be shown greater than 500px wide, save a copy that’s 500px wide. WordPress has this feature built in- learn to use it if that’s your flavour of CMS. Your bounce rate will go down, I guarantee it.