How Our Threads Downloader Works, Step by Step

Step 1: Checking the link in your browser

When you paste a link, your browser first checks that it points to threads.com or threads.net. If it does, the download starts right away. You don't need to press the button. If it doesn't, you see "This doesn't look like a Threads post link" immediately, without anything being sent to our server.

Step 2: A short-lived security token

Right before each lookup, the page asks our server for a token, a small signed code that is valid for 2 minutes and tied to your connection and browser. The server only accepts lookups that carry a valid token. This makes it much harder for bots to call our service directly without loading the site, which keeps it fast and free for real visitors.

If the server rejects the token, for example because your IP address changed between the two requests, the page automatically fetches a fresh one and tries once more.

Step 3: Server-side checks

Our server never trusts the browser on its own, so it repeats the checks:

• Link check: the address must belong to threads.com or threads.net. Anything else is rejected. This also stops anyone from using our server to fetch arbitrary websites.
• Rate limit: each connection can make up to 100 lookups per hour, plus a short-term limit on very fast bursts. Normal use never comes close. The limit stops automated mass-downloading.
• Bot trap: the form has a hidden field that people never see or fill in. Simple bots fill it in, and their requests are rejected.

Step 4: Finding the media in the post

Next, a media lookup service reads the post the same way a logged-out visitor would see it, and returns the list of videos and photos it contains. A post can have one video, one photo, or a carousel with a mix of both. We turn the answer into a single list, so every item gets its own download button.

Because the lookup sees the post as a logged-out visitor, private posts, deleted posts and text-only posts return nothing. You then see "We couldn't find any media in this post". Here's why we don't support private posts.

Timeouts and retries

Each lookup gets up to 12 seconds. If it times out or the lookup service has a temporary error, we wait a second and try once more. In the worst case you get a clear error after about 25 seconds rather than an endless spinner. After 6 seconds, the note under the input box changes to "Still working…" so you know it hasn't frozen.

A short-term cache

A successful result is kept in the server's memory for up to 1 hour. If the same post is pasted again in that time (popular posts often are), the answer comes back instantly. This cache lives only in memory. It is never written to our database, and it is cleared whenever the server restarts.

Step 5: Showing the results

Each video or photo appears as a card with a preview and its own download button. If the post has a caption, the start of it is shown as the title so you can confirm you have the right post.

Step 6: Getting the file to your device

When you press a download button, the file passes from Threads' media servers through our server to your device as it downloads. We do this for two reasons:

• Browsers only honour a "save this file" instruction for files on the same website. A direct link to Threads' media servers often just opens the video in a new tab. Passing it through our server lets your browser save it as a normal file.
• The file arrives with a clear name, threadsave_video_1.mp4 or threadsave_photo_1.jpg, instead of a long random string.

The file is not stored on our server. It is passed along in small pieces as it downloads. It also isn't re-encoded or compressed: you get the same file Threads serves for that post, at the quality Threads provides. Our server only fetches files from a short allow-list of media domains, so this step can't be used to download things from elsewhere.

What we record

For each successful download we record only the media type, the time and how long the lookup took. Those figures power the live numbers on our About page. We don't record the link or your IP address. Your IP address is used only for the hourly rate limit, and those records are deleted after an hour. The Privacy Policy has the full details.

What ThreadSave does not do

• It doesn't log in to Threads, and it never asks for your password.
• It doesn't get around private accounts or other privacy settings.
• It doesn't add watermarks, change the files, or bundle anything with them.
• It doesn't keep copies of the media you download.

If something fails along the way, the error message tells you which step it was. Our troubleshooting guide explains each one.