Post #1837953
2026-04-29 08:36 UTC
Replies (6)
-
@hukl@chaos.social 2026-04-29 09:03
The key message is: use more efficient image formats than old school jpeg and png on the web! I don't care if it's webp, avif or jpegxl - as long as it looks good, uses less space and transfers faster, it's good. Easy win for saving resources - especially time and energy :) (I prefer avif atm because of wide support and very good performance for my use cases)
-
@_nd_@fnordon.de 2026-04-29 08:52
@hukl@chaos.social webp is a scourge *and* you must be aware the conversion is lossy. JPEG XL has a mode that supports lossless transformation between existing JPEG and JXL *and back*, at a size reduction of about 22% https://mina86.com/2025/use-jpeg-xl-already/
-
@eWe@chaos.social 2026-04-29 08:54
@hukl@chaos.social jxl ist immer noch das bessere Format. Echt Mist, das Google das im experimentellen Support versteckt hält… Aktuell funktioniert das nur auf Apple / Safari out of the box
-
@tisba@ruby.social 2026-04-29 08:58
@hukl@chaos.social to be fair, comparing lossless PNG with (in your example) lossy AVIF is of course resulting in good savings 😀 Out of curiosity, what kind of images have you converted? E.g. In the past I used to stick to PNG (with pngquant) for screenshots, because I've bitten too often with weird color issues.
-
@lbenedix@chaos.social 2026-04-29 18:22
@hukl@chaos.social I'm not convinced 🤨 I tried to convert the 525 images from a timelapse-camera and had to go to `-quality 55` to get comparable size to the jpgs.
-
@supergarv@phpc.social 2026-04-30 12:45
@hukl@chaos.social Ggf interessant: https://fershad.com/writing/power-consumption-jpeg-webp-and-avif/