Threads Video Downloader Extension for Chrome and Edge
Skip the copy-paste: the extension puts a download button on the post itself. Here is how it works, what it asks for, and what it will not do.
What the extension does
The web version needs you to copy a post link and paste it into a box. The extension removes both steps: it adds a download button to Threads pages and a "Download" entry to the right-click menu, so saving a public post becomes one click. The toolbar popup is there for everything else — paste a link into it, or let it grab the post you are currently looking at.
It is the same service underneath: the extension asks our server to resolve the post, and the server hands back the direct media file. Nothing about the download itself changes — you still get the original file, not a re-encode.
Three ways to use it
- On a Threads post page — a small download button appears in the bottom-right corner. It only shows up on pages that are actually a post, so it stays out of the way while you scroll the feed.
- Right-click any Threads link — "Download" appears in the context menu. This is the fastest route from the feed: no need to open the post first.
- Toolbar popup — paste a link, or press the button that reads the link of the post on your screen. That second option also works on feed pages, where the post is visible but the address bar shows the feed URL.
How to install it
- Open the Edge Add-ons listing and press Get.
- Confirm the permission prompt. Edge lists exactly what the extension requests, item by item — the four entries are explained in the next section.
- Open any public Threads post. The download button appears in the bottom-right corner; the right-click menu works immediately, with no page to open.
Extension listing: ThreadsDo on Microsoft Edge Add-ons
If you are on Chrome, the web version at threadsdo.com does exactly the same job in the browser you already have — see the section further down on why the listing is on Edge for now.
What it asks for, and why
An extension should be judged by what it requests. This one asks for three permissions:
- "storage" — to remember two settings of your own: the interface language, and whether the on-page download button is shown. Nothing else is kept.
- "downloads" — to write the media file into your Downloads folder. Saving the file is the whole point of the extension; without this permission it cannot save anything.
- "contextMenus" — to add the "Download" entry to the right-click menu.
Alongside those, it declares three sites it is allowed to talk to:
- threadsdo.com — where the post link is resolved into a direct media URL.
- threads.com and threads.net — used only to display the download button on post pages. The extension does not read, collect or transmit the page content.
There is no advertising and no analytics inside the extension. The only thing it ever sends is the post link you explicitly gave it, and that link is processed in memory rather than stored.
What it will not do
- It cannot save a private post. Only posts that anyone can open publicly can be resolved — that is a limit on the server side, not a setting you can turn on.
- It cannot reach profile pictures or Stories. Those are not post media, so they are outside what any of these tools can fetch.
- It will never ask for your Threads password. There is no login anywhere in the extension.
- It does not watermark or re-encode. You get the file the platform serves, at the resolution the creator uploaded.
- It does not bulk-scrape a profile. One link, one post.
Why the listing is on Edge, and what about Chrome?
The extension is built on Manifest V3 and targets Chrome 114 and newer, which means the same package runs in Chrome and in Edge — the browsers share the extension format. Today the published listing is on Microsoft Edge Add-ons, so that is the one-click install path. On Chrome, the web version does the same work right now.
That also answers the naming question: a "Chrome extension" and an "Edge add-on" are the same kind of bundle. The store you install it from is a distribution detail; the button on the post behaves identically in either browser.
Wrapping up
The extension does not add a capability the website lacks — it removes two steps from the one you already have. If you save Threads videos often, that difference adds up; if you only do it occasionally, the web version is right there.
Frequently asked questions
Do I need the extension to use ThreadsDo?
No. The web version does exactly the same work with a copy-paste. The extension only removes the copying and the pasting.
Is the extension free?
Yes — free, with no ads inside it and no account required.
Why is it a "Chrome extension" if the listing is on Edge?
Because it is a Manifest V3 bundle, and Edge add-ons and Chrome extensions are the same format. The extension runs in Chrome 114 and newer as well as in Edge; the published store listing happens to be on Edge Add-ons.
Does it work on iPhone or Android?
No — mobile browsers do not run desktop extensions. On a phone, use the web version: paste the post link and the file lands in your photo library or Files app.
Does it work in Firefox or Safari?
The build targets Chrome and Edge. Firefox and Safari use different extension systems, so this package is not made for them — the web version works in any of those browsers instead.
Does the extension read my browsing history?
No. It reacts to Threads post pages, to Threads links you right-click, and to the link you paste into the popup. It does not send anything else to the server, and the link it does send is processed in memory, not stored.
Will a Threads redesign break the button?
The button is placed on post pages, which the extension identifies from the post URL rather than by scraping the layout, so a redesign is less likely to affect it. If it ever does, the right-click menu and the toolbar popup keep working.