When an X video download will not work

Failures fall into two groups: something about the post makes it unreadable, or something between the file and your device is interfering. The error message tells you which. Work through the matching section rather than retrying blindly, a protected post will never resolve, however many attempts you make.

"We could not find that post"

The post ID was rejected by X. Four possible causes:

The post was deleted

Once deleted, the post and its media are gone. No tool can recover it, because the data no longer exists to be served. This is permanent.

The account was suspended or deactivated

When an account goes, its posts go with it. If you can open the link in a browser and see an error from X itself, the post is genuinely unavailable and the problem is not on this end.

The link is malformed

Check for a truncated URL, copying from a chat app sometimes clips the end, leaving an incomplete post ID. Compare against the shape described in the link guide: the number after /status/ should be 15 to 19 digits.

You copied from a retweet

The link resolves, but points at a repost rather than the post holding the video. Open the original and copy from there.

"That post is not publicly viewable"

The post exists but X will not serve its data externally.

The account is protected

Protected accounts show their posts only to approved followers. That restriction is enforced by X, not by the downloader, so no external tool can bypass it, including while you are logged in yourself, since the tool never sees your session.

The only legitimate route is to ask the poster to send you the file directly.

The video is age-restricted

Posts marked sensitive require an authenticated adult session. Public read access is refused, so they cannot be resolved here.

The video came from a direct message

DM media is private by design and served through a different, authenticated system. It has no public post URL, so there is nothing to paste. To save a video someone DM'd you, use the save option inside the X app itself.

"That post does not contain a video"

The post resolved, but carries no video or GIF. Usually one of:

• It is a photo post. Still images are not video files and are not offered here.
• You linked a reply. The video is in the parent post; scroll up and copy that link.
• The video is a link preview. A post linking to YouTube shows a playable card, but the video lives on YouTube. X never held a copy.
• It is a live broadcast still processing. Wait until the stream ends and the archived post finishes processing, as covered in the formats guide.

The download starts but never finishes

The post resolved and the file began transferring, so the problem is on the network path.

• Unstable connection. Interrupted transfers usually leave a partial file. Switch between Wi-Fi and mobile data and retry.
• Not enough storage. Downloads fail silently on a full device. Check available space.
• Long video, slow link. A several-minute video at high bitrate can take a while. Pick a lower resolution if the wait is the issue, the quality guide explains the size trade-off.

The video opens in a tab instead of saving

The file reached you but the browser played it rather than saving it.

Fix: right-click (or long-press on mobile) the download button and choose Save link as or Download linked file.

On iPhone this is normal behaviour and not an error. Safari routes downloads to the Files app rather than the Photos library. The iPhone guide covers moving the file into Photos.

Nothing happens when you press the button

Usually something is blocking the request before it starts.

• Ad blocker or privacy extension. Some block download requests to any domain other than the one you are on. Pause the extension for this site and retry.
• Blocked pop-ups. If your browser reports a blocked pop-up, allow it for this site.
• Network filtering. Corporate, school and some public networks block media downloads at the DNS or proxy level. Try a different connection.
• JavaScript disabled. The tool needs JavaScript to send the lookup. The site's written content works without it; the downloader does not.

"Too many requests"

A rate limit was hit, either the per-visitor limit here, or X's own limits on the underlying service. Wait about a minute and try again. Repeated rapid retries extend the wait rather than shortening it.

Is any of this a safety problem?

No. None of these failures indicate anything harmful, they are ordinary access controls and network conditions. If you are wondering about the safety of downloader sites generally, that question has its own guide.