Add support for WEBP Animated Images and Emojis
I recall hearing elsewhere that Discord's current libraries do not support animated WEBP. This is disappointing, as there's a lot of untapped potential in allowing WEBP-format emojis and images.
The GIF format is bulky and inefficient. Orthodox methods of encoding GIFs restrict one to a 256 color palette and 1-bit alpha (basically on/off transparency for every pixel, no variation). To get a reasonable file size from a gif, one must romance with frame dropping and color reduction to achieve a slim yet very ugly end result. However, WEBP images are encoded in a manner similar to YouTube videos (YouTube uses VP9 whereas WEBP is a fork of VP8). With WEBP, users won't need to sacrifice color fidelity or framerate for a tolerable product. Rather, they can simply decrease the bitrate to fill the file size maximum. WEBP also supports full alpha and RGB (even in lossy mode!).
The current upload limit is a bit of a squeeze for GIFs. WEBP compression could prove useful in overcoming that file size limit and creating beautiful high-quality animated images and emojis.
-
Proper WebM support would be amazing, I have animations I need to share with our patrons that are in this format, but they don't loop and don't display properly in discord. GIF works okay but I can't have partially transparent pixels which really makes the animations look bad. Right now I need to export into WebM for our actual project files for use in roll20 and also into GIF to be able to show on discord.
1 -
WEBP is becoming the leading filetype on the internet. Discord is allowing itself to give users more excuses to switch to other chat clients that will support this filetype.
Do not allow yourself to fall behind the times, Discord. Remember your roots, lest you be destroyed by them.
4 -
+1 Please add support
i am tired to to check if a link is webp or gif to see if works on discord2 -
needing to use GIF rather then WEBP in 2021 is really disappointing
4 -
There is no way to have animated pictures with transparencys in discord. No apng, no webp. Only gifs. And they aren't good when it comes to transparencys.
Since webp is pushed so hard by Google, supported by every browser, so small in file size. Make it happen goddammnit! It's not that hard.4 -
Make it happen goddammnit! It's not that big of a deal.
So why are you screaming about it on the internet?
-7 -
So why are you screaming about it on the internet?
Of course people are upset. Just look at the date of this topic. They can't make their thumbnail maker understand animated WEBP and APNGs for literal years, so I don't really understand the point of your question.
4 -
So why are you screaming about it on the internet?
I mean, you probably have a point. I doubt complaining about it here will ever change their mind. This forum is here just to placate us until we forget about the issue. At least other people will know they're not the only one looking for this feature though.
3 -
+1 For adding support of animated WebP file-format.
3 -
Is this being worked on?
2 -
Wow! 2 years here and more on reddit? Please add animated .webp support.
2 -
+1 for WebP support. Please Discord, do something that actually benefits users and is a wanted feature by the community for once, unlike the recent brand redesign!
2 -
I discovered yesterday that selecting an animated WebP image as your avatar shows it as animated in the cropping dialog, but after saving the changes it just uses the first frame as a still image.
2 -
Please add Animated webp all main web browser have yet discord still doesnt whats going on
2 -
Tinfoil cap theory: animated WEBP uses a modern codec that compresses videos much better than gif (consider gif not compressed at all). For example, if you've got a gif video in like 30 megabytes, the same video could be encoded in webp with quality close to the source video (with full true color too) and.... under 8 mb, so you don't have to purchase Nitro just to upload your "gif" at all C:
3 -
Tinfoil cap theory: animated WEBP uses a modern codec that compresses videos much better than gif (consider gif not compressed at all). For example, if you've got a gif video in like 30 megabytes, the same video could be encoded in webp with quality close to the source video (with full true color too) and.... under 8 mb, so you don't have to purchase Nitro just to upload your "gif" at all C:
Makes a lot of sense, but I think they'd be saving money on bandwidth if they went with webp. It probably would amount to less expenses, and not everyone who is limited by this cap goes on to buy nitro so...
definitely sounds like something they would be doing though
2 -
Tinfoil cap theory: animated WEBP uses a modern codec that compresses videos much better than gif (consider gif not compressed at all). For example, if you've got a gif video in like 30 megabytes, the same video could be encoded in webp with quality close to the source video (with full true color too) and.... under 8 mb, so you don't have to purchase Nitro just to upload your "gif" at all C:
This wouldn't even surprise me to be honest.
1 -
3 years and no comment by devs yet being one of the highest voted threads
1 -
I submitted a formal ticket a while back and this is the last response I got on October 3rd.
Joshua here, checking in for my buddy, Anne. I just wanted to let you know that I'll be escalating this ticket to a team member to look into further. I genuinely apologize for the inconvenience in the meantime and will keep you updated here as soon as I hear back.
Let me know if you have any other questions at any time!
I think I even investigated the issue myself by looking into the HTML tree and the HTTP requests and emailed it to them.
2 -
The cause of the problem is that media.discordapp.net returns a 415 Unsupported Media Type HTTP error.
cdn.discordapp.com on the other does return the WebP. The issue is internal in Discord's servers.
If this comment is correct then I suspect it's caused by Discord's image resizer not being able to cope with animated WebP.
3 -
Zipdox is a hero. If they can't fix it with his diagnosis then they're doing it intentionally after all. :)
1 -
Zipdox is a hero. If they can't fix it with his diagnosis then they're doing it intentionally after all. :)
Yep, I got a confirmation that equates to "it's not a bug, it's a feature":
Thanks for waiting and I apologize for the inconvenience. This is John stepping in on behalf of my awesome teammate Joshua. It seems that this issue is intended behavior, but if you would like to see changes to these systems in the future, then you can definitely vote up the suggestions at feedback.discord.com.
It would really help us out if you upvote the idea since feedback contributes greatly to our decision-making of which features and fixes to implement in the future based on what our community wants.
I'm so sorry again that we don't have a current solution for you at this time, but I like to think that anything is possible in the future.I doubt this is intended behavior as the image tries to embed and fails. If it was intended behavior it wouldn't embed in the first place.
1 -
Damn, thanks for the hard work. I wonder when, if ever, we'll get WebP if they're behaving like this.
It seems that this issue is intended behavior, but if you would like to see changes to these systems in the future, then you can definitely vote up the suggestions at feedback.discord.com.
It would really help us out if you upvote the idea since feedback contributes greatly to our decision-making of which features and fixes to implement in the future based on what our community wants.Is it bad if I laughed? I guess I'm too cynical to believe that's going to change their decision here.
2 -
I wonder when, if ever, we'll get WebP
Probably just after they properly support a graphics stack from this century, i.e. not any time soon :-(
1 -
Well if anyone knows Go, please add support for resizing animated WebP to this: https://github.com/discord/lilliput
1 -
Well if anyone knows Go, please add support for resizing animated WebP to this: https://github.com/discord/lilliput
Nah Go knowledge doesn't help there, that's just a neat wrapper you'd have to add general support for animated webp somewhere deep in the graphics dependencies which are written in c/c++ which is a way bigger inconvenience
1 -
I'm gonna unfollow this thread but here's my two cents then:
I think if they aren't gonna change their minds on WebP in any way, the only real thing to do is to push for and standardize AVIF as the alternative motion image file format.
They have their reason for not supporting WebP in its motion form, and there's at this point nothing much we can do.
All we can hope is that AVIF by way of its file name will just make everyone think it's a GIF successor and start using that for animations and stuff.
2 -
Nah Go knowledge doesn't help there, that's just a neat wrapper you'd have to add general support for animated webp somewhere deep in the graphics dependencies which are written in c/c++ which is a way bigger inconvenience
Nah, they're already using AVCodec I think, which supports animated WebP.
1 -
I asked if they could if a temporary mitigation could be implemented:
Would it be possible to temporarily mitigate the issue by making the media proxy just pass through the file without resizing it? Until a proper solution is found at least. Implementing such a simple mitigation would require very little effort I believe.
And this is the response:
We sadly are not able to implement fixes upon request through the support portal. It would be best to head over to our feedback page and upvote existing posts, or create a new entry of your own. We really wish we could do more to help, but we thank you for your understanding.
🤡
1 -
We sadly are not able to implement fixes upon request through the support portal. It would be best to head over to our feedback page and upvote existing posts, or create a new entry of your own. We really wish we could do more to help, but we thank you for your understanding.
Between this and having to sign in twice just so I can upvote something I agree with, Discord is truly coming off as a 🤡 lol
Upvoting threads is clearly not enough, but it's pretty much up to them at this point. We have the technology, they our nitro bucks. Yet nothing gets done. Absolute shame.
4
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
81 Kommentare