That "GIF" is an MP4 in disguise
Since 2014, X has converted every uploaded animated GIF into a silent, looping H.264 MP4 at the moment of upload. The GIF label is purely cosmetic — a UI convention left over from the days when the platform really served GIF files. What travels through its CDN today is an ordinary video container. You can confirm it in any browser: open a post with an animation, inspect the media element, and you will find a <video> tag pointing at an .mp4 URL rather than an <img> tag pointing at a .gif.
Why the MP4 looks so much better
GIF is a 1987 format: 256 colors, no inter-frame compression, every frame stored in full. The same animation as an MP4 uses modern video compression — 24-bit color plus delta frames — which is why the platform's version shows smooth gradients where a true GIF would band and posterize. Downloading the post's MP4 gets you that higher-fidelity file instead of a lossy GIF conversion made by a third-party tool.
- Color: 24-bit in the MP4 versus a 256-color palette in GIF.
- Compression: delta frames between images versus none at all.
- Audio: none in either, but the MP4 is a fraction of the size.
The size gap is lopsided too
The gap is easy to measure. We took one 12-second 1080p source and rendered it twice at 480 pixels wide and 15 fps — a typical GIF size — once as a 256-colour GIF and once as H.264:
- GIF: 2.3 MB for 12 seconds.
- The same frames as H.264 at CRF 28: 132 KB.
- That GIF re-wrapped into MP4: 148 KB — 12% larger than encoding from the source, because the palette damage is already baked in.
Fifteen times the size, for 256 colours and visible banding. The conversion penalty is the part most people miss: once an animation has been through the GIF palette, no later encoder can recover the gradients that were discarded — which is exactly what happens when a post is uploaded as a GIF and converted back.
Why X still labels it a GIF
When the GIF picker shipped in 2015, users expected an animation tool, not a video uploader, so the name stuck even after the backend settled on MP4. The platform has stored animated uploads as silent looping H.264 ever since; the player mutes them and loops them. The name is a UI convention, the file is a video.
What to do about it
Save the MP4. It plays everywhere modern GIFs play — every browser and social platform converts them anyway — it is smaller, and it is the exact file the uploader's animation became. If you genuinely need a .gif for a legacy destination, convert it locally from the MP4, so you control the palette and frame rate instead of trusting a converter of unknown quality.
Troubleshooting
- You got a .gif back: a legacy converter was in the chain — fetch the MP4 instead.
- The file will not loop: looping is the player's job; the MP4 itself is silent and continuous.
- The file is enormous: you saved a real GIF — download the MP4 again.
- There is no audio: expected, since X animations are silent by design.
Frequently asked questions
- Is an X "GIF" actually a GIF? No, it is a silent MP4.
- Why is the MP4 both smaller and sharper? Modern compression against a 1987 format.
- Can I post the MP4 where a GIF is expected? Most platforms convert it automatically.
- Which file should I keep? The MP4 — it is the highest-fidelity version that exists.