memes

fucking Telegram automatically converts any webp sent in a message to a fucking sticker

I didn't want that. I want the ability to view the image, including zooming in and panning, and telegram forcing it into a sticker kills that completely

webp is absofuckinglutely inferior to JPEG-XL and that one is where you actually have that problem. I’m literally providing an avif-fallback on my website, because otherwise pretty much no browser would support anything.

(Speaking of it, avif is also superior to webp.)

for my use cases of memes or a PowerPoint type thing once in a while for school. Literally any image format works for me. I don't care about quality (as long as it's not REALLY bad) and just want to get the image from Google to the PowerPoint, and somehow GOOGLES own image format fails to work for GOOGLES PowerPoint product.
I don't understand how you can not support your own format 10 years after it came out.

pro tip by the way, you can open it in Microsoft paint then "save as -> .PNG" to get Google slides/whatever to accept it.

(before someone recommends alternatives, im talking about use on a locked down school computer. I can't use alternative software that's better because they block images in WIKIPEDIA, no shot for using an actual foss software lmao)

in my honest opinion, it’s a real shame that webp isn’t widely supported. it’s actually really great: it has awesome lossless compression, it’s so much smaller than a png while not losing any quality, it supports animation and loops, etc. it’s like jpg, png, and gif rolled into one format.

Real men use .ico

The giant jpeg square artefact on the side of Homer's head in the first frame undermines the message somewhat.

I recently put in a lot of hours for a software system to be able to handle webp just as well as every other image format it already accepted. I put in a lot of work as well. Hadn't heard about it for a while, but saw the feature release statement for the new version I knew my changes were in. It wasn't on there. So I reached out to my contact and asked if there was an issue or did it get bumped to a later version or what? So she told me the marketing team that do the release statements decided not to include it. They stated for one, people already expect common formats to be handled. Saying you now handle a format looks bad, since people know you didn't handle it before and were behind the curve. The second (probably more important) reason was nobody knew what webp even was and it's only something technical people care about (they probably said nerds, but my contact translated). So no regular customer would be interested and it could only lead to confusion and questions.

I hope somebody is happy with the work I put in tho. Somebody is going to drag a webp into the system and have it be accepted. Someday.... I hope...

skill issue

As someone who sometimes needs a quick and dirty stock image for my work, webp is the bane of my existence. The work computers won't let me visit sites or install programs/extensions to convert the image, and my document processing programs have no fucking clue what to do with the format. There is an option in Microsoft edge to edit image, and it will dump the result as a .png which is the only workaround I've found.

Just change the file extension to *.png. Works every time.

I'm working on a project which generates images in multiples sizes, and also converts to WEBP and AVIF.

The difference in file size is significant. It might not matter to you, but it matters to a lot of people.

Here's an example (the filename is the width):

Also, using the <picture></picture> element, if the users' browsers don't support (or block) AVIF/WEBP, the original format is used. No harm in using them.

(I know this is a meme post, but some people are taking it seriously)

.jxl is the better image format anyway

Since we're here and someone may find it useful, I use this: https://addons.mozilla.org/en-US/firefox/addon/dont-accept-webp/