How to delete tweets in bulk on X: the archive, the tools and the limits

X (formerly Twitter) has no bulk delete. Its help page says so directly: "We do not provide a way to bulk-delete posts. You can only delete posts manually, one by one." (X Help Center, checked 18 October 2026.) Every tool that removes many posts at once is repeating that single deletion for you. It does this in one of two ways: through X's paid API, at 50 deletes per 15 minutes per account, or by clicking through your logged-in session as a browser extension or desktop app. Download your archive before you start. It is your backup, and it holds the post IDs that API tools need to reach anything older than your latest 3,200 posts.

Can you delete all your tweets at once on X?

No. X has no delete-all button, no date filter for deletion and no batch option on the website or in the apps. You delete your own posts one at a time from each post's menu. Every bulk method is software that repeats that single action for you, post by post. The methods differ only in who does the repeating, how fast, how far back it reaches, and what it costs.

Deletion also does less than many people expect. According to the same help page (checked 18 October 2026), a deleted post goes from your account, from your followers' timelines and from X search, and reposts of it go too. These remain:

• Quote posts, where someone reposted you with their own comment.
• Copies that other people pasted into their own posts.
• Copies held by third-party sites, apps and search engines, which X says it cannot remove.

Bulk deletion tidies your profile and X search. It does not recall anything that has already been quoted, screenshotted or indexed elsewhere.

The three ways to delete tweets in bulk

In October 2026 there are three working ways to delete tweets in bulk. You can delete by hand from search results. You can use a tool that calls X's paid API once per post. Or you can use an extension or desktop app that works through your own logged-in session. They differ in speed, in how far back they reach, in whether they can remove likes, and in how they sit against X's automation rules.

By hand from search

This is the only route that needs no tool and no authorisation. TweetDelete's own guide describes the method: use Advanced Search to narrow results to your account, a word and a date range, then delete each result on web or mobile. The X help pages read for this post do not document that search method, so test the filters before you rely on them. It works for a few dozen posts. It is impractical for thousands.

A tool on the X API

You authorise an API tool on your account. It then sends one request per post to X's delete endpoint, which X's API docs describe as: "Deletes a specific Post by its ID, if owned by the authenticated user." There is no batch version. The rate-limits page caps the endpoint at "50/15min" per user, and X bills every request (see the cost section below).

An extension or app in your own session

Session-based tools work inside the browser where you are already logged in. They do what you would do by hand, only faster. TweetStorm's extension for Chrome and Firefox deletes this way, one item at a time. Desktop apps such as Redact also run locally: its page says "The deletions run on your device". A tool that does not go through the API is not bound by the API's rate limit or billed per request. The vendor pages read for this post do not say how fast these tools run.

Tools, from their own pages

Prices appear here only where the vendor's own page showed them on 18 October 2026. Labels such as "official X partner" are the vendors' own claims and were not checked with X.

Download your X archive before you delete anything

Request your X archive before any bulk deletion, for two reasons. It is your own copy of what you are about to remove. It also holds the post IDs that tools need to reach anything older than your latest 3,200 posts. X describes it as a "machine-readable archive of information associated with your account in HTML and JSON files" (X Help Center, checked 18 October 2026).

1. Go to Settings and privacy, then Account, then Your X data.
2. Verify yourself with the code X sends by email or phone.
3. Select Request data.
4. Wait for X's email or push notification that the archive is ready. X says: "It may take a few days for us to prepare the download of your X archive."
5. Download it in the same browser where you are logged in to the account. Your email address must be confirmed.
6. Keep a copy somewhere other than the computer you are cleaning from.

Source: How to download your X archive, checked 18 October 2026. X gives no firmer time than "a few days". Third-party blogs quote shorter waits and a limited download window, but X's page does not, so do not plan around them. One third-party source (Stashr) reports that the archive includes likes but not bookmarks. The X pages read for this post do not confirm that.

Why tools only see your last 3,200 tweets, and how to delete older ones

A tool that reads your posts through the X API can only see your most recent 3,200 of them, or 800 if replies are excluded. X's timeline docs (checked 18 October 2026) say: "Requesting Posts beyond these limits returns a successful response with no data." The tool gets no error. It simply sees nothing more. That is why a cleaner can report nothing left to delete while old posts are still on your profile.

The delete endpoint works by post ID, so the fix is to hand the tool the IDs directly, and your archive contains them. This is why TweetEraser and TweetDeleter offer archive upload to reach all your tweets, and why Redact Premium imports your X data export. Circleboom advertises deletion "including tweets beyond the 3,200-tweet API limit". To bulk delete old tweets:

1. Request your archive and wait for it to arrive.
2. Choose a tool that accepts your archive files.
3. Set the filter: everything, everything before a date, or posts containing a word.
4. Let the tool work through the list at whatever pace its route allows.
5. Check your profile and X search afterwards for anything it missed.

How long bulk deleting takes, and what the X API costs

