If Twitter/X videos look blurry, compare the local export with the same moment in the published video before changing settings. A soft source, a heavily compressed export, a small player and a playback problem need different fixes. Start with the earliest stage where the detail becomes hard to read.
Locate the blur before exporting again
| What you observe | First check | Useful next action |
|---|---|---|
| The camera original or screen recording is soft | Focus, motion and source detail | Use a better original or record the relevant area again |
| The original is clear; the local export is soft | Export dimensions, compression and resizing | Export a fresh copy from the editing project |
| The export is clear; only one viewing setup looks poor | Player size, connection and client | Compare the same post on another current client or connection |
| The export is clear; several viewing setups show lost detail | The uploaded file and content design | Check that you uploaded the intended export; try a short, controlled comparison |
These observations narrow the investigation. They do not reveal X's internal processing or prove that a particular codec caused the problem. A poster image or paused preview also does not establish how the moving video looks.
Inspect the source and the actual export
- Open the original recording and the exported upload file locally. Use the same scene and a similar display size.
- Inspect a still moment with text or fine detail, then a moment with motion. Look for unreadable letters, block-shaped patches and smeared movement.
- Check the export's pixel dimensions and frame rate in your editor or file inspector. A filename containing “1080p” does not verify those properties.
- Confirm that the upload file is the final export, rather than a copy sent through a messaging app or downloaded from an earlier social post.
Resolution describes pixel dimensions. Bitrate describes data used per second. Neither number alone tells you whether a clip is readable. Upscaling a small, blurred source adds pixels without recovering the original detail.
If you already use FFmpeg, its ffprobe tool can inspect a local file without converting it:
ffprobe -v error -select_streams v:0 -show_entries stream=codec_name,width,height,avg_frame_rate:format=duration,size -of json "upload.mp4"This selects the first video stream and reports its codec, dimensions and average frame rate, plus file duration and size. A rate such as 30000/1001 means approximately 29.97 frames per second. Metadata helps identify the file; it cannot grade visible quality.
Export a clean copy from the original project
Use the original recording in your editor. Keep its aspect ratio and frame rate unless the edit requires a deliberate change. For a clear 1920 × 1080 recording, an export at those dimensions is a reasonable comparison baseline. This is an editing example, not a universal X upload requirement.
Choose your editor's high-quality export option, then inspect the exported file. If the file is too large for the composer, shorten a working copy or adjust export compression and compare it locally again. Keep the master file. Repeatedly downloading, editing and re-encoding a compressed copy can introduce further loss.
For screen recordings, crop to the relevant controls, enlarge labels and slow down fast pointer movement. For camera footage, improve focus and light at capture. Raising export settings cannot repair a badly focused original.
X's video help explains upload and preview controls. Account and client limits can differ. Use the current composer's format or size message when an upload is rejected; acceptance does not guarantee a particular delivered quality.
Check playback separately from upload quality
- Open the original published post and play through the affected scene. Expand the player and compare at a sensible size.
- Check available data-use and playback controls in your current app. If a quality selector appears, record the selected option. Interface labels can change.
- Replay the same moment on a stable connection. If practical, compare Wi-Fi with another connection and compare the app with a current browser.
- Record whether the problem affects this clip or several unrelated videos. Keep the same device and player size for the first comparison.
A connection change that improves playback is useful evidence about that viewing session. It does not prove that every viewer gets a clearer version. If the upload has just finished, replay later and record the elapsed time; this guide does not promise a fixed processing delay.
Worked example: a screen recording with tiny text
Illustrative example, not a measured X experiment: you record an entire 1920-pixel-wide desktop. A label is 20 pixels high in the recording. If the video is displayed 360 pixels wide with proportional scaling, that label becomes about 20 × 360 ÷ 1920 = 3.75 pixels high. Actual player layouts vary, but the arithmetic shows why a sharp desktop recording can be unreadable on a phone.
First check the local export at that smaller width. If the label is already unreadable, increasing bitrate alone does not solve the layout problem. Record or crop to the relevant panel, enlarge the interface text and export from the original project. Inspect the revised local file before making a short upload comparison. Report the observed result rather than assuming the revision worked.
Keep a short comparison log
Use a clip you own or have permission to post. Change one factor at a time. Avoid publishing repeated full-length copies just to compare settings.
| Record | What to enter |
|---|---|
| Source and export | Filename, dimensions, frame rate and export option |
| Scene | Timestamp and the specific detail you need to read |
| Viewing conditions | Device, app/browser, connection, player size and available quality setting |
| Timing | Post URL and time since upload |
| Observation | What is readable locally and in the published version |
| Next change | One change and the reason to try it |
Preserve a readable version of the information
Keep your original and editing project as the master copies. If you need an offline copy of a post, follow the video download workflow; a downloaded platform copy may differ from your original.
Put essential steps and numbers in the post text or a linked explanation. For a detailed static diagram, use a separate readable image and consult the image placement guide. When saving the surrounding written post, a tweet screenshot records its visible context; keep the video file separately.
Sources and limits
Technical references checked October 16, 2026: How to share and watch videos on X and ffprobe Documentation. The workflow and tables are diagnostic guidance. No upload experiment was conducted for this article, and no export preset here promises to bypass platform compression.