WebP has been around for a while now, offering better compression and performance over JPEG and PNG. So why haven't more apps fully adopted it yet? Are there hidden compatibility issues, performance downsides, or just inertia in the industry? Curious to hear if the switch to WebP has made a difference for anyone here, especially for mobile performance.
Because it's Google. Apple in particular didn't want to play nice for many years and tried to pitch HEIC support instead (or AVIF these days). WebP came out in 2010, right when the whole mobile app vs web app thing was heating up and Apple/Google were fighting for mindshare. It wasn't until 2020 that Apple added stable support for WebP.<p>Neither offered a big enough improvement for end-users to care.* Cloud operators did care, and Imgix and Cloudinary can automatically transform older formats to WebP or AVIF, for example: <a href="https://docs.imgix.com/en-US/getting-started/tutorials/performance-and-metadata/improved-compression-with-automatic-content-negotiation" rel="nofollow">https://docs.imgix.com/en-US/getting-started/tutorials/perfo...</a> and <a href="https://cloudinary.com/documentation/image_optimization#automatic_format_selection_f_auto" rel="nofollow">https://cloudinary.com/documentation/image_optimization#auto...</a><p>There are also a bunch of Wordpress extensions that can do the same, and FOSS proxies too.<p>* Hell, you think PNGs are bad? We still use animated GIFs and MP3s, even though both are terrible by today's efficiency standards. Sometimes good enough is good enough.
As a user, WebP doesn't really bring anything to me that matters. I mildly dislike it (not enough to really complain), though, because a lot of my tools still don't understand the format.<p>So, at least for me, it's 99% inertia.
I use webp in my applications.<p>HEIC don’t display in browsers. Or maybe they do now but I haven’t checked lol. AVIF don’t work well in iOS messages for example. If you send someone an AVIF it asks you to download it. WEBP works just fine, like you’d expect any image to show up.<p>I used to convert any non JPEG image to JPEG.<p>Nowadays I convert any non WEBP image to WEBP.<p>My B2B saas has a file explorer functionally in it. Any image for display is served as WEBP, and it is converted after upload. The WEBP files are like 20-90% smaller than what the user uploaded. Of course, the user can download and I give them their original file back.<p>AWS charges me for bandwidth which is more expensive than storage. Most users upload images and view them (open it up in viewer) maybe twice. But they will scroll a lot more and when the explorer opens in grid they can see anywhere from a dozen to 40 images. A small amount will download the original again.<p>WEBP is used by a lot of non-Google companies. Notion, for example converts images to webp.
I process large amounts of images for sd and also do simple graphics work sometimes. Webp saves some space but is slow af at saving, like 10-50x slow. So not even remotely a good tradeoff. Reading is fine, afaict.
Because you also want to sell to customers who have older devices, which can't display WebP. People who are not computer enthusiasts can keep a machine around for a decade or more. The gains from using WebP are negligible, the downside when they break are significant.
Same reason many aren't using HEIC or HEIF which are common image files from phones now. They are overlooked or aren't thought about.<p>Also many people forget about JPE, which is rare, but I've had problems with it, its basically a DOS format for JPEG, and alternative for JPG
I really wanted to like WebP as a one stop replacement for jpg/png/gif. Sadly the ios webkit decoder for animated webp is infuriatingly inconsistent wrt frame rate so I had to abandon it.