Through the X API, one account can delete at most 50 posts per 15 minutes. That works out at 200 an hour, or 4,800 a day if the tool never pauses. The 50 per 15 minutes figure is X's limit for the delete endpoint (rate-limits page, checked 18 October 2026). The hourly and daily numbers are arithmetic from it, not figures X publishes.

XWipe's guide gives similar estimates from the same limit: about 5 hours for 1,000 tweets and about 2 days for 10,000. These are minimums. Any pause or failed request adds to them.

On cost, X's pricing page says: "The X API uses pay-per-usage pricing with no subscriptions." The monthly Basic and Pro tiers are gone, and there is no free self-serve tier for this use. The rate card lists "Interaction: Delete" at $0.010 per request and "Content: Manage" at $0.005 per request. Owned reads of your own data cost $0.001 per resource from 20 April 2026. The docs read for this post do not say which line a post delete is billed under, so budget about a cent or less per delete and check the Developer Console. If a vendor holds the API access, the per-request cost sits inside its own price. For the account limits that apply alongside these API numbers, see X rate limits in 2026.

Deleting likes, replies and retweets in bulk

Replies delete exactly like posts. Retweets are undone, not deleted. Likes are the hard part: since 20 April 2026, X's self-serve API can no longer remove them. Each one needs a different approach.

Replies

A reply is a post, so it goes through the same delete endpoint and the same 50 per 15 minutes limit. Most tools treat replies as a filter option. Keep the timeline cap in mind: when replies are excluded, the API timeline returns 800 posts rather than 3,200, so a tool that skips replies while reading sees even less of your history. The archive avoids the problem.

Retweets (reposts)

X's help page says you remove a repost of someone else's post by undoing it, not by deleting it. When a tool lists retweets among the things it clears, the action underneath is an undo. The original post stays on its author's account.

Likes

From 20 April 2026, X removed following, likes and quote-posting through API writes from all self-serve tiers. The announcement names "POST /2/users/{id}/likes (and DELETE for unlike)". The changelog says: "Following, Likes, and Quote-Posts via the API have been removed from all self-serve tiers." A tool on X's self-serve API can therefore no longer bulk unlike. That leaves Enterprise API access, or tools that work inside your own browser session.

Redact, TweetDelete and TweetEraser all list likes on their own pages. None of those pages, as read, says how they remove likes now that the self-serve unlike endpoint is gone, so ask before you pay. If the answer is that the tool clicks unlike in your browser, it belongs with the session-based tools above, and the same rule applies.

How to auto delete tweets older than a set number of days

X has no native auto delete. A rolling rule, such as deleting anything older than a month, exists only as a scheduled feature in third-party tools. TweetDelete says you can "run it once or automatically on a schedule", and TweetEraser offers automatic tasks that run in the background (both checked 18 October 2026).

Before you switch one on, consider three practical points:

• The tool keeps access to your account for as long as the schedule runs. The authorisation is not a one-off.
• Each run uses the same one-post-at-a-time delete. For API tools, that means the same rate limit and the same per-request billing. Once the backlog is cleared, each run only removes posts that have crossed the age line since the last one, which is a much smaller job.
• Download a fresh archive before the first run and at intervals afterwards. Once the rule has removed a post, your archive is the only copy you hold.

Can mass deleting tweets get your account locked?

Nobody outside X can say for certain. X publishes no limit on deleting your own posts beyond the API's 50 per 15 minutes per user. It does not say whether fast deletion through the website triggers locks or limits, and its automation rules do not address deleting your own posts. Because X does not publish its detection rules, any confident answer either way is a guess.

Here is what can be said. API tools work within a limit X publishes for that exact action. Session-based tools fall under the ground rule against "scripting the X website" quoted above, which names permanent suspension as a possible result. If an account is locked partway through a clean-up, stop the tool before you deal with the lock. X account locked: the three official routes out covers what to do next, and why X accounts get suspended covers the wider picture.

Giving a deleter access, and taking it back

• API tools: you authorise them on X. When the job is done and you are not using a schedule, revoke the app's access in X's settings and close your account with the vendor. X's help page on connected apps was not checked for this post, so follow the wording in your current settings.
• Extensions and session-based apps: they act inside your own logged-in browser, so there may be no app to revoke on X. Uninstall the extension when you have finished.
• Either way, read what a tool asks permission to do before you grant it, and prefer one that states plainly where the deletions run.

Bulk deleting tweets across several X accounts

Every limit, archive and authorisation in this process is per account. Cleaning ten accounts means ten archive requests, ten verification codes, ten authorisations or logins, and ten separate delete queues. Each queue is capped at 50 deletes per 15 minutes through the API. X states the limit per user, so one account's queue does not use up another's allowance.

For session-based tools, separation matters more than speed. If you run one deleter in one browser and log in and out of many accounts, all of those accounts pass through the same browser and the same connection. If your accounts already live in separate profiles, run the deleter in each account's own profile. flottra, for example, keeps a separate saved browser profile and proxy for each account on your Windows computer, but it does not delete posts and is not the tool for this job. For the wider setup, see how many X accounts you can have, and how to run them and X automation in 2026: what actually works.