Running the Deletion Script

Understanding the Workflow

XeetDelete and x.com are two separate browser tabs with two separate roles. Think of it like writing a shopping list at home and then taking it to the shop. You don't try to buy groceries in your kitchen.

Step-by-Step: The Two-Tab Workflow

1. Tab 1 — XeetDelete: Upload your archive, set your filters, and click the Copy Script button. If you're deleting more than 100 tweets, you'll first need to type the exact tweet count to unlock the button — this protects against accidental mass deletion. The deletion script is now on your clipboard.
2. Tab 2 — x.com: Open a new tab and go to x.com. Make sure you're logged in to the account you want to delete tweets from.
3. Tab 2 — Open Developer Console: Press F12 (or Cmd+Option+J on Mac / Ctrl+Shift+J on Windows/Linux) to open Developer Tools.
4. Tab 2 — Go to Console tab: Click the Console tab in the Developer Tools panel.
5. Tab 2 — Paste & Run: Click inside the console, paste the script (Ctrl+V / Cmd+V), and press Enter.
6. The script will start deleting tweets. Progress is logged in the console.

Why It Must Run on x.com

The script needs your active login session on x.com to send deletion requests. It uses the authentication cookies that your browser has stored for x.com. If you paste it into the XeetDelete console (or any other site), it won't have access to those cookies and nothing will happen.