Why Can't I Download Twitter Videos? Causes and Fixes
If you can't download a Twitter video, the post is usually not public: it is from a protected account, has been deleted, is marked as sensitive, or is blocked in your country. The next most common causes are copying the wrong link, such as a profile or quote post, and a browser or in-app browser that refuses to save the file.
A failed download gives you almost nothing to work with, but the failures cluster into nine causes and most can be ruled out in seconds. Work down this list in order. The first five cover the overwhelming majority of cases, and once you have found yours, the Twitter video downloader will take the link.
1. The post is not public
This is the single most common cause and it is not a bug. A protected account has chosen who can see its posts, and a downloader only reads what is publicly visible. It has no session, no login and no way to see anything you can see because you are following someone.
The test takes ten seconds: open the link in a private or incognito window where you are logged out. If the post does not load there, no tool will reach it either. The same applies to posts from accounts that have blocked you, and to posts in communities with restricted visibility.
2. The post or account is gone
Deleted posts, suspended accounts and videos removed for a copyright claim all fail identically, because from outside there is nothing left to read. The timeline still shows a cached preview for a while after deletion, which is why a video can appear to exist while the underlying media has already been removed.
Again, the logged out window tells you. A deleted post returns a not found page rather than an empty player.
3. You copied the wrong link
A usable X link contains /status/ followed by a long number. That number is the post ID and it is the only part that matters.
- A profile link stops at the username and points at an account, not a video. There is nothing single to fetch.
- A quote post carries a preview of the original, not the media. Tap through to the original post first.
- A search results link or a timeline link points at a list of posts.
- A link copied from a notification sometimes goes to the notification rather than the post.
Trailing tracking text after a question mark is harmless and can be left in place. The problem is never the junk on the end, it is the part before it.
4. The post has no video to download
Some posts look like they contain video but do not. A link card for a news site or another platform shows a preview image with a play button, but the video lives on that other site. Polls, image posts and posts that only quote a video are the same: there is no media file attached to that post itself.
Check what you are looking at. If tapping the video opens another website, copy that site's link and use the matching downloader. If it is a quote post, open the quoted post and use its link instead.
5. The video is marked sensitive or age restricted
Posts marked as sensitive media are hidden behind a warning, and X only shows them to logged-in accounts that have chosen to see that kind of content. In some countries X also asks for age verification first. A downloader has no account and no age check, so to it these posts look private.
There is no workaround from a public web tool. If a video only plays for you after clicking through a sensitive content warning, that is almost certainly why it will not download.
6. Your browser or an extension is blocking the save
Ad blockers, privacy extensions and download managers all intercept media requests, and several of them block the save without showing an error. The page simply does nothing when you tap the quality you want.
Disable extensions for one attempt, or open the downloader in a private window where extensions are usually off by default. If the download works there, allowlist the site and turn them back on. On iOS, the equivalent is Settings, Safari, Extensions.
In-app browsers are the other big one. If you open a link from inside the X app, it loads in X's own built-in browser, which often cannot save files at all. The page works, you tap a quality, and nothing happens. Open the page in Safari or Chrome instead, using the menu in the corner of the in-app browser. On iPhone, the file then lands in the Files app rather than Photos, which our guide on where downloaded videos go on iPhone explains.
7. Region blocking
Some video on X is geographically restricted, either because of a rights agreement or a legal request in a specific country. Sports highlights and broadcast clips are the usual examples. From a blocked region the media endpoint returns nothing and the failure looks identical to a deleted post.
There is no clever fix for this. The content is not being served to the location the request came from.
8. The download starts and then stalls
A transfer that dies at eighty percent is a network problem, not a file problem. Large files on unstable mobile connections are the usual culprit, and phones make it worse: iOS Low Power Mode suspends background transfers, and Android Data Saver interferes with large downloads on mobile data.
The fix is to pick a lower quality and try again. A 720p file that finishes beats a 1080p file that does not, and on a phone screen the difference is close to invisible anyway.
9. The rate limit
If you paste a dozen links back to back you may hit a short pause. There is no account and no daily quota being counted against you, just light rate limiting so the service stays responsive for everyone. Wait a minute and carry on.
A ten second diagnostic order
- Open the link in a logged out private window. Nothing there, or a sensitive content warning, means the post is private, deleted, restricted or region blocked, and no tool can help.
- Check the URL contains /status/ and a long number. If it does not, you copied a profile or a quote.
- Make sure you are in Safari or Chrome, not the X app's built-in browser.
- Disable extensions and try once more.
- Pick a lower quality in the Twitter video downloader if the transfer is stalling rather than failing outright.
- Check your device has free space. Both phone operating systems report a full disk as a generic failure.
When the video is a GIF or you only want the audio
If the post is one of X's looping GIF clips, a normal video download returns a small silent MP4 and that is correct, because that is what the platform stores. The Twitter GIF downloader explains the format properly. If you want only the sound from a clip, the Twitter to MP3 converter skips the video entirely and produces a much smaller file.
Videos in direct messages
A video someone sent you in a DM is private to that conversation, so no public downloader can fetch it. If it is a shared post, open the post and use its link. For videos uploaded straight into the chat, our guide to downloading video from a Twitter DM covers the workarounds that actually work.
Still failing
If the post loads fine in a logged out window, the URL is a proper status link, extensions are off and it still will not fetch, then the failure is on our side rather than yours. Platforms change their internals regularly and things break for a while. Tell us the link and what you saw on the contact page and we will look at it.
Errors worth reporting, and errors that are not
A single link failing while everything else works is nearly always something about that specific post: private, deleted, region blocked, or the wrong kind of URL. Reporting it rarely leads anywhere, because there is nothing on our side to fix.
Every link failing at once is a different signal. That usually means X changed something internally and the extraction broke, which happens a few times a year and gets fixed once we see it. If you paste three unrelated public posts and all three fail, that is worth telling us about, and the timing helps more than the link does.
For the full picture of how a download works end to end, including which quality to choose and where the file lands on each device, the how it works guide walks through the whole process.
You are almost certainly logged in and seeing a protected post, or a cached preview of something already deleted. Open the link in a private window while logged out. If it is not there, a downloader cannot reach it either.
No. Protected accounts have chosen their audience and the media is not publicly served. This is intended behaviour rather than a limitation that can be worked around.
Network instability, nearly always. Low Power Mode on iPhone and Data Saver on Android both interfere with large transfers. Pick a lower quality, which is a smaller file, and it usually completes.
It can. Several blockers and privacy extensions intercept media requests and cancel the save with no visible error. Try once with extensions disabled or in a private window.
There is no counter and no account, so nothing tracks a quota against you. Light rate limiting applies if you paste many links in quick succession, which shows up as a short pause rather than a block.
X only shows sensitive media to logged-in accounts that have opted in, and in some countries after an age check. A downloader has no account, so the post looks private to it and the download fails.
You are probably in the X app's built-in browser, which often cannot save files. Open the page in Safari or Chrome and try again.
