Twitter (X) Video Download Not Working: What to Check

Contents
- When It Feels Like Twitter Videos Just Won't Save
- How to Check It Yourself With X's Official Pages and Browser Tools
- Why There Are Multiple Qualities—and Why Private or Deleted Posts Get Blocked
- At a Glance: Quality and Format
- Common Sticking Points
- How Far Can You Use a Saved Video?
- How is this different from other download sites and methods?
- The bottom line
- Frequently asked questions
If a video won't save from Twitter (X), the cause is usually one of three things. The account is private, the post has already been deleted, or you're misunderstanding why the quality options are split up the way they are. Most of the time the tool isn't broken — it's about what state X has that tweet in.
This post lays out how X videos are actually stored and delivered, why quality comes in several versions, and what's different about tweets that look like moving GIFs — all based on publicly known facts. Whether or not you use a tool, the criteria that decide whether something can be saved are the same. Once you understand how it works, you'll be able to guess which tweets will work and which won't without pasting anything into a box first.
Summary ① Most cases of X video downloads failing come down to private accounts or deleted posts, not the tool or the quality settings. ② Quality shows up in several versions because X encodes and stores the video at multiple resolutions the moment it's uploaded. ③ Tweets that look like moving GIFs are supported too, as their own category, and t.co short links get expanded to the original address automatically before anything is processed.
When It Feels Like Twitter Videos Just Won't Save
The block starts the moment you find a video tweet you like and try to save it. You right-click on the video and something like "Save video as" never even appears, or it does and clicking it hands you an empty file or one that won't play. That's when you learn it doesn't end with a single right-click the way images do.
This isn't a coincidence. The way a browser displays video is different from a photo. A photo gets drawn on screen as one whole file, but a video sits on top of a player that downloads the pieces it needs for playback in sequence as it plays. So the browser's built-in "save" feature may grab only the part that has played up to that moment instead of the whole file — or it may not offer a save option at all.
That's why the question "It plays fine, so why won't it save?" follows so naturally. To a browser, playing something on screen and downloading it as a file are completely different operations. If you don't know that difference, it's easy to feel like video tweets in particular are being deliberately locked down.
So you search "Twitter video download" and open a few sites. Some work and some don't. You paste the same tweet URL and one site shows a list of qualities while another just throws an error, and you end up hopping from site to site wondering whether some are simply better than others.
There's another annoyance in that process too. Some of the sites sitting at the top of the results have several download-shaped buttons scattered around the page, so just figuring out which one is the real save button and which is an ad takes time. When the screen keeps changing during the short wait after you paste a URL, it's hard to tell whether that's normal behavior — especially on a site you've never used before.
Even when the quality list does appear, a new round of confusion starts. Why does one tweet go up to 1080p while another tops out at 720p? Does picking a lower quality make the save faster, or does it just make the file smaller? You can't quite tell. The quality options look like values the site generates by encoding the video, but in reality they're determined by something else entirely.
Sometimes you're blocked outright while trying to save a video from an account you follow. If that account is private (locked), no matter how precisely you enter the URL, the quality list never shows up. It's also common to go looking for a video that made the rounds only to find the post has already been deleted, so no site can process it. If you've ever seen a tweet one day and gotten nothing but "This post is unavailable" the next, you know how frustrating that is.
Trying it in the mobile app brings its own confusion. You tap share and use "Copy link," but the address you get isn't the familiar x.com URL — it's a strange short one starting with t.co, and you pause to wonder, "Can I just paste this as is?" The fact that the long address in a desktop browser's address bar looks different from the one the app's share button copies is enough to make you suspect you did something wrong.
On top of that, things get murky when you try to save a tweet marked "GIF" that autoplays on a loop in your timeline. There's no play button and it looks like a moving picture, so you're often not sure whether it saves the same way a regular video tweet does. You might wonder whether the file extension is really .gif or something else, but how it plays on the surface doesn't tell you much. Stack up enough of these experiences and it's easy to conclude that saving Twitter videos is just a feature that never really worked.
Sometimes you try long-pressing the screen on your phone to save it. Photos save that way, but with videos you usually get no response at all, or just the share menu and nothing more. You're left asking "Why does this work for photos but not videos?" — and that's often what cements the impression that Twitter videos are uniquely hard to save.
How to Check It Yourself With X's Official Pages and Browser Tools
X doesn't offer a separate "Download" button for videos on the web. So if you want to check without a tool, you can use the browser's own developer tools and watch which files actually load. Here's the order.
- Paste the URL of the tweet you want to save into your browser's address bar and open the actual tweet page. Even if you paste the t.co short link you copied with the Share button, the browser will take you to the real tweet page on its own.
- Press F12 on your keyboard (or Cmd+Option+I) to open developer tools, then select the "Network" tab at the top.
- Type "mp4" into the filter box above the request list to narrow it down to video-related requests.
- Click the play button on the video in the tweet. The actual video file addresses will then show up in the filtered list.
- You'll see addresses for several resolutions listed together. Open the one you want in a new tab, right-click the screen, and choose "Save As" to download the file.
This method only works on public tweets. If the account is private or the post was deleted, the tweet page either won't open at all or will show "This post couldn't be found," so no video file request will appear even if you open developer tools. Tweets that display as animated GIFs work the same way — you can find the file request in the Network tab and save it.
It also helps to know that menu names and locations differ slightly between browsers. In Chrome and Edge, clicking "Inspect" opens the same screen. In Safari, you first have to turn on "Show features for web developers" in Settings before the same feature shows up in the menu. Either way, every browser ends up showing you the same "list of network requests," so don't get hung up on the labels.
The addresses for the various resolutions you find often include width and height pixel values in the file name or request details, so you can compare those numbers to estimate which one has higher quality. Still, when there are several entries, opening each one to play it and compare quality by eye is a real hassle.
There are things this method can't tell you. Just by looking at the request list in the Network tab, it's hard to tell at a glance whether you're dealing with a standard video tweet, a tweet with only a single quality option, or one classified as a GIF. When several requests are mixed together, it also takes time to sort out which one is the actual playback file and which is a thumbnail preview request.
It gets even more confusing with tweets that have both photos and video. Even with the mp4 filter on, multiple video files at different qualities show up at once, so looking only at file names or request order often won't tell you which is the highest quality. You're left doing the manual work of opening each one and comparing screen sizes.
And repeating this sequence every time is a pain. You have to open developer tools, apply the filter, click play to trigger the requests, then compare each resolution by eye to figure out what you're looking at. Doing that for every single tweet you want to save takes a lot of time — and on a phone instead of a PC, opening developer tools at all is hard, so you can't really use this method there.
Here are a few things worth knowing before you try this method.
- If the tweet page won't open at all or shows "Post not found," opening developer tools won't help. It means the account is private or the post was deleted.
- If you tried this while logged in, it's a good idea to log out or open it again in a private/incognito window to check. If the same file requests still appear while logged out, that's a sign the post is actually public.
- If several mp4 files show up in the request list but they all look about the same when you play them, the most accurate way is to save the files and check the actual resolution in Properties or Get Info.
Paste a tweet URL with no login, pick a quality, and save it as MP4. It's completely free.

