You opened your X following list, saw 2,400 accounts, and realised most of them stopped posting two years ago. Now you want them gone. The problem is that X gives you exactly one tool for the job: a button, pressed one account at a time. This guide walks through how to mass unfollow on X using the four approaches people actually use, what each one costs you in time and account risk, and the one limit that quietly breaks all of them.
Why the following list gets out of hand
Nobody sets out to follow two thousand accounts. It accumulates. You follow back everyone who follows you for a year. You follow forty people during a conference. You follow a dozen news accounts during an election. Then three years pass and the timeline you built no longer resembles anything you wanted to read.
The maths is unkind. If you follow 2,000 accounts and want to clear 1,500 of them, and each one takes roughly four seconds — find the row, press the button, confirm you pressed the right one, scroll — that is about an hour and forty minutes of uninterrupted clicking. In practice nobody does it in one sitting, so it becomes a job you restart five times and never finish.
There is a second problem that is easy to miss. The X following list does not load all at once. It loads in chunks as you scroll, and when you unfollow someone the list re-renders underneath you. Scroll position jumps. You lose your place. People routinely unfollow the same account twice and skip thirty others without noticing.
The four approaches you will run into
Search for a solution and you land on the same four options, usually without anyone explaining the trade-offs. Here they are up front:
Let me go through them properly, because the differences matter more than the summaries suggest. Most guides on how to mass unfollow on X stop at naming the tools; the part that decides which one you should use is what each one asks of your account.
Method 1 — Unfollowing by hand
Open x.com/yourhandle/following, hover a row, press the Following button, confirm. That is the whole method.
It is worth saying clearly that this is the right choice more often than people assume. If you are trimming thirty or forty accounts, every other method on this page costs more time to set up than it saves. Open the list, spend ten minutes, done.
Where it falls apart is volume, and it falls apart in a specific way. Around the two or three hundred mark the re-rendering problem compounds, you start losing track of where you were, and — more importantly — you start making decisions badly. By account four hundred you are not evaluating anyone, you are just pressing the button. That is how people accidentally unfollow their own clients.
Method 2 — Web panels that ask you to log in
These are the sites that appear first in search results. You visit, you sign in with your X account, and a dashboard shows your following list with checkboxes.
There is a second, quieter issue. Because the panel acts from its own servers, every action comes from an IP address that is also running thousands of other people's unfollow jobs. From X's side that is a far stronger automation signal than the same actions coming from your own browser. This is a known contributor to accounts getting flagged, and it is the main reason I would not recommend this route.
If you have used one of these in the past, it is worth checking Settings → Security and account access → Apps and sessions right now and revoking anything you no longer recognise. Most people have three or four old authorisations sitting there.
Method 3 — Scripts and the official API
If you write code, the idea of looping over your following list and calling an unfollow endpoint is obviously appealing. It is also mostly closed off now.
The free tier of the X API does not realistically support bulk unfollowing any more — the request allowances are far below what clearing a few thousand accounts needs, and the tiers that do support it are priced for businesses, not for someone tidying a personal timeline. The browser-console scripts circulating on code-sharing sites work by simulating clicks on the page, which puts them in the same category as method four but without the safety rails: no whitelist, no speed control, and no way to stop cleanly halfway through.
I am not saying don't — if you are comfortable reading what a script does before running it, this is a legitimate route. I am saying that pasting unfamiliar code into your browser console while logged into your own account deserves more caution than it usually gets.
Method 4 — A browser extension in your own session
The fourth approach keeps everything inside the browser you are already signed into. The extension reads the following list that your own session already has access to, then performs the same clicks you would perform, at a pace you set.
The distinction that matters: no password leaves your machine and no external server receives a token. You are not delegating access to anyone — you are automating your own hands. This is why a mass unfollow Twitter extension — a mass unfollow Twitter Chrome extension, to be precise about where it runs — sits in a different risk category from a web panel, even though both automate the same actions.
This is the category our own tool falls into. X Unfollow AI works through your existing session, identifies which accounts do not follow you back, and lets you choose between clearing everyone or only the non-followers. Speed is adjustable between 200ms and 5000ms per action, there is a whitelist so specific accounts are never touched, and the following list can be exported to Excel before you change anything. Processing happens locally in the browser.
The honest limitation applies here too: it cannot exceed what X allows in a day. Nothing can. What it changes is the clicking, the record-keeping, and the chance of removing someone you meant to keep.
The daily limit nobody mentions until it bites
This is the part that derails most bulk unfollow attempts, and it is worth understanding before you start rather than halfway through.
X applies rate limits to follow and unfollow actions. The exact numbers are not published and they are not fixed — they shift with account age, verification status, follower count, and how the account has behaved recently. A months-old account with 80 followers has far less headroom than a five-year-old account with 20,000. Anyone quoting you a precise X daily unfollow limit as a universal number is guessing.
What is consistent is the shape of the response. Go too fast and the unfollow action silently stops working — buttons appear to depress but the account stays followed. Push further and you get a temporary action block, usually measured in hours, occasionally longer. Repeat the pattern across several days and it escalates.
The practical approach is to spread the work. Clearing 1,500 accounts across a week at a relaxed pace is uneventful. Attempting it in one evening is how people end up locked out of actions for a day. If you are using a tool with a speed setting, slower genuinely is safer — the gap between actions is the single variable that most affects whether a session finishes cleanly.
Unfollow everyone, or only the ones who don't follow back?
Both are legitimate, and the right answer depends on what the account is for. Most people searching for how to unfollow all on Twitter actually want the second one — they do not want an empty timeline, they want the dead weight gone.
Unfollow everyone on X and start over is the sharper option. It gives you a genuinely blank timeline and you rebuild deliberately. It is also irreversible in any practical sense — X does not keep an "accounts I used to follow" list you can restore from, and if you did not export the list first, those two thousand handles are simply gone. If you are considering this route, export first. It costs nothing and removes the only part of the decision you cannot undo.
Clearing only non-followers is the more common goal, and it is usually framed as fixing the follow-to-follower ratio. It is worth being precise about why that ratio matters: it is not a metric X ranks you on. It is a signal other humans read in the half-second they spend on your profile. An account following 3,000 and followed by 200 reads as automated, whether or not it is. That perception is the real cost, and it is a reasonable thing to want to fix.
One caution on the non-follower filter: plenty of accounts worth following will never follow you back. Journalists, researchers, companies, the person whose writing you read every week. A pure non-follower sweep removes all of them. This is exactly what a whitelist is for — put those accounts on it before you start, not after you notice they are missing.
What to do before you start
Three things, none of which take long, all of which you will be glad of later.
Export the list. Whatever method you choose, get your current following list into a spreadsheet first. It is your only undo. If you later realise you removed someone important, a file with their handle in it is the difference between a thirty-second fix and never finding them again.
Build the whitelist before the first click. Go through and mark the accounts that must survive — clients, close contacts, the handful of accounts you genuinely read. Doing this while you are calm produces a much better list than doing it at account six hundred when you just want it finished.
Decide the pace in advance. Pick a number per day and a speed setting, and stick to them. The failure mode is always the same: it is going well, so you speed up, so it stops working. Deciding beforehand removes that temptation.
If your goal is specifically to clear out accounts that have gone quiet rather than everyone who doesn't follow back, our guide on finding and removing inactive followers on Twitter covers how to identify them first. And before you start any bulk session, it is worth reading the five mistakes that hurt accounts during a mass unfollow — most of them are avoidable once you know they exist.
Frequently Asked Questions
Which method fits your situation
Under about fifty accounts, do it by hand and stop reading. Past that, the realistic choice is between a browser extension and a hosted web panel, and the deciding factor is not speed or price — it is whether you are willing to give an external server standing permission to act as your account. For most people that trade is not worth making when an extension does the same job inside the session they already have open.
Whichever you pick: export the list first, build the whitelist before the first click, and go slower than feels necessary. The daily limit is the one constraint no method removes, and working with it instead of against it is the difference between a clean week and a locked account.
