Best Bitrate for X (Twitter) Video: 4 Official Numbers

Sep 25, 2026

There is no single official "best bitrate" for X video — X's own documentation publishes at least four different bitrate numbers, and two of them sit on the same page. This guide shows you where each number comes from, which upload path it applies to, and how to pick one and export against it.

You will need an encoder or editor where you can set video bitrate, resolution and codec by hand, and you need to know which way you are uploading: the x.com web composer or a mobile app, Media Studio, or the API.

Before you start

Three things decide which number is yours.

1. Your upload path. X's pages are scoped, and one of them says so explicitly. The Media Studio Library page opens its spec list with: "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." So a Media Studio number is not a web-upload number.

2. Your subscription. X's developer best-practices page states: "Subscribed users can upload a 1080p video and get 1080p playback. Unsubscribed users can upload a 720p video and get a 720p playback." That determines the resolution you should be encoding for, and resolution drives bitrate.

3. The fact that X re-encodes anyway. The same page says "All uploads are processed for optimization across multiple platforms." The help centre spells out what that can include: X "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." You are choosing the input to a transcoder, not the bitrate viewers receive.

The four numbers, and where each comes from

NumberSource pageWhat it is scoped to
Minimum Video Bitrate: 5,000 kbpsX API media best practices, "Recommended" listA developer-docs recommendation for uploads
2048K at 1280x720Same page, "Additional Information" tableA per-resolution upload suggestion, explicitly optional
Maximum bitrate: 25 MbpsHelp centre video FAQVideos "uploaded on the web"
Recommended video bitrate: 5-8 mbpsMedia Studio Library, "Encoding"Media Studio only (see the scope quote above)

The first two are the interesting pair, because they are on the same page and point in opposite directions. The Recommended list says "Minimum Video Bitrate: 5,000 kbps". Further down, the same page prints a table of per-orientation suggestions whose landscape 1280x720 row reads 2048K video bitrate and 128K audio bitrate, with 640x360 at 768K and 320x180 at 256K. Portrait 720x1280 and square 720x720 also read 2048K.

That table is prefaced with a caveat you should not drop: "In the table below each row represents an upload recommendation, but is not a requirement. All uploads are processed for optimization across multiple platforms." So one is framed as a floor and the other as a non-binding suggestion — but a 720p file at 2048K is under the stated 5,000 kbps minimum. X's documentation does not reconcile the two, so check the current guidance in the official documentation before treating either as a hard rule.

The 25 Mbps figure is a ceiling, not a target, and it comes with a limit set that belongs to web uploads specifically. That FAQ answer lists: minimum resolution 32 x 32, maximum resolution 1920 x 1200 (and 1200 x 1900), aspect ratios in the "1:2.39 - 2.39:1 range (inclusive)", maximum frame rate 40 fps, maximum bitrate 25 Mbps.

Step 1: Set resolution before bitrate

X's recommended resolutions are 1280x720 (landscape), 720x1280 (portrait) and 720x720 (square), with recommended aspect ratios of 16:9 (landscape or portrait) and 1:1 (square). That subscription sentence is narrower than it looks: subscribers who upload 1080p get 1080p playback, unsubscribed users who upload 720p get 720p playback. It does not say what an unsubscribed 1080p upload comes out as — check the official documentation. Result: you now know which row of the suggestion table applies.

Step 2: Pick your bitrate from the row that matches your path

Posting from the web or an app, use the developer-docs pair as a range rather than a point: somewhere between the 2048K suggestion for your resolution and the 5,000 kbps minimum. Uploading through Media Studio, use its own "5-8 mbps". In every case stay under the 25 Mbps web ceiling. Result: a number you can type into your encoder.

Step 3: Match the codec and audio settings

X recommends "Video Codec: H264 High Profile", "Frame Rates: 30 FPS, 60 FPS", "Audio Codec: AAC LC" and "Minimum Audio Bitrate: 128 kbps". Media Studio's encoding line agrees on the codec family — "AVC encoding (H264)", "stereo/mono AAC (LC)", maximum framerate 60 FPS. Note that the web-upload FAQ caps frame rate at 40 fps, so 60 fps is a developer-docs and Media Studio number.

