Threads Video Not Downloading? Every Error Explained and Fixed

Before you paste: three quick checks

Most failed downloads come down to one of these, so check them first:

1. It is a link to a single post. A post link looks like threads.com/@username/post/…. A profile link (threads.com/@username) or a search page has no single post to read media from.
2. The post contains a video or a photo. Text-only posts have nothing to download.
3. The account is public. Open the link in a private browser window where you are not logged in. If you can't see the post there, ThreadSave can't either. See why private posts are not supported.

Every error message and its fix

"Please paste a Threads post link."

Cause: the input box was empty when you pressed Download. On some phones, the paste didn't happen because the browser blocked clipboard access.

Fix: long-press the input box and choose Paste, then press Download. If the Paste button next to the input box does nothing, your browser asked for clipboard permission and it was denied. Pasting by hand always works.

"This doesn't look like a Threads post link."

Cause: the text doesn't start with https://threads.com/ or https://threads.net/ (with or without www.). We check this both in your browser and on our server. Common culprits: a link copied from Instagram, a shortened link from another service, or extra text pasted together with the URL (for example "Check this out: https://…").

Fix: copy the link again straight from Threads and paste only the URL. Our guide on how to copy a Threads link shows where the option is in the app and on the web.

"We couldn't find any media in this post. It may be private, deleted, or text-only."

Cause: the lookup ran, but no video or photo came back for that link. That happens when:

• the post is from a private account;
• the post was deleted or the account was removed;
• the post is text-only, or the media is in a reply rather than the post you linked;
• the link points to a profile rather than a post.

Fix: open the link in a logged-out browser window. If the media shows there, copy the link of that exact post (not the profile or a reply above it) and try again. If the post is private or deleted, it can't be downloaded. We don't try to get around privacy settings.

"Threads took too long to respond. Please try again in a moment."

Cause: we ask for the post's media, wait up to 12 seconds, and retry once if there is no answer. If both attempts time out, you see this message, so the longest you'll ever wait is about 25 seconds. If the lookup takes more than 6 seconds, the note under the input box changes to "Still working…" so you know it hasn't frozen.

Fix: wait a minute and try again. Timeouts are usually temporary slowdowns on the Threads side. Large posts with many items can take longer.

"The download service is temporarily unavailable. Please try again later."

Cause: the service that reads media from Threads couldn't be reached or returned an error, even after a retry, or our server couldn't issue a security token. This is a problem on our side, not with your link.

Fix: try again later. If it keeps happening for more than an hour, please let us know. It helps us notice outages sooner.

"Too many requests from your connection. Please wait a bit and try again."

Cause: to keep the service free and stop automated scraping, each connection can make up to 100 download lookups per hour. There is also a short-term limit on very fast bursts of requests. On shared networks (offices, schools, mobile carriers) many people can share one IP address and use up the limit together.

Fix: wait a while. The hourly window resets on its own. Switching from Wi-Fi to mobile data (or the other way round) gives you a different connection.

"Something went wrong. Please refresh the page and try again."

Cause: a general error, usually a network drop between your browser and our server. Each lookup also carries a short security token tied to your connection. If your IP address or browser identity changes between requests, the token is rejected. We fetch a fresh token and retry once automatically, but if it changes again, the lookup fails. VPNs that rotate addresses and some privacy extensions can cause this. Clicking Download many times very quickly can also trigger this message.

Fix: refresh the page and paste the link again. If you use a VPN or a privacy extension, try once with it switched off.

Problems after the download

The file saved but I can't find it (iPhone)

Safari on iPhone saves downloads to the Files app, in the Downloads folder, not straight to Photos. Open the file there, tap the share icon and choose Save Video or Save Image to move it to Photos.

The file saved but I can't find it (Android and desktop)

Look in your browser's download list or in the Downloads folder. Videos are named threadsave_video_1.mp4, photos threadsave_photo_1.jpg, and so on for posts with several items.

The video won't play

Downloads are standard MP4 files and play in the built-in players on phones and computers. If a file won't open, it was most likely cut off part-way through, for example by a dropped connection. Check the file size: a video of a few kilobytes is incomplete. Download it again.

Only some items from a carousel appear

We show every video and photo that came back for the post. If an item is missing, it was probably removed from the post or couldn't be read at that moment. Try again after a few minutes.

Still stuck? Report it

If a public post with a video still won't download, send us the link together with the exact error message. We read every report and use them to fix problems.