Why Your Twitter (X) Video Download Fails and How to Fix It

You paste a link into a downloader, click the button, and get an error, an empty result, or a file that will not play. Most of the time the cause is one of a handful of predictable situations rather than a broken tool. This guide lists the reasons a video download from X (formerly Twitter) fails, how to recognise each one, and how to fix it.

First, check the basics

Before diagnosing anything, rule out the three most common slips.

1. Is it the post link? Downloaders need the URL of a single post, in the form https://x.com/username/status/1234567890. A profile link, a search page, a list, or a Community link contains no video to fetch.
2. Does the post actually contain a video? A link preview card for YouTube or another site is not a native X video. Only media uploaded to X can be downloaded from X.
3. Did the page load? If x.com itself is down, every downloader that reads from it fails too.

If those are fine, work through the causes below.

Cause 1: wrong link type

This is the most frequent problem: links copied from the wrong place look plausible but do not point to a post.

Fix: copy the link from the post's share menu or from the browser address bar while the post itself is open. The exact steps for the iOS app, the Android app, and the web are in how to copy a tweet link. If you have a t.co link, open it in a browser first and copy the resolved x.com address.

Cause 2: the account is protected

X lets users protect their account so that only approved followers can see their posts. Protected posts are not visible to logged-out visitors or to anyone the owner has not approved. Because Twget works without a login, it sees what a logged-out visitor sees, which for a protected account is nothing.

How to recognise it: the profile shows a lock icon next to the name, and opening the post while logged out shows an error or a "These posts are protected" message.

Fix: there is no workaround that respects the owner's choice, and Twget does not offer one. If you follow the account and want a copy for personal use, ask the poster to share the original file. Attempting to bypass access controls also runs against the X Terms of Service, which govern how the service may be accessed.

Cause 3: the post was deleted or the account is suspended

A deleted post returns nothing; the media is removed along with it. Suspended accounts behave the same way from the outside.

How to recognise it: the post page says the post is unavailable or does not exist. Technically the server responds with a 404 Not Found status, which the MDN documentation defines as the resource being unreachable at that address without saying whether it is temporary or permanent.

Fix: none for that link. Search for a repost, or check whether the same account posted the video elsewhere.

Cause 4: sensitive or age-restricted media

X marks some media as potentially sensitive, either by the poster's own setting or after review. Such media is hidden behind a warning for many viewers and is not served at all to logged-out visitors in some cases. Because Twget never logs in, media that X withholds from anonymous visitors cannot be fetched.

How to recognise it: the post shows a "This media may contain sensitive content" overlay, or the video is invisible when you open the post in a private browsing window.

Fix: if X shows the video to you while logged in, the only way to save it is a method that uses your own session, such as a local tool with browser cookies. Twget will not ask for your credentials, and you should be wary of any web downloader that does.

Cause 5: rate limits

Every service that serves media has limits on how many requests a single client can make. When they are exceeded the server replies with HTTP 429 Too Many Requests, which, as MDN explains, asks the client to slow down and may include a Retry-After header saying how long to wait. X applies rate limits to its own API as well; its developer documentation describes windows of 15 minutes or 24 hours after which the limit resets.

How to recognise it: downloads worked a moment ago and now every attempt fails, sometimes with a message about too many requests, often after you tried many links in quick succession. Shared networks, such as an office or a university, hit limits faster.

Fix: wait a few minutes and try again. Do not hammer the retry button; each attempt counts.

Cause 6: access denied or blocked request

Occasionally the server responds with 403 Forbidden. Per MDN, this means the server understood the request but refuses to fulfil it. On X this happens when a media URL has expired, a request lacks a token the site expects, or automated traffic protection kicks in.

Fix: copy the post link again from a freshly loaded page and retry. Direct media URLs expire; the post link does not. If every link is blocked, it is usually temporary and clears on its own.

Cause 7: the file downloaded but will not play

If the result is silent, remember that X "GIFs" are silent MP4 loops by design. If the file is only a few kilobytes, you saved an error page or a playlist (.html or .m3u8) rather than the video; delete it and retry with the post link. If it plays on desktop but not on an older phone, download the 720p rendition instead.

Cause 8: browser and device quirks

On iPhone, Safari may open the video in a player tab instead of saving it, or the file may land in the Files app rather than Photos. These are iOS behaviours, not download failures, and they are explained in how to download Twitter videos on iPhone. On desktop, content blockers occasionally interfere with the download request; disabling them for the downloader page is a quick test.

Quick diagnostic checklist

1. Open the post in a private browsing window. If the video does not show there, no login-free tool will work.
2. Confirm the link contains /status/ followed by a number.
3. Retry once after 30 seconds. If it works, you were rate-limited.
4. Check the file's size and extension before assuming the video is corrupt.

Frequently asked questions

Twget says the post has no media, but I can see the video. Why?

The most likely cause is that the video is served only to logged-in users, for example because it is marked sensitive, or that the "video" is an embedded link card from another site. Open the post in a private window to confirm what an anonymous visitor sees.

Can I download a video from a protected account I follow?

Not with Twget or any tool that works without a login, because those tools see the post as a stranger would. Respect the poster's setting and ask them for the file directly.

Most failed downloads trace back to a link that does not point to a public post, media that X hides from anonymous visitors, or a temporary limit that clears on its own. Run through the checklist above, copy a clean post link, and try again in Twget. If the video is public, it will download.

Sources

• X Terms of Service — X Corp., accessed January 4, 2026
• Rate limits — X Developer Platform, accessed January 4, 2026
• 429 Too Many Requests — MDN Web Docs, accessed January 4, 2026
• 403 Forbidden — MDN Web Docs, accessed January 4, 2026
• 404 Not Found — MDN Web Docs, accessed January 4, 2026