Download X videos as MP4 files

Every video download from X arrives as an MP4. Not because this tool converts anything, but because MP4 is the only progressive format the platform stores. Understanding why that is, and what it means for the file you end up with, answers most of the format questions people arrive with.

Container and codec are not the same thing

Two terms get used interchangeably in this area, and separating them clears up most confusion about video formats.

The container is the wrapper. MP4, MOV, MKV, WebM and AVI are containers. A container holds the video track, the audio track, subtitles if present, chapter markers, and metadata such as duration and creation date. It determines the file extension. It does not, by itself, determine picture quality.

The codec is the compression method operating inside the container. H.264, H.265, VP9 and AV1 are video codecs. AAC, MP3, Opus and FLAC are audio codecs. The codec decides how the picture and sound are encoded, how efficiently they compress, and which devices can decode them.

This is why "MP4" alone tells you very little. An MP4 can contain H.264, H.265 or AV1 video. A file that plays fine on one device and fails on another usually has the same container and a different codec.

X standardises on one combination: the MP4 container, H.264 video, AAC audio. Every upload is transcoded into that combination regardless of what was sent.

Why H.264 and not something newer

Newer codecs compress considerably better. H.265 reaches similar quality at roughly half the bitrate. AV1 does better still and carries no licensing cost. On paper, either would save X an enormous amount of bandwidth.

The platform uses neither for general playback, and the reason is decoding rather than encoding.

H.264 decodes in dedicated hardware on essentially every device made since around 2010. Phones, tablets, laptops, smart TVs, games consoles and set-top boxes all ship with a fixed-function H.264 decoder. That silicon does the work instead of the CPU.

The practical difference is large. Hardware decoding lets a phone play video for hours on a charge. Software decoding runs the CPU hard, drains the battery quickly and makes the device warm. On older or cheaper hardware, software decoding of a high-resolution stream can drop frames entirely.

A universally supported codec that every device decodes in hardware beats a more efficient one that some devices must decode in software. For a platform serving video to a global audience on hardware spanning fifteen years, that trade-off is not close.

For you, this is good news. An H.264 MP4 is the most broadly compatible video file in existence. It plays in every browser, every phone, every editor and every television without conversion.

What happens to your file on upload

X never serves the file it receives. On arrival, the video is decoded and re-encoded into the platform's standard format at several resolutions.

Send a MOV from an iPhone, a WebM from a screen recorder, an AVI from something older, or a ProRes master from an editor, and all of them come out the other side as H.264 MP4. The original is not retained.

This has two consequences worth knowing.

First, there is no conversion step when you download. The file has been an MP4 since the moment it was posted, so it transfers directly with no processing queue and no waiting.

Second, the quality was fixed at upload and cannot be improved afterwards. H.264 is lossy: each encode discards detail judged least perceptible. Your source was probably already encoded once by the camera or editor. The upload adds a second pass, and that pass has no access to what the first one removed.

Progressive MP4 versus HLS streaming

X delivers video two ways, and only one of them is downloadable. This distinction explains why the resolution list on a download is fixed rather than adaptive.

Progressive MP4 is a single complete file at one fixed resolution. Request it and you receive the whole video, start to finish. These are the files this tool offers.

HLS, or HTTP Live Streaming, splits the video into short segments, typically two to ten seconds each, listed in a playlist file with an .m3u8 extension. The player reads the playlist, requests segments in order, and can switch to a different resolution mid-playback as available bandwidth changes. This is what runs when you watch a video in the app.

An HLS playlist is not a video file. It is a text index pointing at dozens or hundreds of fragments. Saving one gives you a few kilobytes of text that plays nothing. Any tool offering an .m3u8 as a download either does not understand the format or is relying on you not to check.

Only the progressive renditions are offered here. That is also why the resolution choice is a list of fixed options rather than a quality slider: each option is a distinct file, not a point on a continuum.

The resolution ladder

When a video is uploaded, the platform transcodes it into several progressive renditions at descending resolutions. Those renditions are the complete set of files that exist for that post afterwards.

A typical post offers 1280x720 and 640x360. Newer posts from accounts with higher upload limits often add 1920x1080. Old or heavily compressed uploads sometimes carry only a single small rendition.

The ladder is built downward from the source and never upward. If someone uploaded a 720p video, no 1080p rendition exists, because those pixels were never captured. This is the hard ceiling that no downloader can raise.

Reading the labels

Options are labelled by pixel dimensions, width first. Vertical video inverts them: a phone-shot clip appears as 720x1280 rather than 1280x720. The larger number is still the long edge.

Bitrate matters as much as resolution

Resolution counts pixels. Bitrate decides how much data describes those pixels each second, and it is usually what you actually notice.

