A retweet cleaner is a tool that finds the reposts on your X profile and removes them as a batch, while the posts you wrote and the originals you shared stay where they are. The part worth knowing before a first run is where it stops, because a cleaner that works through the X API never sees past your latest 3,200 posts.
What a retweet cleaner changes on X.
- It removes your reposts from your profile in one filtered batch.
- It leaves each original post, with its likes and replies, on its author's account.
- It reaches retweets in your latest 3,200 posts directly and older ones through your X archive.
Circleboom clears retweets from X profiles in bulk, and it does so as a customer of X's Enterprise API tier. Open Circleboom and run a → retweet cleaner on your X profile.
What does a retweet cleaner remove from your X profile?
A retweet cleaner removes the retweets your account made, and nothing else, as long as it is told to look at retweets only. Your original posts and your replies are a different post type, and a good cleanup leaves them alone.
The need usually appears at a turning point. Retweet history is part of the public record of an account, visible to anyone who opens the profile before a hire, a launch, or a partnership.
Years of reposts can tell that visitor more about what the account used to watch than about what it does now.
Removing reposts on X by hand means undoing them one at a time, and X has no bulk option for it. A retweet cleaner turns that into one filtered job: list the retweets, review them, delete the selection.
Cleaning retweets is one job inside a wider Twitter cleaner routine. It is usually the lowest-risk place to start, because a repost is someone else's content and removing it deletes none of your own writing.
Circleboom works as a retweet cleaner for X by loading your posts into a filterable table. The table does the searching, and every removal stays your call.
The original post stays on X after you clean your retweets
Everything attached to the original stays with it. Only your repost leaves your profile.
| Item | After a retweet cleanup |
|---|---|
| Your repost on your profile | Removed |
| The post you shared, on its author's account | Stays, with its likes and replies |
| Posts and replies you wrote | Stay, as long as the filter is set to retweets |
| Other accounts' reposts of things you wrote | Stay, because only those accounts can undo them |
| Cached views and cross-posted copies | Can lag behind and display the repost briefly |
The last row comes from X itself. X's answers on reposts state that the original post survives when you undo a repost. They also warn that stale timeline views, or copies shared to other services, can keep displaying it for a time.
Two practical consequences follow. First, a cleanup is safe for the people you reposted, since their posts and conversations stay put.
Second, timing matters: if the cleanup is for an interview or a launch, run it ahead of the date so stale views have time to clear.
Removing a retweet versus deleting a post you wrote
The two actions look alike in a cleanup tool, and they are not. Deleting one of your own posts removes its text, media, engagement counts, and impressions from your timeline for good.
Replies, retweets, and quotes that other accounts made of it can still exist, because that content belongs to them.
Removing a retweet takes away only your share. The post you shared keeps its full life on its author's account.
That difference is why the Post Type filter matters more than any other setting in a retweet cleanup. Set to retweets, the run touches amplification only. Left open, it reaches the posts you wrote.
The one-at-a-time version of the same action, how to remove reposts on X, is worth knowing for the odd single repost you notice later.
One edge case sits outside this comparison. If the repost icon on a post will not respond at all, that is a different problem from cleanup. The retweet button greyed out case is worth ruling out before you blame the tool.
Circleboom cleans retweets on X from one filtered table
Circleboom cleans retweets on X with Delete My Last Tweets. The tool pulls your most recent posts, with a ceiling of 3,200, straight from the X API without any archive file, then sorts them by post type before anything is removed.
Filter Options holds the controls that turn a timeline into a retweet list:
- Post Type, set to retweets.
- Date, for a window of creation dates.
- Keyword / Username or Hashtag, matching text contained in the post.
- Language and Media, for narrower passes.
Each row has a link icon for viewing the post on X, so any doubtful retweet can be checked before it goes. The Export button saves the list as a CSV first, and Delete Selected removes only what is still checked.
One default shapes every run. The table loads with every post pre-selected, which means Delete All on an unfiltered table would clear your recent timeline, not only your retweets. Set Post Type first, then read the count.
The deletions run through X's own API with approved access rather than a scraper, and nothing leaves your profile until you press a delete button.
On a first run I filter by date as well as type, so the batch is short enough to read in full.
When the reposts you want gone fall within that 3,200-post range, the table does the finding and you can clear your X retweets in bulk from one screen.
Keeping some retweets on purpose
A cleanup does not have to empty the list. Deselecting a row is how you keep a retweet: after the filter, uncheck the reposts you still stand behind, such as a colleague's research or a partner's announcement, and only the checked rows go when you press Delete Selected.
Where a retweet cleaner stops: your latest 3,200 posts
A retweet cleaner that works through the X API hits a wall at your newest 3,200 posts, because that is the most the API returns for any account. Retweets older than that are invisible to the recent table, however many filters you set.
Older retweets need your X archive. Circleboom's Delete All Tweets tool works from tweet.js, the file inside it that holds your post history. Its post-type checkboxes arrive fully ticked, so a retweet-only pass means clearing Tweets and Replies while ReTweets stays on.
Before you confirm, the Approve & Delete panel breaks the run down by post type. If only retweets appear in that count, the boxes are set right.
The archive route's start and end dates let you delete tweets by date and aim an old-retweet cleanup at the years you choose.
How to tell whether your retweets sit past the line
Check the table before you request anything. The top of Delete My Last Tweets shows how many posts it loaded, and each row carries its Created At date with the relative age.
If the count is well under 3,200, the table most likely reaches back to the start of your account, and the oldest Created At date confirms it. If the count sits at the cap, compare the oldest date with the retweets you remember.
Anything older than that date is an archive job.
Retweets, replies, and your own posts all share the same 3,200-post window. An account that reposts often fills that window faster, so its recent table can cover a much shorter stretch of time than its age suggests.
Timing the archive route
You request the archive from X first, and it can arrive a day or two later. Circleboom takes tweet.js alone rather than the ZIP, and it will only process a file that came from the X account you connected.
Use the wait. Run the recent pass from Delete My Last Tweets while the archive is being prepared. By the time the file arrives, only the old retweets are left, and the archive route skips anything already deleted, so the two passes never collide.
If you want your retweets and tweets in a click rather than retweets alone, leave all three boxes checked. A Protect List keeps named posts safe either way.
How to run a retweet cleaner on your X profile
To run a retweet cleaner on X, bring your recent posts up in a table you can filter, narrow it to retweets, save a record, and delete the selection. In Circleboom that is four moves inside Delete My Last Tweets, all from the Essential Toolbox.
- Load your latest posts by opening Delete My Last Tweets; up to 3,200 appear without an archive.
- Filter to retweets with Post Type in Filter Options, and apply the filter before selecting anything.
- Export a CSV record of the filtered list, since deletion on X is permanent and has no undo.
- Delete the selection with Delete Selected, not Delete All.
The order protects you twice. The filter keeps your own posts out of the run, and the CSV is your one record of what the run removed.
Is there a free retweet cleaner for X?
Yes. Circleboom's free Delete your ReTweets tool handles 50 retweet removals daily, and the count refreshes each day.
That daily cap makes the free route a good fit for short histories and a slow one for long ones. The three Circleboom routes compare like this:
| Route | What it reaches | Pace | What you need |
|---|---|---|---|
| Delete your ReTweets (free) | Your retweet history, listed for selection | 50 removals per day on the free plan | A connected X account |
| Delete My Last Tweets | Retweets inside your newest 3,200 posts | 150 deletions per 15 minutes | A connected X account |
| Delete All Tweets | Retweets anywhere in your history | 150 deletions per 15 minutes | Your archive's tweet.js file |
The paced-route figure comes from Circleboom's published deletion speeds, which list a rate of 150 tweet deletions every 15 minutes. As an illustrative calculation, a history of 1,000 retweets takes 20 days at the free cap and roughly an hour and forty minutes at the paced rate.
Choosing between the free and paced routes
Pick by the size of your history and the date you need the profile clean:
- A short retweet history and no deadline: the free route clears it in a few daily sessions.
- A long history or a fixed date, such as an interview or a launch: the paced route clears retweets in your latest 3,200 posts in one run.
- Reposts from before your newest 3,200 posts: only the archive route reaches them.
To start on the free plan, open the tool to delete retweets and work through the list in daily batches. Each session removes up to the day's allowance, and the allowance resets the next day for the following batch.
On a phone, the same job has its own page to delete retweets on your iPhone.
On a phone instead? Circleboom's walkthrough for deleting all retweets on iPhone, quickly.
https://www.youtube.com/watch?v=PcICc7pKTYY
Leaving old retweets on X costs you first impressions
Without a cleanup, your profile keeps pointing visitors at launches, events, and accounts you stopped following long ago, and you answer for that in every first impression. With one, the profile shows what you post now, and the people you once reposted keep their posts untouched.
The work is smaller than it looks. Retweets in your latest 3,200 posts clear from one filtered table, older ones clear from your archive, and an export before each run keeps a record of every repost you removed.
A retweet you no longer stand behind still speaks for you until you remove it.
→ Delete old retweets on X with Circleboom
What to know about retweet cleaners on Twitter
Why won't some of my retweets delete?
Three explanations cover a stuck retweet: it sits outside the reach of the route you used, it is still waiting in a paced run, or a cached view is still showing it. Anything past the 3,200-post window belongs to the archive route, and big batches complete in stages, so leave the browser open.
For the reasons tied to likes as well, see why you can't delete retweets and likes.
How do I keep retweets from piling up on X again?
For posts of your own that you reshare, give the repost an end date. Inside Circleboom's X Post Planner, the Auto Repost / Un-RePost panel schedules a repost and can also schedule its removal, so planned reposts do not accumulate.
For other people's posts, run the retweet filter regularly and remove what no longer fits.
