WebP has:
>lossy encoding
>lossles encoding
>support for transparency even with lossy encoding
>support for animations
>50% smaller than JPG at the same visual quality
>25-50% smaller than non-lossy PNGs
>currently ~70-80% Web browser support
>is open sores and has no royalty fees
>?????
>profit
JPG IS FINISHED AND BANKRUPT!
Encoder: https://storage.googleapis.com/downloads.webmproject.org/releases/webp/index.html
More samples: https://developers.google.com/speed/webp/gallery
Is the hate behind WebP caused by the fact it was created by Google?
>>55146989
...but muh shitpics anon
>0.4%
lmao
inb4 google shills trying to defend this
I can't wait for a more efficient image compression format to replace JPEG, but I would prefer something based on HEVC to succeed it, like BPG.
>>55148340
Hello lossy pngfag
>>55148360
That test is invalid, FLIF is a lossless image format. Webp is a lossless and lossy image format + animations and losless encoding was not used in the test.
>>55148430
>FLIF is a lossless image format
the point is that BPG is superior you dullard
>>55148411
Never gonna happen. For one thing it's only like 10% better than Webp and you have to pay a royalty fee to the HEVC jews to use it. Because of that nobody will ever adopt it.
>>55146989
>only works on chrome
make this smaller and post it in this thread
>doesn't even work in firefox
i don't care about webp, i'd rather have apng support on 4chan
>>55148439
Not really. Transcoding images 500 times with lossy encoders isn't a realistic scenario and BPG is not that much of an improvement over Webp. Webp is royalty too, why pay for BPG is it only reduces file sizes by like 20% over Webp?
>>55148463
ok
>>55148461
what is:
>pale moon
>brave
>opera
>chromium
>>55148513
filesize only ya dingus. you lost a ton of data
>>55148479
Why are you still using firefox? Firefox died ages ago. I use Brave btw.
>>55148545
>breitbart
yeah, no.
show me another browser that supports extensions and is as customizable as firefox.
>>55148504
*royalty-free