X has no button for this. You can delete one post at a time, forever, and that is the whole of what the app offers. So anyone who wants to delete all tweets from an account goes looking for a tool, and this is the corner of the internet where tools break quietly, charge more than they first appear to, and stop at a limit nobody mentions until you hit it. Here is what each route actually does, and the one thing you should do before you start any of them.
The 3,200 wall almost nobody warns you about
Start here, because it decides which methods can work for you at all.
X only serves roughly the most recent 3,000 to 3,200 posts of any profile. That is not a tool limitation, it is how the timeline is read - scroll far enough back and the list simply stops, for you and for anything acting on your behalf. If your account has 900 posts, this never matters. If it has 40,000, then every method below reaches the newest few thousand and is blind to the rest.
There is exactly one way past it: your own data archive. X lets you request a complete export of your account, which arrives as a file containing every post you have ever made, including the ones the timeline will no longer show. A tool that can read that archive knows about the old posts; a tool that only scrolls your profile does not.
So before comparing anything, check your post count. Under about three thousand and you can ignore this section. Over it, and your real question is not which tool deletes fastest, it is which tool accepts an archive.
Four ways to wipe an X account
1. Deleting posts by hand
Open the post, tap the menu, choose delete, confirm. Four actions, no risk, nothing to install.
It is also hopeless at scale. Five seconds a post is optimistic once you account for the list jumping as items disappear, and five seconds times three thousand posts is over four hours of uninterrupted tapping. The practical failure is not the time, it is that the list reorders beneath you and you lose your place, so you end up re-reading posts you already handled.
Worth knowing: this is the only method that works on a phone without handing anything to anyone.
2. Writing against the API
The developer route used to be the clever answer: a short script, your own credentials, a loop. Two things changed it.
Reporting through 2026 describes X moving to pay-per-use API pricing and closing the free tier to new developers, with deletion billed per request. The figures circulating come from vendors rather than official documentation, so treat exact numbers with suspicion - but the direction is not in dispute, and a few thousand deletions is no longer free. The second problem is the same 3,200 ceiling, which applies here too.
This route still makes sense if you already write code and already pay for API access. For everyone else it is now the most expensive option on this page, which is a sentence nobody could have written three years ago.
3. Web services you sign into with X
Paste your handle, authorise, let it run on their servers. Search for a tweet deleter and these are the results you meet first - they are also the ones that changed most.
Two things to check before authorising anything. First, what the permission actually grants: posting rights, reading your direct messages and following accounts on your behalf are commonly bundled into the same authorisation as deletion, and the screen rarely makes that obvious. Second, that the access ends when you are done - revoking a connected app in your X settings is a deliberate step, and skipping it leaves a service able to act on your account indefinitely.
These also inherit the API costs described above, which is why a service that was free in 2023 may now be free for your first few hundred posts and priced after that.
4. A browser extension on the session you already have
You are signed into X in your browser. That session can already read your posts and delete them, because that is what happens when you click delete yourself. An extension does the same clicking, at a pace you set, without you present.
No credentials change hands because none are needed, and nothing is authorised on X's side that you would later have to revoke - removing the extension ends the access. The work happens in your browser rather than on a server you cannot see.
What "free" actually means in this corner
Almost every search here carries the word free, and almost every answer is more complicated than yes.
Download your archive before you touch anything
This is the one step worth insisting on, and it takes two clicks to start.
In your X settings you can request your data archive. It takes X a while to prepare - often a day or more - and then you download a file containing your posts, replies, likes and media. People skip this because they are in a hurry to be rid of the posts, and it is the only part of this process that cannot be repeated later.
A deleted post is gone from X permanently. There is no restore, no trash folder and no support request that brings it back. Whatever you delete this afternoon, you will only ever have again if you saved a copy first.
This matters more than people expect. Old posts are a record of who you were talking to and what you were working on at the time, and plenty of people who cleared an account to start fresh later wanted the text back for entirely ordinary reasons - a reference, a date, a conversation they half-remembered.
Request the archive, wait for it, then start deleting. If you also want a tool that saves its own backup as it goes, so much the better, but the archive is the complete record and it comes from X itself.
Posts, replies, reposts, likes and bookmarks are five different jobs
"Clear my account" usually means more than posts, and the five lists behave differently.
Deleting a post removes it for everyone. Removing a repost only removes your repost - the original stays exactly where it was, untouched and still visible. Unliking does not notify anyone and does not affect the post. Replies are posts and delete like posts, but they are often the largest list by far and the one people forget to count. Bookmarks are private to begin with, so clearing them changes nothing anyone else can see.
If you want to mass delete tweets but keep your likes as a reading list, or delete your likes while leaving every post in place, check that the tool separates these at all. Several treat the whole account as one switch, which is fine until it is not.
Why a deleted tweet sometimes is not
X can report that a deletion succeeded when it did not. Asking twice looks identical from the outside, so a tool that fires a request and moves on will tell you it cleared four thousand posts while leaving some of them live on your profile.
The honest behaviour is to check afterwards: delete, then ask X again whether the post is still there, and only then count it. This is invisible when it works and infuriating when it does not - you find out weeks later that the account you thought you had emptied still has posts in it.
If you use any method here, spot-check your profile when it finishes rather than trusting the summary screen.
Deleting fast is how accounts get limited
X rate-limits bulk actions. Go quickly and the requests start failing, and the usual response is a temporary block on the action that clears by itself after a while.
Nobody outside X can tell you the exact threshold, and pages quoting a precise number per hour are repeating each other rather than documentation. What is consistent in practice is that steady beats fast: a tool that pauses between deletions and slows down when X pushes back finishes a long list, while one that sprints gets stopped a few hundred posts in and has to be restarted. Anything that offers to delete tweets in bulk should be judged on how it behaves when X says no, not on how fast it starts.
If you are clearing a large account, expect it to take sessions rather than minutes, and treat any tool promising to bulk delete tweets in one fast sweep as a tool that has not met X's rate limiter yet.
Clearing an account from the browser you are already signed into
If the fourth method sounds like the right shape, this is what it looks like in practice. Postwash works inside the X tab you already have open, so it never asks for your password and there is no connected app to revoke afterwards.
It handles the five lists separately, filters by date so you can delete old tweets while keeping the recent ones, saves a CSV or JSON backup of everything before it deletes, and verifies each deletion with X rather than trusting the first answer. For accounts past the 3,000-post wall it reads your X archive so the older posts are reachable. It paces itself against X's own rate-limit counters and slows down before they run out.
Frequently Asked Questions
Which route fits your account
Under a few hundred posts: delete them by hand and skip every tool on this page. The setup costs more than the task.
A few thousand posts, no code, no desire to authorise anything: a browser extension on your own session is the only option that neither charges per deletion nor asks for account permissions you would have to revoke later.
Tens of thousands of posts going back years: your decision is made for you by the archive. Request it first, and then choose from whatever can read it - the number of candidates drops sharply at that point, which is useful, because it means you are choosing between tools that have actually thought about the problem.
Whichever you pick, the order is the same: export the archive, back up, delete slowly, then check the profile yourself. The posts are not going anywhere while you take an extra day over it, and they are very much going somewhere permanent once you start.
