ThreadsDo

Threads Video Won't Download? Here's What to Check

Almost every failure is one of three cases, and each one shows a different message. One of them has a five-minute rule that explains why retrying does nothing.

Find your case first

Start from what you see on screen. The tool shows only two error messages, and where you see them tells you what kind of problem you have.

  • “This doesn't look like a Threads post link.” — the link was rejected before anything was fetched. Case 1.
  • “Couldn't fetch this post. It may be private or deleted — try another one.” — the post could not be resolved. Case 2.
  • The preview appears but the download never finishes, or the file arrives empty. Case 3.

Case 1 — the link is not recognised

The input box checks the link before sending it anywhere, so this message means the address does not look like a post. Profile pages, the home feed and search results are all rejected on purpose — none of them point at a single post, so there is nothing to download.

These forms do work:

  • threads.com/@user/post/POSTID and threads.net/@user/post/POSTID
  • With or without www, and http as well as https
  • threads.com/post/POSTID — the username part is optional
  • threads.com/t/SHORTCODE — the short form of a share link
  • Links with tracking parameters on the end; those are stripped before anything else happens

If your link has none of those shapes, do not try to repair it by hand. Go back to the post, open the ••• menu, and choose Copy link — that is the address the tool expects.

Case 2 — the post cannot be fetched

This is the most common failure, and it has more than one cause:

  • The account is private. This is not a limitation we can lift: a private post is invisible to anyone who is not following it, including our server. No downloader can change that.
  • The post was deleted, or edited into a different one.
  • The link was copied with a character missing or added. Post IDs are case-sensitive.
  • Threads refused the request at that moment, usually because of a burst of traffic from the same network.

Here is the part most people get wrong. When a post fails, the result is remembered for five minutes. Any attempt during that window returns the same failure without asking Threads again — on purpose, so a broken link is not hammered over and over. Retrying immediately, refreshing, or clicking Fetch five times in a row will all give you exactly the same answer.

So do this instead: press Fetch once, and if it fails, try a different post first. If another post works, the problem is that specific post, not your connection. Come back to the first link after five minutes if you think it was temporary.

A VPN will not help here. The post is fetched by our server, not by your browser — changing how your own connection looks changes nothing about that request.

Case 3 — the preview works but the download does not

The preview and the download travel through the same proxy, so a preview that plays means the file itself is reachable. When the download still fails, there are three usual reasons:

  • The media link has expired. Direct media links are time-limited, and a page left open for hours eventually points at one that no longer works. Fetch the post again and download straight away — a fresh result is valid for an hour.
  • Your browser or an extension is blocking the save. Ad blockers and download managers sometimes intercept the request; try a normal window without extensions.
  • The phone cannot write the file. On iOS a browser download lands in the Files app rather than Photos, and it needs free space to land at all.

What will never work

  • Private accounts — the post has to be visible to anyone, exactly as it is on threads.com.
  • Profile pictures. They are not post media, so they are not part of anything a post link can return.
  • Stories. They are not posts, and they are not public in the same way.
  • Downloading a whole profile at once. One link returns one post; there is no bulk mode.

Copying the link the reliable way

  1. Open the post itself — not your feed and not the profile grid.
  2. Use the ••• menu and choose Copy link. Links produced by the app's share sheet can take a different form.
  3. Paste it as it is. Extra parameters are handled, so there is no need to trim anything.

Wrapping up

If the message was about the link, fix the link. If it was about the post, check that the post is public and give it five minutes before trying again. If the preview worked, the file exists — so re-fetch and download immediately rather than leaving the page open.

Frequently asked questions

Why does the same link fail twice in a row?

Because failures are cached for five minutes. The second attempt replays the stored result instead of asking Threads again, so it cannot succeed. Try another post in the meantime, or wait five minutes.

How long is a download link valid?

A parsed post is kept for one hour. The direct media links inside it are generated by the platform and are time-limited, so the safest habit is to download right after you fetch.

Would a VPN fix it?

No. Fetching happens on our server, so the request to Threads does not take your connection into account at all.

It works on my phone but not on my computer. Why?

The service is identical; the difference is usually the browser. A download manager or ad blocker that intercepts requests is the most common cause, and a normal window without extensions usually settles it.

Can a private post be downloaded if I follow the account?

No. The tool works from the public post only — it never uses your Threads login, which is also why it never asks for one.

I pasted a link from the share sheet and it was rejected. What now?

Open the post and copy the link from the ••• menu instead. That produces the canonical post URL the input expects.

More free Threads tools