Loading…
HD X video downloader
Every resolution the post holds is listed with its exact dimensions, and the best one is selected for you. What that maximum is depends on the upload, not on the downloader.
The top option is pre-selected. Step down a rung if you are on mobile data or need a smaller file.
"Download in HD" is the most common promise in this category and the one most often broken. The honest version is simple: you can have the best file the platform holds, and nothing beyond it. This page explains what decides that ceiling, why no tool can raise it, and how to pick between the options you do get.
When someone uploads a video, X does not store the file it receives. The video is decoded and re-encoded into a set of renditions at descending resolutions, so playback can adapt to whatever connection the viewer has.
A phone on a weak signal gets a low rung. A desktop on fibre gets the top one. The player switches between them mid-playback as bandwidth changes.
Those renditions are the complete set of files that exist for that post afterwards. The original upload is discarded. When a downloader shows you resolution options, it is showing you the rungs of that ladder, nothing more and nothing less.
Critically, the ladder is built downward from the source. If someone uploaded a 720p video, the platform generates 720p, 360p and perhaps 270p. It does not generate 1080p, because the pixels for it were never captured.
All four are fixed at upload time and cannot be changed afterwards.
The hard ceiling. Nothing in the ladder can exceed what was uploaded. A screen recording made at 480p yields a 480p top rung, permanently.
Mobile apps have historically compressed video before upload to save the user's data. The platform then receives an already-degraded file and transcodes that. Uploading the same video from a desktop browser generally produces a noticeably better top rendition, because the platform receives more to work with.
Premium subscriptions permit longer and higher-resolution uploads. Posts from subscribing accounts more often carry a 1080p rung, where posts from standard accounts commonly stop at 720p.
Platform limits have risen over the years. A video posted in 2016 reflects 2016's ceiling permanently, regardless of what the account could upload today. This is why old posts so often offer only one small option.
A downloader can only hand you a file that exists. When a site offers 4K for a post whose best rendition is 720p, one of two things is happening.
Either it is upscaling, which enlarges the frame while inventing the new pixels by interpolation. The result has more pixels and no more detail. In practice it looks softer than the original, because interpolation smooths edges that were sharp.
Or it is mislabelling, serving the same 720p file under a 4K label and relying on you not to check the properties.
Neither adds anything. The same applies to any "enhance" or "AI upscale" option offered mid-download: whatever it produces, it is not the platform's file, and it is not more faithful to the original.
This is also why your own uploads come back looking worse than your export. The platform re-encodes on arrival, and that pass is lossy. The full explanation is here, including what to change before uploading.
Renditions are labelled by pixel dimensions, width first. Vertical video inverts them: a phone-shot clip appears as 720x1280 rather than 1280x720. The larger number is still the long edge.
| Resolution | Common name | Typical bitrate | 30 seconds | Best for |
|---|---|---|---|---|
| 1920x1080 | Full HD | 4,000-6,000 kbps | 15-22 MB | Editing, archiving, large screens |
| 1280x720 | HD | 1,500-2,500 kbps | 6-9 MB | The usual maximum, fine everywhere |
| 640x360 | 360p | 600-900 kbps | 2-3 MB | Phone viewing, mobile data, messaging |
| 480x270 | 270p | 300-500 kbps | 1-2 MB | Old or heavily compressed uploads only |
Bitrates are ranges because the encoder varies them with content complexity. A static talking head sits well below the top of its band; a handheld shot of moving foliage pins to the ceiling.
Loosely, and the terms are used inconsistently across the industry. "HD" generally means 720p or better. "Full HD" means 1080p specifically. On this platform 1280x720 is the common maximum, so most video described as HD here is 720p rather than 1080p.
Resolution counts pixels. Bitrate decides how much data describes those pixels each second. Of the two, bitrate is usually what you actually notice.
A 1080p file at 1,500 kbps looks worse than a 720p file at 4,000 kbps, because the 1080p version does not have enough data to describe its own pixels. Detail survives in still areas and collapses wherever there is motion.
The practical rule: when two options list the same resolution, take the larger file. The extra bytes are extra detail.
H.264 encodes the difference between consecutive frames. Anything that defeats that prediction consumes the bitrate budget quickly, and those are exactly the videos where a lower rung looks poor.
A static talking head at 360p is perfectly watchable. A handheld shot of trees at 360p falls apart. This is worth knowing when deciding whether to step down a rung.
File size follows bitrate and duration rather than resolution directly:
file size (MB) = bitrate (kbps) x duration (seconds) / 8000
A 30-second clip at 2,000 kbps lands around 7.5 MB. A two-minute clip at the same bitrate is roughly 30 MB. Doubling the duration doubles the size; doubling the resolution roughly triples the bitrate needed to hold the same perceived quality.
Storage is cheap and quality is not recoverable later. You can always compress a good file. You cannot restore a bad one.
On a phone screen the difference between 720p and 360p is far less visible than the difference in transfer time and data used.
Two situations produce a single-rung ladder.
The source was already small. If someone uploaded a 360p video, there is nothing to build below it worth generating, so the platform stores one rendition.
The video is very short. For clips of a few seconds, the bandwidth saved by a lower rung is negligible, so the platform sometimes skips generating one.
In both cases the single option is the best that exists, and it is what you get.
A common report: the video looked crisp in the app, but the downloaded file seems softer. Usually one of three things is happening.
Screen size. On a phone, a 720p video is displayed at roughly a third of its native size, which hides compression artefacts. Opened full screen on a laptop, the same file is shown at or above native size and the artefacts become visible. The file did not change; the display did.
Rendition mismatch. The player streams the best rendition your connection supports, which is often the same file offered for download. If 1080p is not in the download list, no 1080p rendition exists, and the player was not showing you one either.
A lower rung was chosen. If the download list offered several options and a lower one was selected, that is the difference.
Not meaningfully. Upscaling software can enlarge the frame and some tools do a reasonable job of sharpening edges, but the detail was discarded when the platform compressed the video and cannot be reconstructed. What upscaling produces is a plausible guess, not recovered information.
Starting from the highest rendition available is the only real lever, which is why the top option is preselected here.
For the container and codec side of the picture, see the MP4 page. For a fuller treatment of compression and bitrate, read how video quality works on X. If a download fails rather than disappoints, the troubleshooting guide covers every cause.
Questions
Only if a 4K rendition exists, which is rare. The highest option shown is the highest file the platform holds. Any site promising 4K for a post that tops out at 720p is upscaling, adding pixels without adding detail.
Because that is the best rendition generated at upload. A low-resolution or heavily compressed source produces a short ladder, and the platform never builds upward from what it received.
The player shows the best rendition your screen and connection support, which is often the same 720p file offered here. If 1080p is missing from the list, no 1080p version was ever created.
Loosely. HD usually means 720p or better, and Full HD means 1080p. On X, 1280x720 is the common maximum, so most videos described as HD are 720p rather than 1080p.
Not necessarily. Bitrate matters as much, a 720p file at a high bitrate can look cleaner than a starved 1080p one. When two options share a resolution, the larger file is the better one.
Not meaningfully. Upscaling software can enlarge the frame, but the detail was discarded when the platform compressed the video and cannot be reconstructed. Starting from the highest rendition is the only real lever.
More pixels need more data. A 30-second clip at 1080p is often 15 to 22 MB, while the same clip at 360p is 2 to 3 MB. On mobile data, stepping down one rung saves considerable transfer time.
Related pages
Why the download is already an MP4, what H.264 and AAC mean, and why converting afterwards usually costs you quality.
GuideHow the rendition ladder is built, why bitrate matters as much as resolution, and how to estimate file size in advance.
BlogWhat the platform's re-encode discards, which footage suffers most, and how to export so more of it survives.
Main toolThe full downloader with every resolution listed, plus how the tool reads a post and what it can and cannot access.
DesktopThe desktop workflow where large HD files are easiest to handle, and why a website beats a browser extension.
TroubleshootingLarge files that stall, downloads that open in a tab, and every other failure with the fix for each.