DELETE.1999

You wrote it. You can unwrite it.

Delete your X history

Upload your archive, say exactly what goes, and leave. The job runs on a server, so it keeps going with the tab shut, the laptop closed and you asleep. It has to: X allows fifty deletions every fifteen minutes, and twenty thousand posts is four days of waiting.

Official API, OAuth 2.0, no password 50 deletes / 15 min Dry run first, always
1

Connect your X account

You approve this on x.com. We never see your password, and you can revoke it in two clicks.

Bring your own X app. X makes every tool use a developer app. Making one takes about three minutes, and it keeps the rate limits and the bill on your account instead of ours. The free tier ended in February 2026, so you will buy credits from X directly — at cost, with nothing added by us. Show me how →

Encrypted (AES-256-GCM) against your session and thrown away when you disconnect.

Opens x.com. You approve the permissions there.
2

Where the list comes from

If you have posted more than about 3,200 times, the archive is the only source that can see all of it.

Getting your archive: on x.com, Settings → Your account → Download an archive of your data. X emails a link, usually inside 24 hours. Upload the .zip exactly as it arrives — do not unpack it first.
Drop your archive here, or click to browse Takes the whole twitter-….zip, or a single tweets.js / like.js
3

What goes

Filters run again on the server before anything is deleted. Nothing outside this selection is ever touched.

0 selected
Saves your greatest hits from your worst decade.

Preview

Showing the first 100 matches
Load a source in step 2 and the list appears here.
4

Check it, then run it

Do the dry run. It calls no delete endpoint and hands you the exact list that would have gone.

Selected
0
Rate limit
50 /15m
Est. duration
—
Cost
$0
Read this bit.
  • Deletion is permanent. X has no undo and no bin. Whatever you tick here is gone for good.
  • A long job is normal, not a bug. Fifty deletions per fifteen minutes means 20,000 posts takes about four days.
  • Bursts of automated activity can get an account temporarily locked. This paces itself on purpose. Do not run two jobs against one account to go faster.
  • Keep the .zip. Once the posts are gone it is the only copy of them that exists.
Pause or cancel at any point.