Threads Blocklist Helper

Collect accounts from a Threads likes/followers list and block them, with an allowlist and throttling.

What it does Threads Blocklist Helper is a Chrome extension that blocks many Threads accounts for you, one at a time, using your own logged-in browser. You build a list of accounts, mark the ones you never want blocked, and press Start. It does the clicks you would do yourself: open the profile, press …, press Block, confirm. You can build the list three ways: • Collect everyone from an open likes list or Followers list on Threads • Paste handles or profile links • Add the profile or post author you are looking at, in one click It does not log in for you, does not need your password, and does not send anything outside your browser. It works on threads.com in Chrome only, with the Threads interface in English or Traditional Chinese. Before you start Use it gently: blocking many accounts quickly can get your Threads account temporarily limited. Automated actions are against Meta's terms, so the risk is on your account. The defaults are set to be cautious; keep them that way until you know how your account reacts. • Keep each run to about 20–40 blocks, and spread runs over several days. • On the web, Threads may not show any warning when it limits you. Now and then, open a few "blocked" accounts in the Threads mobile app and check they really are blocked. • If the mobile app ever shows a "Try again later" message, stop for at least several hours. • Review your list before starting. Many people who like a post or follow an account are not the people you mean to block. Quick start Your first run, start to finish: 1. Open threads.com, then open any profile and click the extension icon. Press Test on this profile. The … menu should open and close by itself, and Activity should show "Menu opened: yes" and "Block item: found". Nothing is blocked during the test. 2. Type your own handle under Allowlist, plus anyone you never want blocked. 3. Add accounts: open a post's likes list or a Followers list and press Collect from open list, or paste handles under Add accounts manually. 4. Open View accounts to block and check the list. 5. Set Max blocks per run to 3 for this first run, then press Start blocking. A new window opens and does the work; check the 3 accounts afterward, then raise the limit. Building your block list All three methods add to the same list. Duplicates are merged automatically, and the list is kept until you press Clear collected. Collect from a list on Threads 1. On threads.com, open the list you want: a post's likes list, or an account's Followers list. 2. Keep that list open, click the extension icon, set Up to (the most accounts to collect, default 300), and press Collect from open list. 3. The list scrolls by itself until no new accounts load. The button shows the count as it goes. Keep the list open until it finishes. The owner of the post or profile is never collected. Some posts don't let you see the full likes list; if the extension says no list is open, that list isn't available to you. Paste accounts manually Paste into Add accounts manually and press Add to list. One per line; commas and spaces also work. Any of these forms is fine: @someone someone https://www.threads.com/@someone threads.net/@someone/post/ABC123 The status line reports how many were added, already in the list, on your allowlist, already blocked, or not valid handles. Invalid entries stay in the box so you can fix them. Add the page you're on On a profile page the button reads Add @handle; on a post it reads Add post author @handle. One click adds that account. Allowlist Anyone on the allowlist is never blocked, even if they are in your block list. • Your handle: type your own Threads handle so you can never block yourself. • Never block: one handle or profile link per line. Changes save when you click outside the box. Accounts already in the block list stay there, but are skipped while they are on the allowlist. The To block count shows what will actually be blocked. By default, accounts you follow are skipped too (see Settings). Running a block Press Start blocking and the run happens in its own window, so the tab you are using is never touched. You can close the popup and keep browsing. • The run window opens behind your current window. It visits each account and blocks it. Leave it open and not minimized; Chrome slows down minimized windows. • The yellow bar "Threads Blocklist Helper started debugging this browser" appears during a run. This is normal. Don't press Cancel on it, or clicks stop working. • Show run window brings the run window to the front so you can watch. • Stop ends the run and closes the run window. • Closing the run window yourself also stops the run. • Resume: press Start blocking again. Accounts already blocked are skipped, so it continues where it stopped. The run ends by itself when the list is done or Max blocks per run is reached; the run window then closes. If it stops because of an error or a rate limit, the run window stays open so you can see what happened. The progress bar and the line under it show how many accounts were checked and blocked. Settings Settings are in the Block section of the popup and save as soon as you change them. Setting Default What it does Min wait (s)：10 Shortest random pause after each block. Minimum 3. Max wait (s)：25 Longest random pause after each block. Max blocks per run：40 The run stops after this many blocks. Skip accounts I follow ：On Accounts you follow are never blocked. After a skipped account (allowlisted, already blocked, or followed) the pause is only 2–4 seconds, since nothing was done. Shorter waits mean faster runs but a higher chance of being limited; we don't recommend going below 5–15 seconds. Privacy FAQ Does it read my password or login token? No. It only clicks buttons in your logged-in Threads page. Your browser sends your login with each action, exactly as when you click yourself; the extension never sees it. Does it send my data anywhere? No. It makes no network requests of its own. Your lists, settings and history are stored only in your Chrome profile. Why does it need the debugger permission? Threads ignores clicks made by ordinary scripts on some buttons. The debugger lets the extension make real mouse clicks. It uses it only for clicking, only during a run or test, and Chrome shows the yellow bar whenever it is active. Can Threads tell I'm using it? Possibly. The actions come from your account and look like your own clicks, but blocking many accounts quickly is a pattern Meta watches for. Follow the advice in Before you start.