X (Twitter) Video Resolution and Aspect Ratio Limits

X publishes two different sets of video resolution and aspect ratio limits, and three of the four overlapping numbers disagree. X's help center says web uploads top out at 1920 x 1200 with aspect ratios in the "1:2.39 - 2.39:1 range (inclusive)". X's developer documentation says API uploads must have "Dimensions: must be between 32x32 and 1280x1024" and "Aspect ratio: must be between 1:3 and 3:1".

Both pages are official, and each one states the scope it applies to. The useful question is not which number is "right" — it is which page covers the path you are uploading through.

The limits, at a glance

The help center numbers come from the X videos FAQ titled "What are the limitations on video resolutions and aspect ratios that can be uploaded on the web?" It lists, verbatim:

Minimum resolution: 32 x 32
Maximum resolution: 1920 x 1200 (and 1200 x 1900)
Aspect ratios: 1:2.39 - 2.39:1 range (inclusive)
Maximum frame rate: 40 fps
Maximum bitrate: 25 Mbps

The developer documentation's media best-practices page lists its own hard constraints under "Advanced", including "Frame rate: must be 60 FPS or less" alongside the dimension and aspect-ratio lines quoted above.

Note the direction of the disagreements. The help center allows a bigger frame; the developer docs allow a higher frame rate and a more extreme aspect ratio. Only the 32 x 32 floor matches on both pages. X has no page that reconciles the two sets, so before you build an export preset around either one, check the current values in the official documentation for the path you are using.

Why the scope matters more than the number

Each spec sheet carries its own scope, written by X:

• The help center FAQ heading says these are the limits "that can be uploaded on the web".
• The developer-docs constraints sit in the X API media upload best-practices page and describe media sent through the API.
• Media Studio has a third set, and it explicitly fences itself off: "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." Its encoding table reads "Video specification: AVC encoding (H264)", "Recommended video bitrate: 5-8 mbps" and "Maximum video framerate: 60 FPS".

So there are three official spec sheets, each scoped to a different upload path, and none of them is "X's video specs" on its own. Other platforms split their rules the same way — see the platform limits hub.

What X recommends, as opposed to what it accepts

The limits above are ceilings and floors. The developer docs separately publish a "Recommended" list, which is much narrower:

• "Video Resolution: 1280x720 (landscape), 720x1280 (portrait), 720x720 (square)"
• "Aspect Ratio: 16:9 (landscape or portrait), 1:1 (square)"
• "Video Codec: H264 High Profile"
• "Frame Rates: 30 FPS, 60 FPS"
• "Minimum Video Bitrate: 5,000 kbps"
• "Minimum Audio Bitrate: 128 kbps", "Audio Codec: AAC LC"

One wrinkle worth knowing before you copy a bitrate off that page: the same page also carries an upload table, introduced with "In the table below each row represents an upload recommendation, but is not a requirement." In that table, the landscape 1280 x 720 row lists a video bitrate of 2048K. That is a different number from the 5,000 kbps minimum quoted above, on the same page. Both are verbatim; X does not say which supersedes the other.

The rejections that are not about resolution at all

The developer docs list several hard requirements that have nothing to do with frame size, and any one of them can sink an otherwise in-spec file:

• "Pixel aspect ratio: must have 1:1"
• "Pixel format: Only YUV 4:2:0 is supported"
• "Audio must be AAC with Low Complexity profile. (High-Efficiency AAC is not supported)"
• "Audio must be mono or stereo, not 5.1 or greater"
• "Must not have open GOP"
• "Must use progressive scan"

That covers 4:2:2 and 4:4:4 masters, HE-AAC audio tracks, 5.1 mixes, open-GOP exports and interlaced footage. X states these as requirements but does not publish what error you get when one is violated, so do not expect the failure message to name the cause.

What to do when your file sits outside the range

Re-encode it to something inside the range for your upload path, and reduce the bitrate while you are there. X's own advertiser guidance is blunt about why that helps even when you are not over a stated cap: "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." The suggested method on that page is "Re-export your video file in a smaller size. An easy way to do this is to reduce the bitrate."

This runs inside your browser tab — the file is read from disk, re-encoded locally and handed back, so nothing is uploaded to a third-party server on the way to fixing an upload. If you would rather steer it by hand, the video compressor lets you pick the quality level and cap the output resolution. For a QuickTime source, X's Media Studio guidance is specific: "This happens most often with .mov files. If possible, re-export files as .mp4, which should allow for overall faster upload and processing time." — MOV to MP4 does exactly that conversion.

Gotchas after the upload succeeds

Getting inside the spec does not guarantee the pixels you uploaded are the pixels viewers see. X states that playback resolution is tied to subscription: "Subscribed users can upload a 1080p video and get 1080p playback. Unsubscribed users can upload a 720p video and get a 720p playback."

X also reserves the right to re-encode: it "may modify or adapt your original video for distribution, syndication, publication, or broadcast by us and our partners and/or make changes in order to adapt it to different media, including modifying the resolution and bitrate of the original video while streaming based on the speed and stability of the viewer's internet connection."

And one specific to scheduled posts, from the Media Studio docs: "Scheduled posts can be modified on X.com, however this will create a new, lower-quality copy of the media and lose associated metadata set within Media Studio."

FAQ

What is the maximum video resolution you can upload to X? It depends which page you follow. The help center's web-upload FAQ says "Maximum resolution: 1920 x 1200 (and 1200 x 1900)". The developer docs say dimensions "must be between 32x32 and 1280x1024" for API uploads. Check the official documentation for the path you are uploading through.

What aspect ratio does X accept for video? The help center lists a "1:2.39 - 2.39:1 range (inclusive)" for web uploads; the developer docs require "between 1:3 and 3:1" for API uploads. The developer docs separately recommend 16:9 for landscape or portrait and 1:1 for square.

Can I upload a 4K video to X? Neither spec sheet lists a 4K ceiling for uploads — the stated maximums are 1920 x 1200 (web) and 1280x1024 (API). The one 4K figure in X's documentation sits in Live Studio's encoder table, where "Resolution & frame rate" is listed as 1920x1080 @ 60 fps recommended and 3840x2160 @ 60 fps maximum. That is livestreaming, not file upload.

Why does my 1080p video look soft on X? X's developer docs state it this way, verbatim: "Subscribed users can upload a 1080p video and get 1080p playback. Unsubscribed users can upload a 720p video and get a 720p playback." Read the second sentence literally — it describes a 720p upload getting 720p playback, not what happens to a 1080p upload from a non-subscriber. X does not publish that anywhere, so check the official documentation rather than assuming a number. Separately, X says it may modify the resolution and bitrate during streaming based on the viewer's connection.

Does X accept HEVC (H.265) or ProRes? X's official pages do not state this either way. They publish recommended and required settings around H.264, but no supported-codec whitelist for uploads — check the official documentation rather than a third-party list.

Need the rest of the browser-side toolkit? See all Clapr tools.

Specs quoted from X's help center video FAQ, the X API media best-practices page, Media Studio Library FAQs and X Ads upload guidance, checked 16 September 2026. X's own pages disagree on several of these numbers; verify against the page that covers your upload path before building a preset around them.