A 720p file at 2,000 kbps looks clean. The same 720p at 400 kbps shows blocking and smearing wherever there is motion, because there is not enough data to describe the change between frames. Both are labelled 720p.

The practical rule: when two options list the same resolution, take the larger file. The extra bytes are extra detail. A well-encoded 720p file can look better than a starved 1080p one.

Estimating file size before you download

Size follows from bitrate and duration rather than resolution directly:

file size (MB) = bitrate (kbps) x duration (seconds) / 8000

A 30-second clip at 2,000 kbps lands around 7.5 MB. The same clip at 832 kbps is roughly 3 MB.

Resolution	Typical bitrate	30 seconds	2 minutes
1920x1080	4,000-6,000 kbps	15-22 MB	60-90 MB
1280x720	1,500-2,500 kbps	6-9 MB	22-37 MB
640x360	600-900 kbps	2-3 MB	9-13 MB
480x270	300-500 kbps	1-2 MB	4-7 MB

These are ranges rather than fixed values, because the encoder varies bitrate with content complexity. A static talking head compresses far below the top of its band; a handheld shot of moving foliage sits at the ceiling.

What you can do with the file

H.264 MP4 needs no conversion for almost any purpose.

Playback

Opens in QuickTime, VLC, Windows Media Player, every browser, and any smart TV or console with a media player. There is no device in common use that cannot play it.

Editing

Imports directly into Premiere Pro, Final Cut Pro, DaVinci Resolve, CapCut, iMovie and every mobile editor. No transcode pass, no proxy generation, no waiting before you can start cutting.

One caveat for heavier editing work: H.264 is a long-GOP format, meaning most frames are stored as differences from neighbouring frames rather than complete images. That makes it efficient to store and slightly slower to scrub frame by frame. For trimming and simple edits it is irrelevant. For frame-accurate colour work, converting to an intermediate codec such as ProRes or DNxHD first is standard practice, though it will not recover quality that is already gone.

Re-uploading

Accepted natively by YouTube, Instagram, TikTok, Facebook and X itself. Every re-encode costs quality, so uploading your own master is always better than uploading a downloaded copy. Where the downloaded file is all you have, it will be accepted without complaint.

Extracting audio

The AAC track inside the MP4 can be pulled out as M4A without re-encoding, or converted to MP3 with a small quality loss. Any converter handles this. Extracting is preferable to re-encoding where the tool offers a copy or passthrough option.

When converting is worth it, and when it is not

Be sceptical of tools advertising conversion to a long list of output formats. Converting an already-compressed H.264 file to AVI, WebM or MKV does not improve anything. It re-encodes lossy material, discarding more detail on each pass, and usually produces a larger file for worse quality.

Converting is worth it in a small number of cases:

• A platform demands a specific format. Some older forums and upload systems accept only certain containers.
• You need audio alone. Extracting the AAC track is a legitimate conversion.
• You need an editing intermediate. ProRes or DNxHD for heavy colour work, as described above.
• You need a genuine GIF. Covered below, and still a downgrade.

Outside those, the MP4 you downloaded is already the correct answer.

Why GIF posts also download as MP4

This surprises people, and it is worth explaining because it looks like a bug.

When you post a GIF to X, it stops being a GIF at the moment of upload. The platform converts it to a silent, auto-looping H.264 MP4 and only labels it "GIF" in the interface.

The reason is size. The GIF format dates from 1987. It compresses each frame with a 256-colour palette and no motion prediction between frames. A three-second animation can easily reach 5 MB as a GIF. The same animation as H.264 is often under 300 KB, with a full colour range and better motion.

So a "GIF" download arrives as an MP4 with no audio track, because that is the only file that exists. Converting it back to GIF is possible but always a downgrade: larger file, 256 colours, visible banding on gradients. The GIF downloader page covers that workflow in detail.

Live video and audio Spaces

Live broadcasts behave differently while they are live. During a broadcast only HLS segments exist, because the progressive file has not been assembled yet. There is nothing complete to download.

Once a broadcast ends and is archived as a normal post, standard progressive renditions are usually generated and it behaves like any other video. If a live post fails to resolve, waiting until processing finishes often fixes it.

Audio Spaces run on a separate system and are not served as downloadable MP4s at all.

Practical guidance

Take the highest resolution offered when you are keeping the file, editing it, or watching on anything larger than a phone. Storage is cheap and quality is not recoverable later.

Step down one rung when you are on mobile data, sending through a service with an attachment limit, or saving something disposable. On a phone screen the difference between 720p and 360p is far less visible than the difference in transfer time.

Do not run the file through a converter unless something specifically requires it. For a fuller treatment of how compression decisions affect what you see, read how video quality works on X and the formats and codecs guide.