Twitter Video File Size Limit: Four Official Numbers

X caps video uploads at 512MB for free accounts and 16GB for Premium subscribers — if you read the help centre. Three other official X pages publish different figures. All four are live and all four are quotable, so the figures are set out side by side below rather than reconciled — check the current limit in the official documentation for the account you upload from.

That is the honest answer to "what is the Twitter video file size limit," and it is more useful than a single confident figure, because which number applies depends on which upload path you are using — the web composer, Media Studio, or the API.

The limits, at a glance

Every row below is a verbatim figure from an official X page, with the page it came from.

The free-account line most people quote comes from the help centre video page: "If you aren't a Premium subscriber, you can still upload videos up to 140 seconds long with a maximum file size of 512MB."

The Premium line on that same page reads: "Premium subscribers are able to upload videos shorter than 4 hours at 1080p with a maximum file size of 16GB." It adds a resolution condition that is easy to drop: "Premium subscribers are also able to upload videos above 2 hours and under 4 hours at 720p with a maximum file size of 16GB."

Then About X Premium describes the same benefit as "up to ~3 hours long and up to 8GB file size (1080p) (on x.com and X for iOS only)" — half the size ceiling, an hour less, and a platform restriction the video page never mentions.

There is a fifth number, and it is the most precise one X publishes. The OpenAPI schema for the media upload initialize endpoint defines total_bytes with maximum: 17179869184. The prose on the same developer docs says the endpoint "accepts total_bytes up to 16 GB," and warns that "passing a larger total_bytes than the account is allowed to upload fails at initialize or finalize." So the machine-readable cap and the written cap are stated in different units, and neither page reconciles the two.

Why the pages disagree

Only one of the four explains its own scope, and it is the Media Studio page. Its upload specifications open with a disclaimer worth reading twice: "These instructions are only valid for Media Studio, and should not be followed for usage of the X developer API, Pro Media API, desktop upload, or mobile upload."

That accounts for one of the 8GB figures. It does not account for the other, because About X Premium is describing the ordinary subscriber benefit, not Media Studio, and it still says ~3 hours and 8GB.

The developer documentation adds its own wrinkle. It states that "post-video caps match the X app," and that limits "follow the authenticated user (X Premium / verified status), not your developer API plan." Yet the free-account row in that same table says 20 minutes and 8 GB, where the help centre says 140 seconds and 512MB. Both are official; the scopes are described as the same; the numbers are not. Neither page says which one supersedes the other, so check both against your own account before relying on either.

The practical reading: treat 512MB / 140 seconds as the figure to plan against on a free account, because it is the smallest published cap and the one the help centre gives to ordinary users, and check the current limit in the official documentation before you rely on anything larger.

What to do when your file is over the cap

X's own advice is to reduce the bitrate. The Media Studio troubleshooting entry for "Upload failed" says the error "can appear for a few different issues: file size, resolution, encoding settings, or a connection issue," and that "reducing the video bitrate of the file is the easiest solution for making a smaller file size."

The X Ads upload guide goes further, and this sentence is the one to remember: "Even if your file is under our maximum size, we may still have issues ingesting the file. Reducing the size of the file reduces the time of the upload, maximizing your chances for success."

So re-encoding is not only for oversized files. It is also X's published remedy for uploads that fail without an obvious reason.

Try it right here

Runs in your browser. Your file is not uploaded anywhere.

Loading tool…

This runs entirely in your browser tab — the file is read from disk, re-encoded locally, and handed back. Nothing is uploaded to a server, so there is no second upload limit between you and fixing the first one. If you want the reasoning behind the settings rather than a preset, see how to compress a video without losing quality, or open the compressor on its own page.

Platform and path gotchas

Direct messages are a separate rulebook. The developer docs list dm_video at 140 seconds and 512 MB by default, and 10 minutes / 1 GB for Premium. Post limits do not carry over to DMs in either direction.

Android is capped lower for Premium subscribers. The longer-videos page states it plainly: "Subscribers can upload videos up to 4 hours long (1080p) on x.com and X for iOS. Subscribers can upload videos up to 10 minutes long on Android." That page gives a duration but no accompanying file size. Note the condition — this is a Premium restriction. Free accounts get their 140 seconds "on any platform."

MOV files stall more often. On processing failures, X writes: "This happens most often with .mov files. If possible, re-export files as .mp4, which should allow for overall faster upload and processing time." If your source came off an iPhone or a Mac editor, MOV to MP4 does that conversion locally.

A finished upload can still be rejected. The developer docs state that "upload limits and Post-create limits are separately enforced," and that a media ID which finalized successfully can still be refused at post creation, with a 403 reading "This user is not allowed to post a video longer than 20 minutes." That is the documented mechanism behind a progress bar reaching 100% and then failing.

"Video too long" may not be about length. X's own troubleshooting says of that error: "This error usually appears when uploading media that isn't in a supported format."

FAQ

What is the Twitter video file size limit for a free account? X's help centre states 512MB with a 140 second duration cap. X's developer documentation lists the default post-video cap as 8 GB and 20 minutes. Both pages are official and current; the 512MB figure is the conservative one to plan against.

How large a video can X Premium subscribers upload? It depends which official page you read: 16GB and shorter than 4 hours on the help centre video page, ~3 hours and 8GB on the About X Premium page, and 125 minutes with 16 GB in the developer docs. Check the official documentation for the value that applies to your account.

Why did my upload fail when the file was under the limit? X says this happens: "Even if your file is under our maximum size, we may still have issues ingesting the file." Its published fix is to re-export at a lower bitrate. Codec and container also matter — the Media Studio spec accepts .MP4 and .MOV only, and that spec applies to Media Studio, not to web or mobile uploads.

Does X support H.265 or HEVC video? X's official documentation does not state this either way. The help centre only says you will be prompted if the video is not in a supported format, without listing formats. Re-encoding to H.264 MP4 avoids the question entirely.

Is there a limit on how many videos I can post? The Premium longer-videos page says: "There is no limit to the number of videos you can upload, even if all videos are the maximum length."

Do image and GIF limits work the same way? No. The developer docs list images at 5 MB and animated GIFs at 15 MB, with subtitle files capped at 1 MB. Those are separate ceilings from video.

---

Figures cited from X's help centre, Media Studio documentation, X Ads guidance and the X API media documentation, checked 16 September 2026. Where those pages disagree, both figures are reproduced above rather than reconciled. More platform caps in limits, and the browser-side tools in all Clapr tools. Related: Instagram Reels file size limit.