Why does a Twitter GIF download as an MP4?

The thing labelled GIF is a video file

Twitter shows a small GIF badge on certain media, and everyone reasonably concludes there is a .gif file behind it. There is not. What sits behind that badge is a short MP4 video: no audio track, played on a loop, with the scrubber, the play button and the volume control hidden.

The badge is a label the client draws, not a description of the format. Twitter is telling you how to think about the media — silent, brief, repeating, a reaction rather than a clip — while serving the same kind of file it serves for any other video.

This happens at upload. Post an actual .gif to Twitter and it is converted to MP4 on the way in. The original GIF is not stored and not served; from that moment the only version anybody can see or fetch is video. So when a downloader hands you an .mp4, it has not converted anything or made a substitution. It has given you the file that exists.

Which resolves the complaint that brings most people here. You did not download the wrong thing, and the app did not change the format. You downloaded exactly what the tweet contained, and it was never a GIF.

• The GIF badge — a client label, drawn over an ordinary video player
• The media — a short MP4, silent, with playback controls hidden
• Your upload — converted to MP4 at upload time; the original .gif is not kept
• Your download — the MP4 that exists, not a substitute for a GIF that does not

Why Twitter swapped the format out

GIF is an image format from 1987, and it shows. It is limited to 256 colours per frame, which is why gradients in old GIFs look banded and skin tones look posterised. It has no modern compression — every frame is stored as its own image with only crude tricks between them — so a few seconds of animation can run to several megabytes. And no phone has hardware acceleration for decoding it, meaning the work falls on the processor and, in practice, on the battery.

The same animation as an H.264 MP4 is typically a fraction of the size, keeps full colour, and decodes in hardware. On a mobile timeline where dozens of these loops autoplay as you scroll, that difference is not a nicety — it is the difference between a usable feed and a hot phone.

Twitter is not unusual in this. Practically every large platform that shows looping animations does the same conversion for the same reasons. The GIF survives as a concept — short, silent, looping, reaction-shaped — long after it stopped being the file format underneath.

None of which is hidden, exactly. It is just never mentioned, because for a person scrolling a timeline the distinction does not matter. It only starts to matter at the moment you try to save one.

• 256 colours per frame — the banding and posterisation you see in older GIFs
• No modern compression — file sizes several times larger than the equivalent video
• No hardware decoding — the processor does the work, and the battery pays
• Same animation as MP4 — smaller, full colour, hardware-decoded

What that changes about the file you save

Three things about the saved copy surprise people, and all three follow from the format rather than from the app.

It plays once and stops. A GIF stores its loop instruction in the file itself, so any viewer that opens it repeats it forever. MP4 has no equivalent that ordinary players honour — the looping you saw on Twitter was the client choosing to restart playback, not a property of the file. Open the same file in your gallery and it plays through and ends. Most video players and messaging apps have a loop or repeat option if you want the original behaviour back.

It has no sound, and never did. Twitter strips audio when it converts, and the player has no volume control for a reason. If you saved something labelled GIF and there is no audio, that is correct. It also means that if a piece of media does have sound, it is not one of these — it is an ordinary video, and the Twitter video guide covers that path.

It has no transparency. GIF supports a transparent colour; MP4 does not. Anything transparent in an original was flattened onto a background at conversion, and that background is now part of the picture. This is the one that bites if you were planning to use the animation over something else.

The upside is worth stating too. What you get is smaller, sharper and better coloured than the GIF that started it, and it is an ordinary MP4 that plays and edits anywhere.

Getting it into the app

The routine is the same as for any tweet, because to a downloader this is any tweet.

The quick route is the tweet's share icon: tap it, choose Share via, and pick Savvy from the app list. The link is handed straight over and the download starts on its own. The slower route is Copy link, then open Savvy, tap the Paste button beside the link field, then tap Download. Worth repeating the precise bit: Paste is a button. It reads the clipboard once and fills the field; it does not start anything, and the app does not watch your clipboard in the background.

Link shapes are unchanged as well. x.com and twitter.com both work, along with the www and mobile variants, t.co short links, and the embed-fixer hostnames — fxtwitter, vxtwitter and fixupx — that people swap in so tweets preview properly elsewhere. What is checked is the shape rather than the domain: a single tweet's link contains /status/ and a long number. A profile or search URL has no single piece of media behind it and is refused.

One thing genuinely differs. Because these are short and silent, tweets often carry several of them, and a reply chain of reaction loops is one link per tweet rather than one link for the lot. Copy from the tweet holding the animation you actually want.

• Share to Savvy — link filled and download started automatically
• Copy link, then Paste — tap Paste to fill the field, then tap Download yourself
• x.com, twitter.com, t.co, fxtwitter, vxtwitter, fixupx — all recognised
• A profile or search URL — refused, because there is no single item behind it

What it costs, which is usually nothing

This is the cheapest category of thing you are likely to save, and the reason is the source rather than a discount.

Standard definition, up to 480p, is free in Savvy, from a daily allowance rather than any balance. Reaction loops are generally small — they started life as low-resolution animations, they are a few seconds long, and Twitter has no reason to serve them at cinema resolution. A great many of them sit at or below the free line, so you pick the option offered and pay nothing.

Where a higher rung is offered, the ordinary tiers apply, and the honest advice is to look before spending. Twitter transcodes an upload into a small ladder of renditions and the picker can only offer what is on it. For a four-second loop that began as a 480-pixel-wide animation, a higher tier buys a bigger file of the same picture rather than a better one.

• SD video, up to 480p — free, from your daily allowance
• HD and Full HD video — 10 coins, or one HD credit if you have one
• 2K video — 15 coins
• 4K video — 20 coins
• Images and audio — 5 coins

If you genuinely need a .gif file

Sometimes the extension is the requirement rather than the animation — a forum, a wiki, an email signature or an old chat client that accepts .gif and nothing else. In that case you convert, and you should know what the conversion costs.

Going from MP4 back to GIF is a downgrade in every measurable way. Colour is reduced to a 256-entry palette, so gradients band and faces go blotchy. The file usually gets larger, often several times over, despite looking worse. Any audio would be discarded, though there is none here to lose. What you gain is a file with a .gif extension that loops by itself in anything that opens it.

That trade is sometimes worth making and often is not. If the destination accepts video at all — most modern platforms and messengers do, and most replay short silent clips on a loop — keeping the MP4 is the better answer. Convert only when something genuinely refuses anything else.

Savvy does not convert. It saves the file the platform serves, which is the MP4. Conversion is a separate job for a converter tool, and doing it as a deliberate second step is better than an app quietly doing it for you and calling the result a GIF download.

Where it lands, and the rights bit

The saved file goes to your device's Downloads folder, in a Savvy directory filed by platform. It is an ordinary MP4 from there: your gallery lists it, any video app plays it, and it shares onward like anything else.

Inside the app, Library lists everything with search and filters, and Storage shows what each file occupies with bulk delete. This category accumulates faster than most — reaction loops are small, quick to save and easy to save fifty of — so the Storage screen earns its place sooner than you would think.

On the rights side, these are an unusual case. A reaction loop is frequently a few seconds lifted from a film, a television programme, a sports broadcast or someone's video, circulated so widely that its origin has been forgotten. That circulation does not make it unowned. Keeping one to send to friends is the ordinary use everyone has in mind, and nobody sensible is worried about it. Building it into something you publish or sell is a different act with a real copyright question attached, and the fact that it arrived through a tweet does not answer that question.