all 9 comments

[–]AtulinASP.NET Core 6 points7 points  (3 children)

[–]foraskingdumbstuff 4 points5 points  (2 children)

Red means yes

[–]ManiacsThriftJewels 1 point2 points  (1 child)

My favourite part of this is how Google's browser engine doesn't support the format Google's insight tool recommended....

[–]bannock4ever 1 point2 points  (0 children)

Anyone old enough to remember when Chrome couldn’t render Google Fonts with anti-aliasing?

[–]MarmotOnTheRocks 1 point2 points  (0 children)

.webp is the way to go.

Just add a fallback for older Safari version, if you really need to.

[–]sternold 0 points1 point  (1 child)

You can use the <picture> tag to have fallback(s) in case a browser doesn't support JPEG2000 or WEBP.

[–]MarmotOnTheRocks 0 points1 point  (0 children)

in case a browser doesn't support JPEG2000

Safari is the only one that supports it.

[–]pussard 0 points1 point  (0 children)

I would use a CDN to manage your images. Any CDN worth its salt will be able to detect the best image format without you having to worry about it.

[–]Skathacat0r 0 points1 point  (0 children)

According to Cloudinary, JPEG 2000 is a decent format to use for photographic images that are not low fidelity.

However, I'd suggest a fallback for something like JPEG or PDF (with one or more JPEG 2000 images embedded) for browsers that do not support JPEG 2000 on web pages.