I mean in terms of video containers, webm is a video container made by the same or adjacent team that made webp. The only other video container I’ve seen that supports transparency is HEVC, which only works in safari.
Transparency is the only reason I’d ever use webm, just to clarify.
… as opposed to webp, which also supports transparency?
I mean in terms of video containers, webm is a video container made by the same or adjacent team that made webp. The only other video container I’ve seen that supports transparency is HEVC, which only works in safari.
Transparency is the only reason I’d ever use webm, just to clarify.
If we’re talking in terms of vodeo containers (or codecs), then why are we talking about it on a post about webp?
Unless you consider webp to be a video container because it does support animated pictures, but, again, it also supports transparency.
Also, HEVC is not a video (/media) container, it’s a codec.
As a lay person, codecs and containers are not visible to me, but the file extension is.
So .webm would be relevant in a post about .webp, because they are only one letter different.
What are we even talking about?
fork:
videocontainers (incorrectly) for some reason;The fact that webm is relevant here is undisputed (or so I believe)