still undecided on this onealso the modgroid who blocked all new image formats on this site is a buttfuck
just so you know if you have the option of choice and you pick anything other than .png you're a FAGGOT
>>109882365i want to save space. nvme storage isn't getting cheaper, dipshit.
>>109882195The best info I've found from someone who isn't a complete meme spouting retard mongoloid mouth breather is and he's basically concluded that the stock version of libwebp sucks ass, iris-webp is a good middle-of-the-ground image encoder. AVIF wins hands down but its main drawback is that when dealing with high-res images it's decode intensive and thus more optimal on devices that can hardware decode AVIF.https://giannirosato.com/blog/post/case-against-jxl/Also try umigalaxy if you want to experience the freedom to upload WebP images.
>>109882195>jpg and pngold shit with annoying limitations but works on everything>jxl and avifmodern shit that supports all you’d want but support still isn’t quite there>webpliteral fucking dogshit, worst of all choiceskill yourself daiz
>>109883303see post above you retardthough halifex hasn't released the public .exe encoder yet
>>109883303Oops meant Halide, I forget their stupid name. But yeah google's webp implementation blows for lossy image compression. However it's not completely useless, it's quite respectable at lossless if you're okay with the 8-bit limitation.https://halide.cx/iris/
>>109883200>"The average Web consumer doesn't need lossless" ... "This rules out JPEG XL's lossless advantage">completely dismisses lossless jpeg reencoding due to a ~33% decoding performance penalty>discourages web adoption because non-web programs might not support it and that would be frustratingHe narrows the scope so much and in such absurd ways to completely undermine his conclusions, even if his data isn't cherry-picked, which it may well be.This guy has a paid webp encoder, And is launching a paid avif encoder. There is obvious conflict of interest, so take that with a huge grain of salt.
>>109882195jxl >= avif > webp (lossless) > png > jpeg >>>>> dogshit > webp (lossy)
>>109883851The current decoding complexity of jpeg xl is a complete and utter disaster though. AVIF is already having a hard time getting much adoption because it's 2X decode intensive compared to fucking JPG.JXL literally needs a miracle at this point.>>109883868lol keep up with the thread retard.
>>109882195time for you to stop posting this shit over and over and over again and just fuck off, thanks.
>>109883912>because it's 2X decode intensive compared to fucking JPGIf you think that's the reason adoption is slow, you are stupid.
>>109882377sounds like a poorfag issue but either way why are you wasting storage you cannot afford, one with limited amount of writes no less, on something you clearly don't care enough about
>>109883912>lol keep up with the thread retard.Neck yourself. Spamming in every format thread doesn't make you right.
>>109883997So Gianni Rosato is a fucking retard, right?The co-creator/maintainer of SVT-AV1-PSY who focused on quality over metrics?The guy who convinced mainline SVT-AV1 to adopt variance boost/quantization matrixes?So what literal who? twitter faggot from india using chatgpt should we trust then? :^)
AVIF> but it can take a lot of time to process a large number of them if they're also large resolution.That's the trade-off with good compression though.
>>109884347That's why SVT-AV1 got tune 3. It's incredibly fast if you accept dropping to 4:2:0.Actually 4:4:4 support was a huge thing in SVT-AV1-HDR recently, it might not be far behind avifenc which is pretty exciting desu.https://www.reddit.com/r/AV1/comments/1wlro96/svtav1hdr_420_ghost_robot_is_out/>inb4 "go back"Yeah because the twitter screenshot parroting here is way more reliable right?
If you need a lossless picture, please consider using JPEG XL unless a lossless WebP is smaller. (Such cases will sometimes exist until the lossless encoder of JPEG XL is improved further.)JPEG XL is expected to be supported in almost every browser very soon.Chrome support arrives in Chrome 155 (2026-10-06).Firefox support arrives a week later in Firefox 158 (2026-10-13).However, if you need a lossy picture, AVIF is almost always better.And it will become even better in 2027 when some new AV2-based version of AVIF (or some new AVIF-like format based on AV2) arrives at last.
