Tweets & Likes,
Wiped Clean at Once

Go to X (Twitter) > Settings > Account > Download Data Archive to submit your request. A download link is usually sent to your email within 24-48 hours.

Your archive files and personal data are processed entirely within your browser and are never sent externally. However, anonymous deletion counts (e.g., '500 tweets deleted') are collected for service improvement. No account information or tweet content is included.

Deleted tweets cannot be recovered. That's why simulation mode is enabled by default, allowing you to review results before any deletion takes place.

Due to X API rate limits, tweets are processed at approximately 200 per 15 minutes and likes at approximately 500 per 15 minutes. TweetManager automatically manages the pacing.

Yes. You can designate tweets to preserve using a variety of filters including date range, keywords, like/retweet counts, and pinned tweet threads.

Simulation mode and archive analysis are free. You can also try actual deletion, unliking, and blocking with a 30-minute free trial. After that, a one-time payment of $3.99 gives you 30 days of unlimited access.

Yes. If the original author of a tweet you retweeted has been suspended or deactivated, that retweet won't appear on your timeline or in your archive file. These 'zombie tweets' are a structural limitation of X and cannot be deleted by any tool.

It's possible. X enforces rate limits and anti-abuse heuristics, and we've seen user reports of accounts being suspended after bulk-deleting thousands of tweets in a single session. TweetManager already paces requests within X's published limits (~200 tweets / 15 minutes, ~500 likes / 15 minutes), but if you are running archive mode against a very large history, consider splitting the work across several days rather than clearing it all at once. This risk exists with any deletion tool, not only TweetManager.

X allows roughly 200 deletions every 15 minutes. That cap is the real bottleneck. TweetManager's default 4.5-second interval is the theoretical minimum that rides the cap exactly while eliminating bursts. Shortening the interval barely changes the total duration — it only changes the shape of the request pattern, and the flatter that pattern stays, the less it looks like a bot.

Total time barely moves as the slider moves, because X's cap — not our pacing — sets the bottleneck. A wider interval doesn't cost speed; it straightens the request pattern along the cap line.