Rate Limits & Deletion Speed

How Rate Limiting Works

X limits how quickly you can send requests. XeetDelete handles this automatically — if it hits a rate limit, it pauses for 60 seconds and retries. You don't need to do anything. If the script gets rate-limited 10 times in a row, it stops as a safety measure — run it again later and it will resume where it left off.

Choosing a Delay

Before copying the script, you can set a delay between each deletion: 1s, 1.5s, 2s, or 3s. A slower delay reduces the chance of hitting rate limits but takes longer. For large archives, a 1.5s–2s delay is a good balance.

Large Archives (50,000+ tweets)

If you're deleting a very large number of tweets, XeetDelete will show an estimated completion time. Consider breaking the job into smaller batches using date range filters — for example, delete one year at a time.