formats

Addressing the JXL or JPegXL format floating around the internet.

We’re going to do something we usually do not do for ANY of our blog articles. We’re going to purposefully STOP all optimization of our files in this entry and only use ONLY PNG files (Blog article only, navigation, footer, and backgrounds will still be processed. It may sound totally counterproductive to do when making an article about a new format that the developers insist that you use. However, in order to graphically demonstrate my points about the “New kid on the image war block,” we must go totally lossless with a codec we trust and has been proven for almost 20 years.

Now, for those users running nightly builds of Chrome or Firefox that want to test out JXL Good news! Every article EXCEPT this one has already been encoded thanks to scripting mentioned in this blog article. So once you’ve enabled JXL in your browser (details described below) you can explore this site with it and see if it’s really all of the hype it’s meant to be!

Read on if you care about my rants and opinions of this format.

First there was AV1. Now there’s AVIF

A while back during my video encoding sessions, I toyed with the concept of serving AV1 videos on my site. The results were not great out of respect that we could not find a great way of detecting the client’s capabilities of video decoding without writing some shitty JavaScript system to snoop around and break privacy rights all the way. However, there’s a branch of the Av1 system known as “AVIF” which is designed to use for still images. It boasts about getting better compression ratio’s to that of even WebP images that we discussed a while back.

Why did we implement AVIF here? Read on if you want to know more.

JXL – JPEGXL and the web experience here.

Addressing the JXL or JPegXL format floating around the internet.

AVIF and WEBP is now being hosted here.

First there was AV1. Now there’s AVIF