Most people who go looking for a tweet deletion limit have already hit one. The free tool stopped at 50, the app made them delete posts one by one, or a bulk tool showed 3,200 tweets when they know they have written far more.
Each of those stops has a different cause, and each has a different way around it.
Manual on X: one post per tap, no filters, and no reach past what you can scroll to. Circleboom: deletes your tweets on X in paced bulk runs from the full archive, up to 14,400 a day, through X's official Enterprise API access.
→ Run a full-history delete beyond the free tweet deletion limit
Choose your route first; the steps follow.
Why the tweet deletion limit on Twitter changes from tool to tool
The tweet deletion limit changes from tool to tool because more than one thing sets it, and a number quoted on one site rarely describes the same thing as a number quoted on another.
The X app has no bulk delete, so every post costs a few taps of its own. A free tool such as Circleboom's Delete your Tweets caps you at 50 per day, resetting daily. Bulk tools sit underneath X's API pace, which every tool has to respect.
That last limit works in time windows. X's developer documentation on API rate limits explains that requests are counted per endpoint, in windows that are usually 15 minutes or 24 hours.
Going past a limit returns a 429 error until the window resets.
A bulk tool that ignores those windows does not delete faster; it gets refused and stalls.
The fix depends on which of these you hit. A cap of 50 calls for a different route, a list that ends at 3,200 calls for a file, and a worry about speed is answered by the pace itself.
The useful question is which route matches the size of your history, and the answer decides whether you need your archive. If you already know your history is large, you can launch a bulk tweet delete paced to the tweet deletion limit and skip the guesswork.
Why can't tools reach more than 3,200 of your tweets on X?
Tools that work through X's API can only reach your 3,200 most recent tweets, because that is all the API returns for any account. Everything older stays out of the queue, however fast the tool deletes.
The way past the ceiling is your X archive. X lets you download your X archive from your account settings. The file inside it called tweet.js holds every tweet you have posted, regardless of age or volume.
Circleboom's Delete All Tweets reads that file instead of the API timeline. An account with 25,000 tweets can reach only the latest 3,200 through the API; uploading the archive brings all 25,000 into the cleanup.
That is the job a Twitter archive eraser does, and it is why long-running accounts need it.
The archive is also your backup. Once the run finishes, the downloaded file is the only record of what you posted, so it is worth keeping somewhere safe. Circleboom's page to delete old tweets with your archive covers the same route from the product side.
Is a bulk deletion run safe for your X account?
A bulk deletion run is safe when it stays inside X's rules and API pace, and Circleboom performs every deletion that way. Its published pace for Delete Tweet is 150 requests every 15 minutes, or 14,400 per day, with tweets removed one by one and a short pause between each.
That pacing, the real tweet deletion limit for bulk tools, keeps a cleanup inside what X accepts. Hand-deleting at speed, or using a tool that fires requests as fast as it can, is what rate limits are built to stop.
A queue that sends single deletions at an accepted rhythm never asks X for more than it allows.
Circleboom works this way because it is a listed X Enterprise customer, with access granted by X itself rather than workarounds. Circleboom removes tweets from your Twitter history through that access, so a long run takes time but stays inside what X allows.
The flow behind a bulk tweet delete in 3 simple steps is the same one described below.
If you are ready, you can erase your full tweet history in paced batches once the archive is in hand.
Under 3,200 tweets or more: pick your Twitter deletion route first
Your route around the tweet deletion limit depends on one question: are the tweets you want gone inside your latest 3,200, or older than that?
Inside the latest 3,200. Delete My Last Tweets loads your recent tweets through the API, with no archive to request or upload. It is the faster start, and the same paced bulk rate applies.
Every post loads pre-selected, so filter or deselect before you delete.
Older than the latest 3,200, or the whole history. Delete All Tweets is the route, and it starts with your X archive. X can take 24 to 48 hours to prepare the file, so request it before anything else if the cleanup has a deadline.
When in doubt, use the archive.
It covers recent tweets too, so it never leaves part of the history out, and the steps below follow that route.
Back up your X history and decide what stays
A few minutes of preparation protect against the one thing a deletion run cannot fix, which is deleting the wrong thing:
- Keep the downloaded archive; it is the only record once the run is done.
- Export Tweets to a spreadsheet if you want a reviewable list, as an extra, not a replacement for the archive.
- Note your best performers in Post Analytics so you can protect or reuse them.
- Tell the team or client first if the account is shared or owned by a brand.
Old tweets can carry announcements, customer answers and backlinks. Deciding what survives before the upload is faster than regretting it after.
What to upload when your Twitter archive is too big
Upload only the tweet.js file, never the whole archive ZIP. If tweet.js itself is larger than 100 MB, compress that single file into a zip or gzip and upload the compressed copy instead.
Circleboom's page on uploading Twitter archive files larger than 100 MB lists the file names it accepts for a compressed upload:
- tweet.js.zip or tweet.zip.
- tweet.gz.
- archive.zip or archive.gz.
The file sits in the data folder of the extracted archive, and on some downloads it appears as tweets.js, tweet or tweets.
Circleboom discards any file other than tweet.js inside an uploaded archive, so sending the full folder adds size without adding anything.
If an upload still fails after compressing, Circleboom's support team accepts the tweets.js file directly and handles the upload for you, as the same help page explains.
Two more checks save a failed upload. The file has to come from the same X account that is linked to your Circleboom subscription, or it will not be processed. And the walkthrough on how to delete your Twitter archive history shows the archive folder for anyone unsure which file is which.
How to delete tweets past the tweet deletion limit with your X archive
The archive route end to end: requesting the file on X and erasing its tweets on Circleboom.
Seven steps take you from sign-in to a confirmed run.
Log in and open the delete tools
- Log in to Circleboom with the X account whose tweet history you are clearing.
- Open the Essential Toolbox menu and select Delete All Tweets from Delete Tools.
Get the tweet.js file out of your X archive
- Request your archive on X under Settings and privacy, "Download an archive of your data," and download it when X's email arrives.
- Extract the archive and upload tweet.js from its data folder by drag and drop, compressing it first if it is over 100 MB.
Run the deletion, then re-run when you need to
- Review the uploaded count and the Approve & Delete panel, adding any post you want to keep to the Protect List; a date range is one way to narrow a run to a single era.
- Click "Delete my Tweets" and leave the browser open until the queue completes. The same tweet.js file can be uploaded again later for a separate run with different filters, because Circleboom excludes tweets that are already deleted.
- Upload the file again for any second pass, such as clearing only retweets after an earlier run kept them.
Requesting the archive early means the 24 to 48 hour wait is already behind you when you reach the count, and re-uploading the same file lets one archive serve every pass instead of a fresh wait.
How re-uploading tweet.js stages a Twitter cleanup
The re-upload is what turns one archive into a staged cleanup. A common sequence looks like this:
- A first pass with a date cut-off that clears everything before a rebrand.
- A second pass on the same file that removes a former employer's name with a keyword.
- A third pass that keeps only the ReTweets box checked to clear old amplification.
Each pass starts from the same tweet.js, and none of them touches tweets an earlier pass already removed.
Staging the work this way also keeps each Approve & Delete count small enough to read properly.
Tweets are only part of a cleanup. Old retweets and likes sometimes survive after the original post or its author disappears, and the guide to delete leftover retweets and likes covers those stubborn cases.
Likes have their own archive route as well. Past your latest 3,200 likes, Circleboom's page to remove all your Twitter likes works from the like.js file the same way tweet.js works for tweets.
What it costs to skip the archive route on X
Without the archive, a cleanup stops at the 3,200 most recent tweets or crawls at 50 a day, and the oldest posts, usually the ones you most want gone, stay public.
With it, every tweet you ever posted enters a paced queue that clears up to 14,400 a day.
Plan around the tweet deletion limit instead of fighting it.
The archive gives you reach, X's pace keeps the account safe, and the re-upload covers any pass you did not think of the first time.
One easy mistake is starting a run on the API window, finding the old years untouched, and only then requesting the archive. Request it first, and the 24 to 48 hour wait runs while you decide what to keep.
Deletion is permanent, so keep the archive you downloaded. Circleboom handles everything in between as a company verified on X's Enterprise customer directory, so the account you are cleaning stays in good standing while the history goes.
→ Run a paced bulk tweet delete from your full archive
Questions about daily delete caps on X
What if I need to halt a deletion queue on X midway?
Yes. Revoking Circleboom's access to your X account stops all active deletion queues, usually within seconds of the change being detected. If you resume later, uploading the same tweet.js file skips the tweets that are already gone.
Should I stay on 50 free deletions a day or switch to bulk?
Stay on the free tool for a few hundred tweets if you can return daily, since the allowance resets every day. For thousands of tweets or anything older than your latest 3,200, the archive-based bulk route finishes in days instead of months.
Can I keep a few tweets while deleting everything else?
Yes. Add those posts to the Protect List before you confirm, and Circleboom leaves them on your timeline while the rest of the selected tweets are deleted.
Will deleting my tweets remove other people's replies and quote tweets?
No. Replies, retweets and quote tweets that other accounts made of your posts belong to those accounts, so they may still exist on X after your tweets are deleted.
Do old links to my tweets still work after a cleanup?
No. Links, embeds and references to a deleted tweet break or lose their context, so check whether any post still earns traffic or serves as proof before you include it in a run.
