Company
Contact us
How to reach ThreadsDownload about a broken link, a copyright notice, or a privacy question — and what we can and cannot help with.
Email works. There is no contact form on this page, and that is deliberate: a form means either a third-party script watching you type or a table of stored submissions, and this site runs neither. An address you can see is also an address you can verify.
Where to write
General questions
Anything about how the tool works, a feature that behaves oddly, or a suggestion.
hello@threadsdownload.orgCopyright and legal
Takedown notices, counter-notices, and trademark matters. Read the copyright policy first — it explains what we are able to act on.
copyright@threadsdownload.orgPrivacy
Questions about what is logged, requests about information you believe is held here, or anything in the privacy policy.
hello@threadsdownload.orgReporting a link that failed
This is the most common reason people write, and the reports we can act on all look the same. Include:
- The Threads link you pasted. The full URL, exactly as you had it. Without this there is nothing to reproduce.
- The message you saw. Quote it verbatim — each one points at a different cause, so "it didn't work" narrows nothing down.
- Whether the post is public. Open it in a private or logged out browser window. If it does not load there, it is not public, and that is the answer.
- Your browser and device. For example "Safari on iOS 18" or "Chrome on Windows".
- What you expected instead. Occasionally the tool is working as designed and the surprise is worth fixing anyway.
Before writing, it is worth checking the list of reasons a link fails — most reports turn out to be a private post, a profile URL pasted instead of a post URL, or an expired results page that just needs running again.
What we cannot help with
Not to deflect, but so you do not wait on a reply that cannot fix anything:
- Anything about your Threads or Instagram account. We are not Meta and have no access to accounts, posts, or moderation decisions.
- Getting media out of a private or follower-only post. Not a bug and not an oversight — it is a boundary we keep on purpose.
- Recovering a deleted post. Once it is gone from Threads there is nothing left to fetch. Nothing is cached here that could stand in for it.
- Removing a copy hosted somewhere else. No media is stored here, so there is nothing on this server to take down. The host of the copy is the effective place to file.
- Raising your rate limit. Twenty lookups a minute per address is what keeps the service available; there is no allowance to grant.
What to expect back
Every message is read. Bug reports with a link and an error message get looked at first, because they are the ones that can actually be fixed. Complete copyright and privacy notices are answered directly. We will not promise a response time we cannot keep — but no valid notice goes unanswered.