Copy image? Nope, here’s the link instead.
Why are we sending someone to “Extra Hell” for making an improved image format that has better compression and is an overall improvement over all 3 of the existing formats it replaces (jpeg, png, gif)?
Shouldn’t this apply to
everyonethe companies who refused to adopt it, thus breaking every normal image workflow? (Same thing can be said about JXL)Edit: fix vague wording
Because they have a poor user experience with an OS and applications that have chosen not to support it properly, and blame the image format for this
I have comments about your first question, but they’re mostly stupid on my end. I think the problem for most is related to your 2nd question. Google is doing it’s google thing where they do a lot to force adoption with a goal of doing nothing to support it. Combine with a general distrust of Google.
I’m realizing my wording might be vague, by “everyone” I meant the big tech companies that didn’t implement it, like Google, Apple, Microsoft, and Adobe. AFAIK most of the open source apps actually implemented support pretty quickly, and obviously it wouldn’t be the end users’ fault because they can’t change what formats are supported
I’d say the knowledge about webp’s benefits is not mainstream at all, I learned about it last week from a random YouTube video. So when people download a file that isn’t working as expected they don’t know who to be mad at so they make memes like this.
Obviously be mad at whoever responded to a request without accept webp in it with a webp or didn’t provide an alternative. Nothing wrong with supporting webp with a fallback
It’s not an improvement over PNG.
but it has an optional lossless mode that no one uses
No one uses it and even if they did, you’d never know since there isn’t a .webl or .webpl to differentiate lossless.
You know a PNG in lossless, you know a jpg is lossy. webp should just be assumed lossy 100% of the time.
webp will always be funny to me because it was made exclusively by Google to reduce lossy file size for faster HTTP transfer, but then when JPEGXL was released with better lossy compression and the ability to load graphical data progressively by quality instead of line by line bitstream, Google switched to AVIF instead and doubled down on even more lossy compression because they just want to save cloud costs and don’t care about image quality.
AVIF has a lossless mode. Although nobody cares for it, the slightly lossy is fine. It’s adjustable just like JPEG is adjustable.
Also, it’s really annoying to convert since ffmpeg can’t do it yet, but the two major browsers support AV1 video, with alpha, in a .avif that you can shove into an <img> tag. It’s basically just a video. But animated. And transparent. It also works on Discord web now (but not mobile). AND you can set repetition count, if you really want. Can’t show the masterpiece I’ve made before with that since it would be way out of topic, although here’s an HD example with the animation from here:
demo

Ironically, the creators of the damn browser didn’t know that it’s possible and used a .webm. Well, the bourgeoisie division of the organization that makes the browser, of course. The @redhat.com emails, lol. Also, the metadata for the .webm says “ezgif”. Oh welp. And yes, the greenscreen leaking at the edges was already there.
Command (bourne shell):
ffmpeg -c:v libvpx-vp9 -i pop-up-1480.webm -strict -1 -f yuv4mpegpipe -pix_fmt yuva444p - | avifenc --stdin pop-up-1480.avif(-c:v needed to get ffmpeg to read the transparency).File size:
.webm: 540KiB
.avif: 486KiB
.gif: 6.2MiBGIF command used for comparison:
gifski pop-up-1480.webm -H 832 -r 33.3333333333333333333333 -Q 100 --extra -o pop-up-1480.gif, 100% to match original quality somewhatspoiler
It also supports HDR. In year 2060, when the @redhat.com people finally get HDR out for everyone, we will have lazer eye “”“gifs”“”
spoiler spoiler
Users of custom clients and netsurf (via custom frontend) and such will be complaining about this just like about OP’s repost is complaining about WebP.
Google has NIH Syndrome.
WebP has all the functionality of jpg, gif, and png with better compression ratios.
As someone who has edited videos and had to convert WebPs every time I accidentally downloaded them, no they do not.
Translation: your video editor sucks.
Have you ever edited a video or are you just talking out your ass? Really doesn’t matter, he said they had the same functionality, they do not. It had no problem at all with other image formats.
To be fair, if your video editor doesn’t support webp in 2026 it has to at least suck a little bit.
Speaking of talking out your ass, you seem unable to differentiate between the responsibility of a file format, and the responsibility of the file reader.
Yes, a few times. I have exactly 60 “.kdenlive” files in my “videos” dir. That editor itself sucks, but seems your does harder.
Can’t demo much as most of these are aimed at very niche communities (ranging from 1k people to 4 person groupchat with only 1 person who cares), and some are also a bit problematic in content. As you could have guessed, it’s meme stuff, so quite image heavy.
some examples that I am comfortable with sharing
license (please note that they are basically collages of de minimis and transformative content, sometimes needed for parody)
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE Version 2, December 2004 Copyright (C) 2004 Sam Hocevar <sam@hocevar.net> Everyone is permitted to copy and distribute verbatim or modified copies of this license document, and changing it is allowed as long as the name is changed. DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. You just DO WHAT THE FUCK YOU WANT TO.Now, what are you defining as “functionality”?
There’s a difference between whether or not a file format supports features and a software supporting the file format. A tractor can have loads of features and still not be the right fit for you if it does fit in your barn. Doesn’t mean the tractor doesn’t have those features. DDR5 can be better then DDR4 and yet not all motherboards support it. It is trivial to convert from webp to the file format you need for your unique situation. Its supported baseline by browsers and use on the web is its best case. I make websites that allow people to customize SOLIDWORKS CAD files. SOLIDWORKS doesn’t support webp: I still use it on the website wherever possible and if someone uploads in webp I just convert to jpg before inserting into SOLIDWORKS.
can’t store images larger than 16,383 x 16,383 pixels
I weep for the web server that has to serve those size images. I can typically cut webserver bandwidth in half by converting all non svg images to webp. Have had one project where this cut the network fee by 80% and allowed us to downgrade the rented server space.
that’s a lot, what format did it have before?
… What was ever wrong about webp? As far as I know it gives slightly better compression than jpg at similar quality
The biggest issue AFAIK has been that certain OS vendors didn’t allow their users to enjoy it while the internet went on to use a new tool, so they got a lot of broken images
That is your vendors fault, not webp
?format=jpeg
Pin that to your clipboard
You use shitty app it is not fault of format
I agree with the comic. Saving a webp as an actually useful file format is an extra annoying step.
Half the time it works. Half the time it doesn’t. Idk what the determining factor is but I’ve just got in the habit of doing screenshots. Which I then still have to open another program to paste and save.
What even was the reason for this awful file type ?
Copy image? Nope, here’s the link instead.
Where are you seeing this?
Have you never tried to copy a webp? Or have you been blessed by never having to mess with them?
I mess with webp every day, its great for compressing because it keeps great picture quality
Are you telling me when you look at this image: https://lemmy.world/post/49219082
You can’t copy it?
You can, but you can’t paste it into certain apps as it isn’t recognized, or attempting to will paste the URL instead in others and load it like a shared link.
Use it with FoundryVTT all the time, its great for reducing size without losing much quality.