Step 4: Clear the constraints that have nothing to do with bitrate

These are listed as "must" on the developer best-practices page, and a file can fail all of them at a perfectly reasonable bitrate: pixel aspect ratio must be 1:1; "Only YUV 4:2:0 is supported"; audio "must be AAC with Low Complexity profile" and "(High-Efficiency AAC is not supported)"; audio "must be mono or stereo, not 5.1 or greater"; the file "Must not have open GOP" and "Must use progressive scan". Result: no silent rejection from a 4:2:2 master or a 5.1 mix.

Step 5: Check the file size your bitrate produced

Bitrate times duration is file size, and X enforces size separately from everything above. If you are near a cap, X's own advice is to drop the bitrate: the Media Studio troubleshooting entry says "reducing the video bitrate of the file is the easiest solution for making a smaller file size", and the X Ads upload page adds "Even if your file is under our maximum size, we may still have issues ingesting the file." Caps differ by account tier and upload path — see X video file size limits for the numbers.

Try it right here

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

Loading tool…

That runs in your browser tab: the file is re-encoded locally instead of being sent to a server, which is the point when the whole reason you are re-exporting is that an upload failed. If your source is a QuickTime file, MOV to MP4 handles the container in the same pass — X's Media Studio page notes upload trouble "happens most often with .mov files" and advises "re-export files as .mp4". For a plain size reduction with no other changes, compress video is the direct route.

Common mistakes

  • Treating 25 Mbps as a target. It is the maximum listed for web uploads, alongside the 40 fps and 1920 x 1200 caps in the same answer — not a recommendation.
  • Mixing the web numbers with the API numbers. The developer docs state dimensions "must be between 32x32 and 1280x1024", frame rate "must be 60 FPS or less", aspect ratio "must be between 1:3 and 3:1". The web FAQ's figures are different in three of four rows. Quote one set at a time.
  • Applying Media Studio's 5-8 mbps to a phone upload. Media Studio's spec list explicitly excludes desktop and mobile upload.
  • Reusing livestream bitrates for file uploads. X's Live Studio encoder table (12 Mbps recommended, 40 Mbps maximum) and the X Ads stream spec (9Mbps recommended, 12Mbps maximum) are for RTMP streaming, a different pipeline.
  • Expecting your bitrate to survive. X says it processes all uploads for optimisation, so the delivered bitrate is not yours.

FAQ

What is the best bitrate for X (Twitter) video? X does not publish one. Its developer docs list a 5,000 kbps minimum and, on the same page, a 720p suggestion of 2048K; Media Studio says 5-8 mbps; the web FAQ caps you at 25 Mbps. Pick the number scoped to your upload path and stay under the ceiling.

Why does X list both 5,000 kbps and 2048K? Both appear on the X API media best-practices page — one in the "Recommended" list as a minimum, one in a per-resolution table that is prefaced "is not a requirement". X does not explain the gap, so check the official documentation for current guidance.

Does a higher bitrate mean better quality on X? Not necessarily. X states it processes all uploads for optimisation and may modify resolution and bitrate during streaming based on the viewer's connection, so past a point you are only making the upload bigger and slower.

What bitrate should I use for 1080p on X? X's recommended resolution list stops at 1280x720 and its per-resolution table has no 1080p row. It does say subscribers who upload 1080p get 1080p playback. For a 1080p bitrate figure, check the official documentation.

My upload failed — will lowering the bitrate help? X says it can. The Media Studio troubleshooting page calls reducing video bitrate "the easiest solution for making a smaller file size", and the Ads upload page notes files under the maximum size can still fail to ingest and recommends re-exporting smaller.


More export-settings walkthroughs are in the how-to guides, and every browser-side converter and compressor is listed on all Clapr tools. Bitrate figures cited from X's help centre, X API media best-practices and Media Studio pages, checked 16 September 2026 — verify against the official pages before relying on them.

Clapr team

Clapr team

Best Bitrate for X (Twitter) Video: 4 Official Numbers | Clapr Blog