Your video looking softer on X than it did in your editor is documented behaviour, not a glitch. X writes, in its own help centre, that it may change the resolution and bitrate of what you uploaded — and its developer documentation ties 1080p playback to whether the uploading account is subscribed.
That makes this one of the rare "why does it look bad" questions with an actual paper trail. Below is what X states, with the scope of each statement attached, and the parts it does not state at all.
What X says it does to your video
The clearest statement is in the help centre page about longer videos for Premium subscribers, under the question of whether quality is affected. Verbatim:
"We strive to maintain the highest possible video quality for all videos uploaded to our platform. However, we 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."
Two things in that sentence matter more than the rest.
"modifying the resolution and bitrate of the original video" — X is telling you outright that the file you uploaded is not the file that gets served. The developer documentation says the same thing more briefly: "All uploads are processed for optimization across multiple platforms."
"based on the speed and stability of the viewer's internet connection" — part of what a viewer sees is decided on their end, not yours. A clip that looks fine on your desk can look worse to someone else on the same post, and nothing you re-export changes that half of it.
What X does not publish anywhere in its public documentation is the encoder it uses, the bitrate ladder, or the specific parameters applied to your upload. If you need those numbers, check the official documentation — they are not something to take from a third-party blog.
The part that explains most complaints: 1080p playback follows the subscription
This single line is in X's developer documentation, under the recommended video resolutions. Verbatim:
"Subscribed users can upload a 1080p video and get 1080p playback. Unsubscribed users can upload a 720p video and get a 720p playback."
So the answer to "why does my 1080p export look like 720p" has an official half: 1080p playback is stated as something subscribed accounts get. The same page's recommended resolutions are 1280x720 (landscape), 720x1280 (portrait) and 720x720 (square).
Be careful about the other half. X's documentation does not state what happens when an unsubscribed account uploads a 1080p file — whether it is downscaled, and to what. Anyone giving you a specific number for that is not quoting X.
Duration matters too, and it cuts across subscribers as well. The Premium longer-videos page states: "Videos above 2 hours and under 4 hours must be at 720p and should not exceed 16GB file size." Other official X pages publish different duration and size figures for Premium accounts, so check the official documentation for the one that applies to how you upload — a fuller breakdown is in X video length limits by account tier.
The fastest fix: match X's own recommended encode
You cannot control X's processing. You can control what you hand it, and X publishes what it wants. From the developer documentation's recommendations, verbatim:
- 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 - Aspect Ratio:
16:9(landscape or portrait),1:1(square)
One inconsistency worth knowing before you act on that list: the same page also carries an upload recommendation table where the 1280x720 row lists a video bitrate of 2048K and audio of 128K. That is a different number from the 5,000 kbps minimum above, on the same page. The table is introduced with "each row represents an upload recommendation, but is not a requirement." Take both as published and do not average them.
X's advertiser help page is blunter about what to do when a file misbehaves. Verbatim:
"Re-export your video file in a smaller size. An easy way to do this is to reduce the bitrate. Even if your file is under our maximum size, we may still have issues ingesting the file."
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
This runs inside your browser tab — the file is read from disk, re-encoded locally and handed back, so nothing is uploaded to a server on the way to fixing an upload. Use it to land on a clean H.264 MP4 at a sane bitrate before X's own processing gets a turn. If you want the tool on its own page, it is at compress video.
Other causes, in order of likelihood
Your source breaks one of X's hard constraints. The developer documentation lists requirements that have nothing to do with file size, verbatim: pixel aspect ratio "must have 1:1"; "Only YUV 4:2:0 is supported" for pixel format; 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". X states these as requirements but does not state what happens when a file misses one, so treat them as a checklist for your export settings rather than as a diagnosis.
You are comparing against the wrong ceiling. X publishes two different sets of maximums. The help centre, under a question explicitly about videos "uploaded on the web", lists maximum resolution 1920 x 1200 (and 1200 x 1900), maximum frame rate 40 fps and maximum bitrate 25 Mbps. The developer documentation, describing API uploads, says dimensions "must be between 32x32 and 1280x1024" and frame rate "must be 60 FPS or less". These are different upload paths; do not mix the two lists.
You edited a scheduled post. X's Media Studio documentation states: "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." If your quality dropped after an edit rather than after the original upload, that is the documented explanation.
Your source is a MOV that struggled to process. Writing about stalled processing in Media Studio, X notes this happens "most often with .mov files" and advises: "If possible, re-export files as .mp4, which should allow for overall faster upload and processing time." Converting with MOV to MP4 takes one pass.
How to tell it worked
Check playback on a full-screen desktop view rather than an inline mobile autoplay, and check it on a connection you trust — X states the served resolution and bitrate adapt to the viewer's connection, so a bad first look on patchy mobile data is not a verdict. Then compare against the subscription line above with its scope attached: X states that subscribed users uploading a 1080p video get 1080p playback, and that unsubscribed users uploading a 720p video get a 720p playback. What an unsubscribed 1080p upload turns into is not something X's official documentation states, so check the official documentation rather than treating any specific number as settled.
FAQ
Why does my 1080p video look blurry on X? X's developer documentation states that subscribed users get 1080p playback and unsubscribed users uploading 720p get 720p playback. X does not publish what happens to a 1080p upload from an unsubscribed account, so the specific downscale target is not documented.
Does X compress every video? X states it may modify the resolution and bitrate of your original video, and that "All uploads are processed for optimization across multiple platforms." The exact encoder settings are not published.
What bitrate should I export at for X?
X's recommendations page lists a minimum video bitrate of 5,000 kbps and a minimum audio bitrate of 128 kbps, while a table on the same page recommends 2048K video for a 1280x720 upload and calls those rows "not a requirement." Both figures are official.
Will uploading a bigger file preserve more quality? Not necessarily. X states that "Even if your file is under our maximum size, we may still have issues ingesting the file," and recommends reducing the bitrate and re-exporting. Size limits by account tier are covered in X video file size limits.
Does the quality drop depend on the viewer? Partly, yes. X's wording is that resolution and bitrate may be modified "while streaming based on the speed and stability of the viewer's internet connection."
Quotations are from X's help centre and developer documentation as recorded on 16 September 2026. X publishes different figures on different pages for several of these limits — verify against the official page for the surface you upload through. More walkthroughs are in the fix guides, and every browser-side compressor and converter is listed under all Clapr tools.
