How to Delete More Than 3,200 Tweets (Why Tools Stop and the Fix)
Many tweet deleters stop at 3,200 tweets because the X API only returns a user's most recent 3,200 posts. Older posts can still be deleted by a tool that reads your X archive, the file X gives you with your full post history. TweetCleaner works from that archive, so posts older than the 3,200 limit can be deleted too.
Why tools stop at 3,200 tweets
A tool that works only through an app connection asks the X API for the list of your posts, then deletes what is on that list. The API returns up to the 3,200 most recent posts (Timelines, X API documentation).
For anything older, the tool has no list to work from. It finishes its 3,200 and your older tweets are still there.
Why the archive removes the limit
Your X archive contains every post, starting with your first one. A tool that reads the archive takes the list of posts from that file instead of the API, so the 3,200 limit does not apply.
| Approach | What it can delete | Preparation |
|---|---|---|
| App connection only | Your most recent 3,200 posts | None |
| Reads your X archive | Every post in the archive | Request the archive from X and download it |
How to delete more than 3,200 tweets
-
Request your archive from X
In X, open Settings and privacy, then Your account, then Download an archive of your data. Confirm your password and select Request archive.
-
Download the ZIP file when it is ready
X sends an email or an app notification when the archive is ready. X says it may take a few days to prepare (How to download your X archive, X Help Center).
-
Sign in to TweetCleaner with X
Use the same X account that requested the archive.
-
Upload the ZIP file
Upload it as it is. If the file is very large, unzip it and upload only the tweets.js file from the data folder. Uploading does not delete anything.
-
Check the number of posts found, set your conditions, and confirm
The options screen shows Tweets Found. Delete everything, or set conditions to keep some posts, then confirm.

If you see "Please check your archive."
This appears when the uploaded archive cannot be matched to the account you are signed in with. The screen lists two possible causes:
- The archive does not belong to the logged-in account
- An archive file (tweets.js) already used by the deletion tool was uploaded
Upload the latest archive requested from the account you are signed in with. If you use several accounts, check that the account signed in to X is the owner of the archive.
If you only want to delete some tweets
- Delete a certain period only: How to delete old tweets by date range
- Clear the whole timeline: How to delete all tweets at once
Good to know
- The archive is a snapshot taken when you requested it. Posts you publish after that are not in it.
- Deleted posts cannot be restored. That is how X works. Keep the ZIP file as your own backup.
- The ZIP file is deleted right after the post data is extracted. Post text is automatically deleted after about 24 hours. After that, only post IDs, dates, and like and repost counts are kept, and these are removed too when you use the delete-data option.
- For the effect of bulk deletion on your account, see the FAQ: Could bulk deletion get my account suspended or restricted?
Frequently asked questions
Can I delete tweets older than 3,200 without the archive?
Not with TweetCleaner. The X API alone cannot list posts older than your most recent 3,200, so the archive is required.
Do I have to unzip the archive?
No. Upload the ZIP file as it is. Use the tweets.js file from the data folder only when the ZIP is very large.
I have fewer than 3,200 tweets. Do I still need the archive?
Yes. TweetCleaner always works from the archive, whatever the number of posts.
Does it work on a protected (private) account?
Yes. Protected accounts can delete posts the same way as public accounts.
This guide is written by the team behind TweetCleaner, a tweet deleter to mass delete tweets on X, based on the actual screens and X's official documentation.