An effective way to delete all your Tweets.
If this script was useful to you and you would like to support my work, you can buy me a coffee through the link below.
Please proceed with caution. There is no going back after you delete your Tweets. Do it at your own risk!
Here's how I deleted all my Tweets. You can run this scrip on any machine with Python installed.
This script does not require access to the Twitter official API to delete your tweets. Instead, it communicates with Twitter the same way that browser app communicates with TWitter servers - trough GraphQL calls.
The first thing you should do is request your Twitter/X archive. Blue Delete uses the archive files to know which Tweets to delete. It usually takes 24 hours for Twitter/X to get your archive ready.
So, request your archive and work on the other steps below while you wait for your archive to be ready.
You can so by going to Settings and privacy > Your account > Download and archive of your data either through the X app or the website.
Once the archive is ready for download, unzip the tweet archive and copy the tweets.js file to the same folder where you placed this python script. tweets.js contains the information to all your tweets.
Login to your Twitter/X account through a web browser on a desktop computer. The instructions below are for Chromium but they should be the same in all browsers.
Open your browser developer tools by pressing Ctrl + Shift + I on the keyboard and go to the Network tab. This is where you can see all the traffic between your browser (your computer)
and the network operations it is performing.
Still on your Twitter/X page, go to your profile page and choose a single Tweet to delete. Make sure that network traffic is being recorded. The record button should be red.
Delete the Tweet and press the red record button to stop recording network traffic.
Find the entry labeled DeleteTweet. Right-click on this entry and choose Copy > Copy as cURL (bash). This will put the cURL command in your clipboard.
Open the file names curl.txt and replace all the content of the file with the cURL command from the step above. This will be used to extract all your session and cookie information.
Browser reverse engineering is fun, huh?
Time to run the script and delete all your Tweets. Proceed with caution, there is no going back.
The script will read all your tweets from the archive, and will make API calls to delete each one of them. It keeps track of tweets that have been deleted in a file called tracking.json.
If the process is interrupted for some reason, it doesn't have to start from the beginning again.
It will take a 5 minute break after 101 deleted Tweets. I'm sure there is a rate limit on how many calls can be made to the GraphQL API, but I don't know what the limit is. I figured around 100 or so requests every 5 minutes will fly under the radar. I deleted some 2500 tweets with these settings without running into a rate limit.
If you want to run it faster, just edit these settings:
# Take a break after deleting this many Tweets+1
# This is to prevent hitting any rate limit on the GraphQL API
pause_after = 200
# Break for how long - in seconds
pause_length = 150Yep, it does work. It probably means your authentication is failing. Follow the steps to copy the cURL request from the web browser and save it to a file names curl.txt
Not that I can tell but proceed at your own risk. It is using an undocumented GraphQL API. The requests look just like deleting a Tweet using Twitter/X through a web browser
Yeah, you can run it as many times as you want. Check the tracking.json file if any Tweets are still pending. All the Tweets marked as deleted will not go through the script again.