Threads Video Downloader

Public posts with a video, which includes replies and quote posts, since Threads treats those as posts in their own right. Anything a signed-out visitor can watch is reachable, and the extractor reads the post's own media rather than whatever else the page happens to render.

That last part is worth spelling out, because a Threads permalink shows more than the post you asked for. The thread parent, the replies underneath and a tray of related posts from other accounts are all rendered into the same page with their own video data attached. A tool that grabbed the first video it found would hand you a stranger's clip and call it yours. This Threads video downloader matches on the post's own code before reading anything, which was worth doing: a plain text post on the NASA account co-renders an unrelated video post, and the naive approach picks up the wrong one every time.

Carousels work. A Threads post can carry several items, and a result here carries one file, so the first video in the carousel is the one you get and the card says how many it found when there is more than one.

Image posts list their photos at the largest size Threads serves, and text-only posts come back as having nothing to save, which is accurate rather than a failure. Private profiles are out of reach, because VideoCatch holds no Threads session and asks for no password.

One MP4, listed once. Threads publishes the same progressive file three times under different internal type numbers for its own player, so showing all three would be showing you one file three times over. The row you see is that file.

Its numbers are measured rather than quoted. The byte size comes from the content-range header of a single ranged request, the pixel dimensions come from the file's own track header, and the duration comes from the playback manifest Threads publishes beside the post. Reading the file matters, because the dimensions a post reports describe what the author uploaded rather than the copy Threads serves.

There is no watermark to remove. Threads stores what the author uploaded and streams that, so nothing is stamped on by the platform. A handle in the corner of the frame was put there by the author before uploading.

The download itself runs between your browser and cdninstagram.com. Nothing passes through this site, which is why there is no queue and no size cap.

“videos up to 5 minutes in length”

Threads has one failure shape and it is an unhelpful one: a deleted post, a private account, a misspelled handle and a server under load all answer with HTTP 200 and a page that simply lacks the post. There is no status code to read and no error to quote, so a single request cannot tell those cases apart.

What can be done about it is retry. The last of those four cases, the page served without its data, tends to come back complete a moment later, so VideoCatch fetches once, waits, and fetches again before reporting a miss. That doubles the wait on a genuinely missing post, which is the price of not giving up on a good one.

How often the empty page arrives is tracked separately from ordinary failures, so the rate is visible rather than buried in a general error count. It was never seen at all from the servers this site runs on during testing, and it was seen readily from an ordinary home connection, which suggests it is keyed on the requesting address.

If Retry does not help, check the link. The most common mistake is copying the address of the profile rather than the post, which gives a page with many posts on it and no single one to read.

1. Meta Newsroom, Introducing Threads: A New Way to Share With Text (2023-07-05)

Last updated September 2, 2026