The technology that managed to accomplish what NFTs couldn’t.
deleted by creator
Not really? Just lucky.
Go back and eddit this comment when you download a webp and nothing can use it.
I have plenty of WEBP and every image editing/viewing application I have installed can use it fine. Including, but not limited to:
pdn, GIMP, Krita, Aseprite, InkScape, OpenToonz, IrfanView
I think Apple users have issues with Webm & Webp? But the issue here is using Apple products in the first place. Losing 90% of basic functionality is what you expect when using one of those.
Maybe then I’m the unlucky one that want to use things that don’t support it.
And I’m not on Apple lol (linux)
Name one program that doesn’t support WebP.
All the memes I send to my friends on messenger basically come from Lemmy. I always have to download the image and use the phone image editor to crop it by one pixel. It then let’s me save it, and it saves as jpg/png by default.
Yeah but memes don’t need high quality?
Windows can only display .bmp images apparently. It’s an old problem.
Don’t think so cause if I change the extension to PNG or JPG it works just fine
Skill issue, the only actual drawback is that some legacy systems whitelisted image extensions and haven’t been updated. Even then just take a screenshot and upload that.
I wouldn’t mind the webp format if programs supported it!
They do tho.
Mint’s default wallpaper manager doesn’t, and Discord doesn’t let me pick a .webp as an avatar. Those seem like 2 pretty big ones that don’t work.
I’ve also run into other less common examples over time, but those are more random spread out things and I don’t remember what they are.
No offense but Mint is not a great example. They are behind in general. Still figuring out Wayland, fractional scaling and VRR, things which KDE has supported in stable releases for some time now. KDE even is getting HDR along with Cosmic and SteamOS, something Mint isn’t even close to. Mint kernels are older than Ubuntu’s, which are hardly new. I used to love Mint, but they are falling further and further behind KDE, Gnome, and System76 (PopOS and Cosmic). To me it seems the new distros for newbies are Fedora, Debian, and a few derivatives like Nobara, UBlue, and PopOS.
Cinnamon hasn’t been keeping up for years. When I tried Mint again when I went full-time linux last year, and found the same unfixed bugs from three years prior, I ditched it forever.
The format has been around for 13 years, and is objectively superior to its predecessors. By now it is actually set to be replaced by avif and jpgxl which are even better.
At this point running into cases where it doesn’t work makes me question the software, not the format.
I don’t understand what people’s problem with this format is except in the case of animated .gifs. I can view it. I can reupload it. It’s still an image and it still works. The exception is animations. Animations always end up as a still image when saved in that format.
I use the Firefox extension Save WebP as PNG or JPEG (Converter).
I got excited when I saw this post because I knew someone in the comments would have a solution!
Same. Very useful.
(I also have no love for .webm as a video format)
It’s just mp4 dumbed down which itself is mkv in stupid form.
Webp works fine for me now.
The problem is AVIF. I mean I love AVIF (almost as much as JPEG-XL), but it doesn’t work with anything except browser web pages, even after all this time.
My only concern with jpeg xl is… how do you know if the encoded file is losslessly compressed or not?
with jpg and png, one is lossless, one is not. But if all the files have a jxl extension, you can’t know unless the encoder adds metadata for it, right?
I felt the same way about webp when it came out.
In practice it doesn’t really matter:
- if you’re encoding the file you know how you’re doing it.
- if you’re receiving the file, you get the pixels you get no matter how it was encoded.
- if you’re sending the image through some third party service, they’re going to reencode and mangle it anyway so there’s no point in worrying.
Also, it turned out that even if it’s quite good, lossless webp is rarely seen in the wild because svg is more convenient.
For me webp is always some gif I’m trying to text people, and now I have to go convert it.
webp is better than jpeg, png or any other file format
But the best image format to download is the original one it was uploaded in, without the recompression of server-side conversion to a lossy webp which we’re seeing all over the place.
Even if it wasn’t, you could just convert it to .jpg if you felt strongly about it. Not as though there’s a compatibility issue.
The complaint people are having is with resizing/manipulation after download. They want these enormous uncompressed files floating around on every website, in the off chance they plan to download it and manipulate it. 99.9% of the web needs to be full of megabyte sized image files for the 0.1% y’all want to play with.
I do this little trick where I change .webp to .jpg
Ezgif.com has a webp converter
Webp is great for web images tbough
ffmpeg <3
At least it’s not a .art file
If you get this reference, remember to take your daily meds on time.
Referenced acknowledged.
After all, we have CompuServe to thank for the proliferation of .gif.
I hate .webp, almost no software supports it. I can see it reduces the amount of space, but I’m always having to convert it
That format is awful from a user perspective.
Why? I use it all the time and never had issues with it
How so. I get that the support isn’t there yet, but how is the format itself awful
Literally, you answered your own question. From the user end, unsupported file types of any frequently shared format are garbage. No one cares on the user end about server space. They care about sharing a funny image. They don’t care about 2 extra ms of load speed. They want shit to just work.
It’s the same reason Open Office sucks. You can’t rely on it to just work. As much as dev’s hate it (myself too), reliability is king. Webp fails this measure, badly.
The format itself is perfectly fine, it’s just that most software doesn’t work with formats made in the 21st century
The only program that I ever use that doesn’t support webp is Facebook Messenger.
Lucky
Just imagine if there was an actual open consortium not spearheaded by monied commercial interests that could temper recent Google decisions. They’ve lost a lot, if not all, of their goodwill with old guard, open web standards nerds. And the old guard that still actively support their standards influencing schemes now make too much money to stop.
Yes, JPEG XL really is the one that got away. 😭
Hey Google, 🖕🖕 for killing it, man. Very evil and self-centered choice.
Also I just noticed what the arrow in the image pointed to. Holy crap that would be awful if true.
Yeah, sorry, that part I didn’t fact check myself so I didn’t even want to mention it. Like I said, there’s many possible reasons.
Not sure what you mean by “Google killed it”. JPEG XL proposal was only submitted in 2018 and it got standardized in 2022. It has a lot of features which are not available in browsers yet, like HDR support (support for HDR photos in Chrome on Android was only added 8 months ago, Firefox doesn’t support HDR in any shape at all), no browsers support 32 bits per component, there’s no support for thermal data or volume data, etc. You can’t just plug libjxl and call it a day, you have to rework your rendering pipeline to add all these features.
I’d argue that Google is actually working pretty hard on their pipeline to add missing features. Can’t say the same about Mozilla, who can’t even implement HDR for videos for over a decade now.
They removed JPEG XL support from chrome. It was behind a feature flag previously.
(At least that’s what I gathered from reading the screenshot.)
Yeah, why keep a feature which doesn’t work? Once they add missing stuff to the renderer, they’ll add XL support back. But I guess that will take a few years.
Can you provide a source on how Google is working hard on JPEG-XL missing features?
