Loading…
How to download X videos
Copy the link to the post, paste it below, choose a resolution and download. The steps are the same on every device, only where the file lands afterwards differs.
Start here, then read on for the device-specific details if the file does not appear where you expect.
Saving a video from X takes about ten seconds once you know which link to copy. Getting the wrong link is what wastes the other ten minutes. This page covers the steps, the three link cases that silently fail, where the file lands on each device, and how to read an error when one appears.
That is the whole process. Everything below explains what to do when a step does not go as expected.
Worth answering because it is the first question people have.
You can save your own drafts and media within the app, but there is no option to download a video someone else posted. This is deliberate. The platform is built around keeping viewing inside the app, where it controls the experience and the advertising. Offering downloads would make it trivial to redistribute creators' work elsewhere.
The video files themselves are not hidden. They sit on the platform's media servers with real, addressable URLs, because the player has to fetch them. The interface simply never surfaces them. That gap is what tools like this close.
A usable post link has three parts: the host, the account handle, and the word status followed by a long number.
https://x.com/username/status/1234567890123456789
That final number is the post ID. It is assigned when the post is created and never changes, which is why an old twitter.com link still resolves years later.
All of these work and refer to the same post:
x.com/username/status/1234567890twitter.com/username/status/1234567890mobile.twitter.com/username/status/1234567890x.com/username/status/1234567890?s=20&t=abc, tracking parameters are ignoredEach of these produces a technically valid URL that points at the wrong thing, which is why the failure is confusing.
A URL ending in just a username identifies an account, not a post. There is no single video to resolve. The link must contain /status/ followed by a number.
The same applies to search URLs, list URLs and hashtag URLs. None of them point at one specific post.
The most common failure and the hardest to spot, because the link resolves perfectly. It just resolves to a post that holds no video of its own.
When someone reposts a video there are two posts. The original holds the media. The repost points at it. Copying from the repost gives you the reposter's post, which contains a reference rather than a file.
To fix it, tap through to the original, the post showing the original author's handle directly above the video, and copy from there. If a tool reports that a post contains no video, this is almost always the reason.
Links shared outside the platform are often wrapped in t.co. These are redirects carrying no post ID, so there is nothing to resolve.
Open the short link in a browser, let it land on the real post, then copy the expanded URL from the address bar. It will have become a normal /status/ link.
Three questions:
/status/? If not, it is not a post link.Tap the post so it opens on its own screen. Copying from a scrolling timeline sometimes grabs the post above or below the one you wanted.
Tap the share icon beneath the video, an arrow pointing out of a box, and choose Copy link. If your share sheet shows Share via instead, pick that and then choose Copy from the system sheet that follows.
Identical to iOS in the app. Tap the post, tap the share icon, choose Copy link. Some Android launchers show a system share sheet with Copy as the first option.
Two reliable routes. Click the post to open it and copy the whole URL from the address bar, which lets you see exactly what you are copying. Or use the share icon under the post and choose Copy link to post.
Avoid right-clicking the video itself and choosing Copy video address. That returns a link to a streaming fragment rather than the post, and it expires.
The download is identical everywhere. What differs is the folder your browser writes to, and whether the video reaches your photo library on its own.
Safari saves downloads to the Files app, not to Photos. It does this because a download can be any file type, and routing everything through the photo library would not make sense.
The video is on your device the moment the transfer completes. It is simply somewhere other than where most people look first.
To move it into Photos: tap the download arrow beside the address bar, tap the file, tap the share icon, choose Save Video. It then appears in your camera roll. The iPhone page covers this and the storage quirks in more detail.
Chrome saves to Internal storage > Download. Android's media scanner then indexes the file, so it usually appears in Gallery or Google Photos within seconds without any further action.
If it does not appear, the scanner missed it. Opening the Files app and tapping the video once normally triggers a rescan. A restart always does. The Android page has the detail.
The file goes to your browser's usual downloads folder. Right-clicking the download control and choosing Save link as lets you pick the destination directly, which is quicker when saving several. The desktop page covers browser differences.
Every rendition the platform holds is listed with its dimensions and estimated size, highest first and preselected.
Take the highest when you are keeping the file, editing it, or watching on anything larger than a phone. Storage is cheap and quality is not recoverable later.
Step down one rung on mobile data, when an attachment limit applies, or for something disposable. On a phone screen the difference between 720p and 360p is far less visible than the difference in transfer time.
The options differ between posts because the platform generates them at upload from whatever it received. A post offering only 360p was uploaded at 360p. The HD page explains what fixes that ceiling.
The message identifies which class of problem applies. Retrying blindly does not help for most of them.
The post ID was rejected. Four causes:
Open the link in a browser to check. If the platform itself shows an error, the post is genuinely gone.
The post exists but its data is not served publicly. Protected account, age-restricted post, or direct message media. None of these are reachable by any external tool, and being logged in yourself makes no difference, because the tool never sees your session.
The post resolved but carries no video or GIF. Usually a photo-only post, a reply where the video sits in the parent post, or a link-preview card where the video actually lives on another platform.
The post resolved and the transfer began, so the problem is the network path. Interrupted transfers leave a partial file. Switch between Wi-Fi and mobile data and retry, check available storage, or pick a lower resolution if the file is large.
The file arrived but the browser played it. Right-click, or long-press on mobile, the download control and choose Save link as or Download linked file.
On iPhone this is normal rather than an error: Safari routes downloads to Files, as described above.
Something is blocking the request before it starts.
A rate limit was hit. Wait about a minute. Rapid retries extend the wait rather than shortening it.
No. A web page does the job in any browser on any device, and the alternatives ask for considerably more access than the task requires.
A browser extension must be granted permission to read and change the pages you visit before it can add a download button. That is a permanent grant covering every site, in exchange for saving a few seconds.
A downloadable app or APK is worse. Sideloaded APKs advertised as official versions of web tools are a well-documented malware route on Android, and a native app adds a store account, a review delay between fixes and users, and a permissions dialog for access the task does not need.
If you want the convenience of a home screen icon without the exposure, the site can be installed as a web app: full screen, offline-capable, roughly 100 KB, and no device permissions.
No. The platform provides no download notification, and nothing in a post's analytics distinguishes a download from ordinary viewing.
The lookup happens on this site's server and reads the same public data that renders embedded posts on news sites. It does not register as a view on your behalf, and it does not touch the like, repost or reply counts.
This is general information rather than legal advice, and copyright law varies by country.
The video is a copyrighted work belonging to whoever created it. Uploading it to X licensed it to the platform; it did not place it in the public domain.
Generally accepted: saving a video to watch offline, keeping a copy of something you posted, saving a clip as evidence in a dispute, and short excerpts used in commentary or news where fair use or fair dealing applies.
Generally not: re-uploading someone else's video as your own, using a creator's work in advertising without permission, or monetising content you did not make. Downloading a file does not grant rights it could not grant. The safety and privacy guide covers this in more detail.
Questions
Not for other people's videos. You can save your own drafts and media within the app, but there is no option to download a video someone else posted. That gap is the reason external tools exist.
No. A web tool does the job in any browser on any device. Apps and browser extensions ask for far more access than saving a video requires, which is a poor trade for the small amount of convenience they add.
Reading the post takes about a second. After that, the transfer speed depends on your connection and the file size, most clips finish in a few seconds, and a long high-resolution video can take a little longer.
Yes. A post can hold up to four media items, and each one is listed separately with its own resolution choice and download button.
Copy the link to the reply itself. Open that reply so it fills the screen, then use the share icon on it, the link will point at the reply's own post ID rather than the parent.
There is a rate limit to prevent automated abuse, which works out at roughly twenty lookups a minute. Ordinary use never comes close to it.
Keep reading
The downloader itself, with the full explanation of how it reads a post and what it can and cannot access.
GuideEvery app and browser, plus the retweet and short-link cases that produce a valid link to the wrong post.
GuideWhy the options differ between posts, how bitrate affects what you see, and how to estimate file size first.
QualityGetting the highest resolution a post holds, and why that ceiling is set at upload rather than at download.
GIFHow animated posts differ, and why a GIF on X is really a silent looping MP4 with no GIF file behind it.
PrivacyWhat a downloader can see, whether the poster is notified, and where personal saving ends and copyright begins.