The case against GIFs in 2026
GIF is a 1987 image format. It tops out at 256 colours per frame, has no real inter-frame compression, and ships every animation as if it were a flipbook. That is why a 5 MB GIF can become a 200 KB MP4 with the same visuals — H.264 actually compresses motion, while GIF basically does not. The original argument for GIFs ("they autoplay everywhere, video does not") stopped being true years ago. Slack, Twitter, Discord, iMessage, Notion, and most modern CMSes all autoplay short MP4s the same way they autoplay GIFs.
What this tool does, exactly
We re-encode the GIF's frames to H.264 at CRF 23, force yuv420p pixel format for hardware-decoder compatibility, and wrap the result in MP4 with +faststart so it begins playing immediately when streamed. There is also a small but important detail: H.264 requires even pixel dimensions, and plenty of GIFs are odd-numbered (e.g. 481×271). We use scale=trunc(iw/2)*2:trunc(ih/2)*2 to round down to the nearest even pair before encoding, so the conversion never fails on an odd-sized source.
What about audio?
GIFs are silent, so the output MP4 is silent too — but unlike the GIF, you can now add audio to it later in any editor without re-converting from scratch. That is a frequently useful escape hatch: you take an existing meme GIF, convert it once, and now it can carry a soundtrack on the second pass. The reverse — adding audio to a GIF — is not a thing that exists.
Adjacent tools you might want
Going the other direction (clip → animated GIF, for the rare cases that still call for it) is MP4 to GIF. If you also need to silence an existing video for an autoplay-muted social embed, Mute video does that as a stream-copy in seconds. And if you are creating screen recordings that keep ending up as GIFs by mistake, Clipy records straight to a shareable MP4 link with no watermark — the cleanest path to modern, autoplay-friendly screen captures.