Please stop making gifs at all. It's a terrible format that creates massive files that look like shit.
Webm is supported almost everywhere now and manages better quality at higher framerates and smaller file sizes.
This is a most excellent place for technology news and articles.
Please stop making gifs at all. It's a terrible format that creates massive files that look like shit.
Webm is supported almost everywhere now and manages better quality at higher framerates and smaller file sizes.
Counterpoint: GIFs loop by default in basically every app, WEBM doesn't
Can just use avif instead, it holds an AV1 stream and acts like gifs/images do WRT looping — also very broad support (more than AV1 in WebM containers).
Demonstration:

Edit: switched to an example with simpler decode requirements.
Your demonstration is a sluggishly loading static image on my end, so I guess support isnt that widespread :P
(Im using the app "Summit")
I checked that app's source code, and basically they're doing their own avif decode call instead of relying on a browser/webview to handle it. So essentially they forgot/don't know/don't intend to implement animated avif. Looks like they also use the aom reference decoder instead of using something faster like dav1d.
Static image, also Summit.
Static image, Eternity.
Works great as a static image. Would probably be better if it actually played...
It's unfortunately not that simple. The AVIF doesn't load at Jerboa, for example :/
(on Arctic on ios) the uploaded image displays as a static image for me. Even clicking on it and waiting, it doesn’t seem to animate :T
Edit: I checked again through the Voyager app, and it did indeed load, though it took around 45-60 seconds* for it to get through the entire animation before it started looping again, albeit at the same speed as the first playthrough.
I chalked it up to the outdated hardware, as you mentioned in your reply. Cheers! :)
Apple has limited support for AV1 streams (yes, even for software decode) unless on very recent hardware. Here's an AV1 stream inside a webm container for comparison, would be interesting to see if that works over the avif container on your stack.
This doesn't work for me but the original one you posted does (Voyager, iPhone 14 pro)
Ah yeah, that would explain it - my phone is now pretty outdated (I’m on a 12) - I clicked on the image link in your response but it didn’t load for me, unfortunately.
I’m not sure if that’s a result of my outdated hardware or if I perhaps clicked on it before it had a chance to process your upload, but you seem much more knowledgeable than I, so I’m going to assume it’s my hardware. I appreciate the response and the second attempt, though! :)
It's an intentional behavior by Apple. Basically they just don't support AV1 videostreams unless the hardware you're using has a hardware decoder. They could support it using software decode (what browsers typically do for AV1 inside avif containers) but.... for whatever reasons don't.
Your example image doesn't work in boost while the gif above does :/
I’ve honestly given up on support of new formats.
Here we are, 2026, and brand new software like Lemmy:
Doesn’t support AVIF
Doesn’t support JXL
Doesn’t support WebP
Won’t upload short, small videos either.
Meanwhile:
Many clients won’t play animated WebP
Most clients won’t play APNG
Many won’t load AVIF
Basically only Apple/Safari will load JXL
VP8/VP9/AV1 support in video isn’t universal
What am I supposed to do?
I used to send support requests over this, but I’ve given up. We are going to be stuck with SDR JPEGs and blocky GIFs forever, especially since media format literacy seems to be decreasing.
Webm is supported almost everywhere now and manages better quality at higher framerates and smaller file sizes.
Anybody who has compared animated WebM vs animated JPEG XL?
I used to love optimising images in gif format. I would make like 4–30kb memes and animations for my friends in Photoshop CS2. It's actually extremely efficient and lightweight if you do it right… You have cool tools like transparency between frames and unbroken colour blocks don't take any additional storage space. There's nothing wrong with gif.
The problem is how people use them. We take a live action video file and shove it through an automated converter tool that doesn't give a shit about efficiency and will do a complete repaint between frames and use 256+ colour palette. Then you end up with an ugly dithered overcooked piece of shit 50mb 10 second animation. Gif was not designed for this…
"...massive files..."
I thought the file size was part of the format specification, no?
Yes? I don't really understand the question.
Problem is the medium people use to send GIFs to each other doesn’t support any alternatives

the same file without visual quality loss could be a 156.79 KiB webp file, saving energy, internet, and storage costs
Most people do this:
ffmpeg -i video.mp4 output.gif
...no, most people have never heard of ffmpeg and throw it in an online converter.
Which are probably just web front ends to the above?
Definitely, but then it's on whoever made the web tool. Still not "most people".
Thanks. This is going straight to my 'cool info to never be used' pile.
My folder like that is just named ★
I just tested this with a 8-second, 35MB mp4 video.
The "don't do this" command made a crappy looking 316MB gif.
The suggested pair of commands, using the palette file, made a 57MB very nice looking gif.
Seems legit to me but I'm not, as you say, an expert.
that's still massive, an animated webm will probably be more useful
I mean, it's still going to have the pants beaten off it by WebM or AVIF for anything originating from a video camera.
GIF was just never intended to be a video format. I have a hard time thinking of something where it's really competitive. Maybe if you had a recorded lossless video of a small-palette video game, like, NES era or earlier, then GIF might be a solid choice. I'd still think that APNG or MNG would probably outperform it.
GIF animations really only got a boost because there was a period of time when it was all that browsers could display.
EDIT: Also, if one is using GIF...I dunno if ffmpeg does this by default, but most video formats have I-frames and then frames that depend on those. When seeking, a player will seek to the nearest prior I-frame and then decode from there.
I don't believe that GIF 89a has a formal concept of I-frames, because the format was never intended for real video. But it is possible to create frames in a GIF 89a animation with transparent areas that don't differ from the prior frame, and this achieves some of the efficiency benefits that a video format would get. I know that there have been GIF 89a conpressors that will do this. The downside is that it kills seekability, since after a seek in a player thst just starts drawing from the current frame, you'll see only some of an image until the next time that a pixel in a frame is non-transparent and gets redrawn. But for applications where you don't care about seekability, that may help mitigate some of GIF's limitations for animations.
In all honesty, though, the right answer for video is almost always "use a newer format than GIF".
Don't get mad at people for using logical command line switches.
Get mad at ffmpeg for trash defaults.
As much as everyone likes to trash on it, this is part of what webp is for. Animated, loopable images at super small sizes that display on just about anything that runs a browser.
I wish the article had examples. It would be cool.
There is this older tutorial from 2015 that goes into more detail and includes examples.
ffmpeg <3 good info here, also give Gifsicle a look if you need help getting your gifs smaller


I always liked to use Photoshop with the 'save for web (legacy)' export. Gives you a handy preview of how big it will be and lots of options.
Really interesting and useful read, thanks.
A lot of that is mostly the fault of the technology. But we still like it anyway.
Gif is indeed a shit format for the purpose.
Video codecs are downright magical and everything down to your average toaster packs a hardware decoder for h264, so this is the bare minimum we should actually be using for this use-case.
I know that's hyperbole, but I'll be cold in the ground before a "smart" toaster is allowed in this house.
Nope

Nobody: zzzzz
Me reading about 256 bit color conversion at 3 am: 🤔🥱🤓🤷💀🐩