How to delete all your tweets on X in bulk

#Quick answer

There is no bulk delete on X. To delete all your tweets you authorise a third-party deleter, and the order matters: request your data archive first, test on a small batch, then run the full job. Any tool connected live to your account can only see your most recent 3,200 posts, so anything older than that has to be deleted from the archive file. Deletion is permanent, and there is no undo.

Last updated: September 2026

#What X gives you, and what it does not

X (formerly Twitter) ships exactly one delete control: the three-dot menu on a single post. X's help page for deleting a post describes that flow and nothing else. There is no select-all, no date filter, no "delete everything before 2023" button, and every year someone expects one to appear. It has not.

What X does give you is your data. Settings and privacy, Your account, Download an archive of your data, confirm your password, Request archive. The file arrives by email and X warns it may take a few days to prepare. Request it now even if you are still deciding, because once the deletion runs, that archive is the only copy of anything you post. Our walkthrough of what is inside your X archive covers the folder structure.

So the real question is not whether to use a tool. It is which one, what it can reach, and how long it keeps access to your account.

#The 3,200 wall that most guides skip

Here is the constraint that decides everything and that most "delete all tweets" posts never mention. X's API returns up to your 3,200 most recent posts (X API timelines documentation). That is not a pricing tier or a rate limit you can buy your way past. It is the depth of the endpoint.

Any deleter that connects live to your account inherits that ceiling. Post 3,201 and older is invisible to it, which is why people pay for a tool, watch it chew through a few thousand posts, and then find their 2016 timeline still sitting there in public. The tool did not fail. It ran out of timeline.

Getting past the wall means the archive. Your archive file lists every post you ever made with its ID, and tools that accept an upload read the IDs from the file and delete them one call at a time. Circleboom markets this as an archive eraser and says plainly that its live module carries the 3,200 limit while the upload path does not. TweetDelete puts archive upload behind a paid plan for the same reason, noting on its homepage that X archives your older posts past 3,200. Redact calls it file import.

If your account has fewer than 3,200 posts, ignore this section. If you have been posting since the 2010s, the archive is your only route, and that makes the download the first step rather than an optional backup.

#What bulk deletion costs in 2026

Free tiers got stingier and the reason is not greed. X moved the API to pay-per-usage credits with no subscriptions, and its published rates price a content-management write at $0.005 per request. Deleting a post is one of those requests. A 10,000-post timeline is therefore about $50 in raw API credits before the tool adds servers, support or profit, which is why nobody hands out unlimited deletions and why per-credit pricing looks the way it does.

Prices checked on 19 September 2026, each on the vendor's own page:

Two things fall out of that table. XWipe's $0.04 a post at the entry tier is eight times the underlying API cost, which is a normal margin rather than a scam, and it tells you the credit model is tracking real metered spend. And Circleboom's 50 a day free is genuinely useful for a 500-post cleanup while being about eight months of daily logins for a 12,000-post wipe.

One caution on the marketing. TweetDelete's site bills it as "X.com's Official Partner", which is the vendor's own wording rather than something we could confirm against an X-published list, so treat partner badges on any of these sites as a claim to verify rather than a safety guarantee.

#The order that protects you

Run it in this sequence. Most of the horror stories come from doing step four first.

1. Request the archive and wait for it. Every deletion after this point is permanent, and X's own help page makes no promise of recovery. The archive is your only rollback.
2. Decide the scope. All posts is one choice. Everything older than two years, or everything matching a keyword, or replies but not original posts, are usually better ones. Every tool in the table filters by date and keyword; the filters are the feature worth paying for.
3. Test on 10 posts. Pick a narrow date window, run it, reload your profile. You are checking that the tool is authorised correctly and deleting what you asked for, not something adjacent.
4. Run the full job and leave it alone. Deletions go one API call at a time inside X's rate limits, and Redact's own page warns that those limits slow large timelines. Hours is normal for five figures of posts. Closing the tab on a live-connected web tool usually stops the run.
5. Revoke access immediately afterwards. Settings and privacy, Your account, Security and account access, Apps and sessions. Remove the deleter. It has no reason to keep write access to your account once the job is done, and a dormant authorisation is a standing liability.
6. Spot-check the tail. Search your own handle with X's from: operator and an old date range. If posts from 2017 are still there, the tool hit the 3,200 wall and you need the archive path.

#Likes, DMs, bookmarks and Grok history

Deleting posts does not touch the rest of your footprint, and for a lot of people the likes are the exposure that matters. Each content type is a separate job with separate pricing.

Redact covers the widest surface, listing posts, reposts, replies, quote posts, Articles, likes, DMs, lists and Grok chat history on its X service page, plus bulk unfollow, unblock and unmute. Circleboom and TweetDelete handle likes and DMs on paid plans. If the goal is a general reset rather than removing specific posts, the follow graph is its own project and how to unfollow everyone on X covers the limits that apply there.

Watch your daily action limits while any of this runs. Stacking a mass unfollow on top of a mass delete in the same afternoon pushes an account through a lot of automated actions in a short window, and the platform reads volume, not intent.

#What deleting does not do

Set expectations before you pull the trigger, because "delete all tweets" solves less than people assume.

• It does not retract quote posts. A quote of your deleted post survives as an unavailable card in someone else's timeline, and their commentary stays fully readable.
• It does not clear screenshots or embeds. A post quoted in a news article or screenshotted into another thread is a copy you never controlled.
• It does not purge search engines on your schedule. The URL stops resolving, then crawlers catch up over days or weeks.
• It does not remove other people's replies. Your post goes; the reply chain under it persists, minus your side of the conversation.
• It does not undo enforcement. Deleting a post that already drew a strike does not clear the strike. If the account is restricted, how to delete a post on X explains what removal does and does not change.
• It does not free the handle. Only deactivating the account does that, and that is a different decision entirely.

If what you want is your history out of public view rather than destroyed, making your X account private is one toggle, instant, and reversible. Consider it seriously before spending $99 on something irreversible.

#The access you are handing over

Read this part even if you skim the rest. A deleter needs write permission, which is the same permission a posting tool needs. For the length of the authorisation it can create posts as you, not only remove them.

Three habits keep that exposure small. Authorise only through X's own OAuth screen and read the scopes it lists, because any tool asking you to type your X password into its own form is asking for the wrong thing. Prefer a desktop client that works from your machine over a cloud service that stores your token on its servers; Redact's pitch that your content and logins stay on your device is the right shape of claim. And revoke the moment the job finishes rather than at some point later, because "later" is how a two-hour authorisation becomes a two-year one.

That principle is the same one behind how we built X-Autopilot: it drives X from your own logged-in browser session on your Mac instead of asking you to hand your session to a cloud server. It is a smaller detection surface than a shared cloud IP pool, though no browser-route automation is sanctioned by X's rules and we will not pretend otherwise. If you would rather read a vendor-by-vendor view before authorising anything, our Circleboom review covers what its account-management side actually does.

#Bottom line

Deleting all your posts on X is a three-part job: get the archive, pick a tool that can reach past 3,200 posts, then revoke it when the run ends. The 3,200 ceiling is the detail that decides which tools can finish the work, the pay-per-usage API is why free tiers are capped at 50 a day rather than infinite, and permanence is why the archive request comes first. Do it in that order and the worst outcome is a slow afternoon. Do it backwards and the worst outcome is a decade of posts you can never read again.