Why There Are Multiple Qualities—and Why Private or Deleted Posts Get Blocked
The rest of this section explains why these differences happen, based on how the system is built. We'll stick only to the facts we've already checked and won't invent new numbers or policies. If we walk through the five threads in order, you'll see that all the confusion listed in Section 1 actually comes from the same root.
It Uses the Public Syndication API
The address cdn.syndication.twimg.com is the public syndication API X exposes so news outlets and blogs can embed tweets on their pages. If you've ever seen a tweet inserted as a card in the middle of a news article, this is the channel used to render it. The key thing about this API is that it responds as long as it has the tweet's unique number (the tweet ID). No login session or cookies are needed for the request to go through.
Look closely at a tweet URL, and you'll see a long number at the end. That's the tweet ID. Ask the syndication API for this ID, and you get information about the tweet. If it contains a video, the response also includes a list of files you can save. This is why a quality list appears immediately from just a tweet URL, with no login.
It matters that the same API is used both for news embeds and for download tools. A tweet card embedded on a news page uses this information to draw the text, author, and video preview on screen. A download tool uses the same information but pulls out the list of downloadable file URLs instead of drawing them. Both are using the same source data in different ways.
The Quality List Is Set at Upload Time
The 720p, 360p, and 270p options you see aren't generated in real time the moment you hit save. When X receives a video upload, it converts it into several resolutions ahead of time and stores each as a separate file (variant). So "choosing a quality" means picking one of the files that already exists—not lowering or compressing the quality on the spot.
There's a real example you can check. If you analyze the video tweet from NASA's official account of the Mars rover Perseverance's successful landing ("Touchdown confirmed"), you can confirm that MP4 files at three resolutions—720p (1280×720), 360p (640×360), and 270p (480×270)—exist at separate URLs. That means even an iconic video from a large account like NASA had only 720p as its top quality. That's not a limit of the tool; it means the upper limit of the qualities X had encoded for that tweet was 720p.
This example also shows something else: the gaps between the three qualities aren't even. Going from 720p to 360p halves both the horizontal and vertical pixel counts, while the drop from 360p to 270p is smaller. The quality tiers aren't split into clean arithmetic steps. It makes more sense to see them as a few practical tiers prepared for different playback environments.
So the answer to "Why doesn't this tweet have 1080p?" is usually "Because X didn't encode and store it at that quality." A resolution that isn't in the list is a file that never existed, so no site or program can create a quality that isn't there. Put another way, every quality in the list is the original file exactly as X stores it on its servers. That's why "choosing" a quality really means "specifying one of the files that are already prepared."
Preparing multiple resolutions ahead of time isn't unique to X. It's a common approach for sites that serve video on the web. Playback environments (screen size, connection speed) vary, so instead of converting at playback time, sites pre-build a few representative resolutions and serve the one that fits. That reduces server load. From a download tool's perspective, its job is simply to point you to the addresses of these pre-made files.
Why Private Accounts and Deleted Posts Get Blocked
The syndication API is designed to return normal data only for public tweets. If you send a request with the ID of a post from a locked account or a post that has already been deleted, you get a 404 error or a tombstone (a response indicating that the post was deleted or is inaccessible) instead of video information.
This isn't because the download tool lacks "permission" to access the tweet. The API itself is responding based on its judgment that the post "does not exist in public form." If you're logged in to the X app and follow that account, the video will show up normally, but that's a completely different story for a syndication API that requires no login. The same tweet can be visible or invisible depending on the path you use to reach it.
Flipped around, this structure comes down to one rule: if a post isn't "something anyone can see without logging in," this method can't retrieve its data in the first place. Posts that require follower approval, older posts on an account that has since switched to private, and deleted posts are all filtered out for the same reason under this rule. The same standard applies with no exceptions, so there's no case where one particular account uniquely works or doesn't.
What Tweets That Look Like GIFs Actually Are
In the X timeline, some tweets loop automatically without a play button—the ones people commonly call "GIFs." X stores these under a separate internal category (animated_gif), distinct from regular video tweets, which are classified as "video." Because the download tool also recognizes and handles this category in the syndication API response, these tweets aren't left out of the quality list; they're captured alongside video tweets with a normal play button.
The very existence of this distinction means that even though they look like the same "moving picture" to users, they're managed as different types of content inside the system. If a download tool doesn't handle this category, tweets shown as GIFs can silently drop off the list. But once you know that these tweets are items handled together in the syndication API response, differing only by whether they have a play button, it's easy to understand why they're processed on the same screen.
t.co Short Links and Direct Delivery via CORS
X wraps every link inside a tweet once in its own short URL, t.co. This is just a redirect for measuring click stats; it doesn't point somewhere separate from the tweet. So when you paste a link that starts with t.co, it's automatically expanded to the original address first, and then the tweet ID is pulled out and processed. That means you don't need to find and paste the original URL separately.
This is also why the address copied by the share button in the mobile app often comes out in t.co form. When the app creates a share link, it generates it as a short URL that can track clicks. That's just a difference in how the link is issued, unrelated to the tweet itself. Whichever form of address you enter, the tweet and tweet ID you ultimately reach are the same.
Another important difference is exactly where the saved file comes from. X's video servers allow CORS (Cross-Origin Resource Sharing), so your browser can fetch the file directly from X's servers without going through an intermediate server. This is a different setup from many download sites, which first fetch the video to their own servers and then pass it on to the user. The absence of that middle step is what you experience as a difference in speed.
To sum up, the quality list, GIF support, t.co handling, and delivery speed—all four features covered in this section—come from one principle: a public API structure that deals in "public data only, without login, exactly as the original." Once you know this principle, why qualities are split this way, why private posts are blocked, and why saving is fast are no longer separate features; they all connect through one explanation.
Why Knowing This Structure Helps
Without knowing the structure, every time a save fails, you end up repeating, "Is this site the problem? Should I try another one?" But if you know the structure, the order of judgment gets simpler. First check whether the tweet is a public post that anyone can see without logging in. Only then look at how many qualities are listed or whether it's a GIF.
If you reverse that order, you'll keep getting confused. Before blaming the tool for why there's only this one quality, check how many qualities X prepared for that tweet in the first place. Before blaming the tool because saving doesn't work at all, check whether the account is still public. Just knowing the order of causes can save you from wasting time bouncing between sites.
At a Glance: Quality and Format
What you can save, and how it behaves, depends on the quality level and the type of tweet. Here's the table version of the mechanics covered above.
| Category | Format | Traits | Saveable? |
|---|---|---|---|
| Highest quality (the cap differs by tweet; cases up to 720p have been confirmed) | MP4 | Largest file size, sharpest picture | Yes |
| Medium quality (e.g. 360p) | MP4 | A middle ground between size and sharpness | Yes |
| Lowest quality (e.g. 270p) | MP4 | Small file, so it saves relatively fast | Yes |
| Tweets that appear as animated GIFs (classified as animated_gif) | MP4 family | Loops automatically with no play button | Yes |
| Video behind a t.co-shortened link | MP4 | Resolved to the original address automatically, then processed | Yes |
| Tweets with only one quality available | MP4 | A low-resolution source upload means fewer variants | Yes (one option) |
| Video from a private (locked) account | - | The syndication API doesn't return valid data | No |
| Video from a tweet that's already deleted | - | Handled as a tombstone response | No |
One thing to note here: the "number" of quality options differs from tweet to tweet. Some tweets have all three qualities ready, like the NASA example, but others may only have fewer options depending on the source resolution of the uploaded video or how X processes it. Treat the qualities listed as everything you can pick from for that tweet.
It also helps to know how to choose a quality based on file size. If you're watching on a small screen or want to save storage, medium quality is often plenty. If you plan to re-edit the video or play it on a big screen, it's better to pick the highest quality on the list. Whichever you choose has no effect on whether the save succeeds; it only changes the file size and sharpness of the result.
Common Sticking Points
In practice, almost everything that trips people up comes down to one of the six items below. Here are the symptoms, causes, and fixes. Skim the table and find the row that best matches your situation.
| Symptom | Cause | Fix |
|---|---|---|
| No quality options appear after I enter the address | The account is private, or the post has already been deleted | First open the tweet directly in a browser and confirm it actually displays normally |
| There's no 1080p in the quality list | X only ever encoded that tweet up to a lower quality, such as 720p | It's a limit of the source file, not the tool, so pick the highest quality on the list |
| It's a GIF tweet but there's no sound icon | Tweets classified as animated_gif are silent looping videos by nature | That's normal behavior — just save it as is |
| I hesitate to paste a link that starts with t.co | A shortened link is just a redirect for click statistics; it isn't different from the real address | It's converted to the original address automatically, so you can paste it as is |
| I assumed I had to log in and started entering my account info | It's built on the public syndication API, so no login is needed at all | You only need the tweet address; you don't have to enter any account info |
| It saved, but the file won't open | The download was interrupted, or you lost track of where it saved | Check your downloads folder and try saving again |
| Saving several tweets in a row means repeating the same process every time | Each tweet has its own quality list and file address | You can't skip the step of checking each tweet's address one at a time |
If your situation isn't in the table, a good first diagnostic is to open the tweet in a browser window where you aren't logged into any account (incognito mode, for example). If it displays normally while you're logged out, that means it's a public tweet. If it doesn't, your case is likely the first row of the table above.
How Far Can You Use a Saved Video?
As established earlier, only public tweets can be retrieved. Private accounts and deleted posts are never processed in the first place. But "can be retrieved" and "can be used however you like" are completely different questions.
Copyright in a video belongs to the original creator who made and posted it. Unless you shot or produced the video yourself, or you have clear permission from the original creator, re-uploading or redistributing the saved file to another social network, YouTube, or anywhere else can constitute copyright infringement. This principle applies the same way regardless of quality or file format.
There's one easy-to-miss point here. An "embedded tweet," the kind you often see in news articles or other tweets, wraps the original tweet in a card, so the author's information and a link to the original are always shown alongside it. When you save only the video file and post it somewhere else, that context and attribution don't come with it. If you plan to re-upload the saved file anywhere, that difference alone means you need to handle crediting the original creator yourself.
Keeping a copy for yourself, backing up a video you appear in, or saving something briefly for research and reference generally counts as reasonable use. Using it commercially, though, or moving it to another channel without attribution is a separate matter. If you're unsure, the safest route is to contact the original creator directly and confirm the scope of use. Remember that the technical fact that a public tweet can be retrieved and the judgment of how you may use the result are questions on two different levels.
Setting your account to public doesn't mean anyone is free to take and use everything you post. Visibility is a setting that determines "who can see it," while copyright is a separate right that determines "who can use it." Confusing the two can get you into trouble unintentionally, so if you plan to use a saved video beyond personal keeping, it's worth recalling that distinction once more.
It also helps to remember that a saving tool only judges "can this be downloaded," not "is this okay to use." Even for a public tweet that's technically accessible, if your purpose conflicts with the original creator's intent, that judgment ultimately rests with the person doing the saving.
How is this different from other download sites and methods?
There are plenty of sites online that advertise "video downloads," and many of them say they support multiple platforms at once. These general-purpose sites usually use a relay method: when they get a link, their own servers download the video first, re-encode it, and send it back to you. That takes time, and depending on how they process it, the result may differ from the original.
X (Twitter) videos are a little different structurally. Thanks to the public syndication API, you can access the list of original files directly with just the tweet ID, without logging in. The file itself also goes straight from X's servers to your browser (CORS is allowed). That means there is no re-encoding step in between, so the quality is exactly what X originally stored, as described earlier.
Compared with other platforms, there are differences too. Many social networks limit the scope of their public embed APIs or often require a login session, so saving often requires a separate workaround. Because X makes its syndication API public, the download path is relatively simple. But that simplicity applies only to public posts. With private accounts, access is blocked just as it is on other platforms.
Browser extensions are another comparison. Extensions require installation and granting permissions, and you have to install them separately for each browser. Pasting a URL into a website has a lower barrier to entry because you can check a tweet with a single address without installing anything. Extensions often ask for broad permissions on every page you visit, so keeping that level of access just to save one video can feel like a burden.
Installing a PC program works the same way. You have to download the program separately for each operating system and keep up with updates, while a web-based method works the same on PCs and phones as long as you have a browser. In the end, no matter which method you choose, the fundamental limit is the same: you can only get public posts. The differences between methods come down to how much hassle the access process involves and how fast they process.
It also helps to compare this with screen recording. Screen recording can capture video from any platform as long as it plays, but the recorded file is lower quality than the original and tends to include unnecessary elements like window borders or notifications. The quality of the result is simply different from downloading the original file at each available quality.
It's also easy to confuse this with X's Bookmarks feature, but they serve different purposes. Bookmarks mark a tweet so you can find it again later inside X, so they disappear if your account status changes or the post is deleted. If you save the file directly, the file stays on your device even if the tweet later becomes private or is deleted.
The bottom line
- When a Twitter (X) video won't download, the cause is usually a private account or a deleted post, not the tool itself. The first thing to do is open the tweet without logging in and check whether it actually displays.
- The reason multiple qualities show up is that X encoded and stored several resolutions at upload time. A quality that isn't in the list doesn't exist as a file in the first place, so no tool can create it.
- Tweets that look like animated GIFs are supported too under a separate category (animated_gif). t.co shortened links are automatically expanded to the original address before processing, so you can paste the URL copied from the mobile share button as is.
- Saved files go straight from X's servers to your browser, so the structure is simpler and has fewer steps than a relay method that routes them through another company's servers.
- Being able to save something is different from being free to redistribute it. Remember that copyright always belongs to the original creator, and use downloads only for personal, lawful purposes.
Paste a tweet URL with no login, pick a quality, and save it as MP4. It's completely free.
Frequently asked questions
What's the most common reason a Twitter video won't download?
Most of the time, it's a post from a private (locked) account or a post that has already been deleted. The public syndication API only responds for public tweets, so locked accounts and deleted posts return a 404 or a tombstone response, and no quality list appears at all. The fastest way to diagnose it is to open the tweet directly in your browser and check that it displays normally. If the page itself won't open, switching download tools won't change the result.
Why is there no 1080p in the quality list?
Because X didn't encode and store that tweet at 1080p in the first place. The quality options you see aren't generated in real time when you click save; they're files prepared at upload time. Even an analysis of NASA's Mars landing video tweet shows a maximum quality of only 720p, so in many cases the limit is the original file itself, not the tool. Pick the highest quality in the list, and that's the best you can get from that tweet.
Can I download tweets that show up as animated GIFs?
Yes. X stores these tweets internally under a separate category (animated_gif) that's different from regular video, and the downloader recognizes and handles that category too. Even if a tweet loops automatically without a play button, it still appears in the quality list just like a regular video tweet. It's normal for there to be no sound, so don't worry.
Can I get videos from private (locked) accounts?
No. The public syndication API is built to serve only public tweets, so a request for a post from a locked account returns an error or a deleted/blocked indicator instead of normal data. Even if you follow the account and can see the post in the X app, this API, which doesn't require login, treats it as inaccessible. This isn't a limitation of one specific tool; it's a structural limit that applies to any service using the same method.
Can I recover and download a video from a deleted tweet?
No. If you request a post ID that has already been deleted, the syndication API returns a tombstone (a response indicating that the content has been deleted or blocked). That means the video has been removed from the server, so if you didn't save it before deletion, there's no way to get the original file back afterward. For videos that are going viral, saving them before they're deleted is the only precaution.
The tweet URL is shortened as t.co. Can I paste it as is?
Yes. t.co is just X's own short address that wraps every link so X can track click statistics; it doesn't point somewhere other than the tweet. When you paste it, it automatically expands to the original address and then extracts the tweet ID from it, so you don't need to find the original URL and replace it yourself. The URL copied with the share button in the mobile app is usually in this form.
Do I need to log in to download?
No. The public syndication API is something X made public so news outlets and blogs can embed tweets, so it can respond with just a tweet ID, without a login session or cookies. There's no step where you enter account information. That said, this only applies to public posts. Posts from private accounts still won't be processed whether you're logged in or not.
This article was adapted from our Korean original. Read the Korean original