Makes more sense when you think of it in terms of Google both getting to control the standard and getting to shove their libWebp binaries into Firefox, Linux, Mac/iOS, popular image processing libraries, etc etc (oh but HURR DURR IT’S OPEN SOURCE yeah that doesn’t matter when every project just uses Google’s source code without looking at it because Google generously made it a complete turnkey solution you can just import. This isn’t even a hypothetical, Google has already managed to backdoor literally every device that uses it and it had already been exploited by their darling Israel for ages before someone outside of Google discovered it, you expect me to believe it wasn’t intentional?). Like so many things in the tech world, it’s not for your benefit, it’s for the corporations’.

I thought webp was supposed to be smaller at the same loss-level as jpeg? Also, doesn’t it have a lossless mode too? Compatibility is an issue.

…that also has arbitrarily small dimension restrictions.

Webp and avif are nice, but I think their inherent base in a video codec makes them a bit funny, e.g. lack of progressive decoding. I await our jxl future. Jpeg is dated and we can do a lot better than a format defined in the early 90s, as venerable as that format may be.

It’s like holding onto mp3 when aac and opus exist, or mpeg2 when hevc exists. The only benefits of the old stuff is less computation required, which only matters if you are using some seriously primitive hardware in 2025.

Incompatible with every website in which browser? It works for years in both Chrome and Firefox. Is this a meme for Safari users only?

The fact that Google invented this format is the most annoying thing about webp, but the complaints in this image haven’t been an issue for a very long time in my experience.

Webp is pretty great actually. Supporting a 32bit alpha channel means I’ve actually managed to reduce file sizes of what were formerly PNGs by something like 80%, which drastically improved performance (and the size of my project). I don’t get where the complaint of image quality came from either, as it seems to perform better than JPEG at the same file size.

The worst part is that you missed the real problem with the format: the CPU overhead (and therefore the energy cost) of handling the file. A high-traffic site can dramatically increase the energy required for the images processed by the thousands/millions of clients in a single day, which places a drain on the grid and emits more CO₂ (yes, this is really a thing that people measure now).

Basically Google invented the format to externalise their costs. Now, rather than footing the bill for bigger datacentres and greater bandwidth, they made everyone else pay for decompression.