Wiping 10 Years of Tweets: A Power User’s Test

I took a 2013 account with 32,148 tweets and ran the whole thing end to end, just to see what it really takes to delete 10 years of tweets. The name makes it sound like one button. In practice, getting the data ready alone took three days. So this post is mostly numbers: how long each stage ran, where the money went, the four things that tripped me up, and what actually changed on the account afterward.

Headline result first. Total elapsed time was 3 days and 4 hours, and three of those days were just X building my archive. My own hands-on time came to about 1 hour 10 minutes of real attention. The bill came in under the price of a decent dinner. If you have an old account sitting on a decade of posts, this should save you half the trial and error.

Why there is no one-click wipe for ten years

X does not offer a delete-everything feature and shows no sign of building one. On the web you can only remove posts one at a time, and the timeline scrolls back roughly 3,200 tweets before it stops handing you more. With 32,000 tweets, manual deletion would mean paging through ten times more history than the interface will ever show me.

That leaves the data archive as the only real entrance. X packages your full history into a ZIP, and inside it tweets.js stores the ID, timestamp, and text of every post. Once you have IDs, deletion requests go out by ID, which has nothing to do with what page a tweet sits on. That is precisely how the 3,200-tweet ceiling gets bypassed: it caps reading, not deleting.

What the test account looked like

The profile probably resembles a lot of accounts. Registered in 2013 as a college freshman, heavy posting from 2014 to 2017 at a dozen-plus tweets a day including a pile of location check-ins, then mostly quiet retweeting after 2018.

• 32,148 tweets total: roughly 19,000 original, 13,000 retweets
• 1,204 geotagged tweets, clustered around travel and campus life in 2015 and 2016
• 203MB archive ZIP, over 27,000 files once unzipped, most of them image thumbnails
• Footprint health score of 41, with three phone-number hits and one home address flagged red

That 41 surprised me. I was confident I had never posted a phone number, and technically I had not: in 2015 I split my number across two tweets in three chunks so someone could add me on WeChat. Split text, same red label.

The full run, stage by stage

1. Request the archive. Settings, then Your account, then Download an archive of your data. Password plus SMS code, then you wait.
2. Wait for generation. X says up to 24 hours. Mine took 68. Old accounts hold more data and run slow; nothing for you to do here.
3. Download and unzip. Four minutes to pull 203MB, ninety seconds to extract. Confirm data/tweets.js opens before going further.
4. Run the on-device check. Drop the ZIP into the checker: 2 minutes 12 seconds to a full report with score, risk labels, and a per-tweet cleanup queue.
5. Test-delete a small batch. I selected only August 2016, 214 tweets, then came back the next day to verify the filter had done what I expected.
6. Run the bulk deletion. Once the logic checked out I released the full queue. It ran 3 hours 10 minutes in the background, with one pause in the middle.
7. Sweep for leftovers. Afterward I searched my own name, phone-number variants, and my old employer, and dug out about thirty stragglers.

Step five is the one I would defend hardest. Test deletion feels like a wasted step until you realize it converts a wrong filter from irreversible into repeatable. Full mechanics live in the complete bulk deletion walkthrough.

Time and cost, measured

Stage	Measured time	Needs my attention	Notes
Request archive	~3 minutes	Yes	Password and SMS verification
X builds archive	68 hours	No	Stated 24h; old accounts run longer
Download and unzip	5 min 30 sec	No	203MB on a 100Mbps line
On-device parse and check	2 min 12 sec	No	32,148 tweets, nothing uploaded
Reviewing the cleanup queue	~40 minutes	Yes	The most mentally taxing part
Test delete of 214 tweets	3 min + overnight check	Yes	Validates the filter
Bulk delete of 28,700 tweets	3 hr 10 min	No	Background, pause and resume
Keyword sweep	~25 minutes	Yes	Recovered 30-odd leftovers

Add up the rows that need me and it is about seventy minutes. Everything else is waiting. So the real cost of wiping a decade is patience, not effort. Deletion itself is priced per tweet with volume tiers, laid out in the per-tweet pricing breakdown.

Four things that tripped me up

One: I assumed the archive would be fast. I requested it on a Friday night and got it Monday morning. If you are cleaning up before a job search, budget for the wait instead of expecting same-day results.

Two: image content is invisible to the scan. The checker reads text. Several of my tweets carried sensitive details inside screenshots: a student ID, a shipping label. For those you have to page through images by date yourself; no tool catches them for you.

Three: I spent too long deciding about retweets. Retweets were 13,000 posts, about forty percent of the account, and I burned half an hour debating them. The call ended up being simple. Retweets carry almost none of my private information, but they dilute the account, so they went out by year along with everything else.

Four: I nearly forgot to back up. I almost started deleting straight away. Luckily the archive ZIP is already a snapshot, so I copied it to an external drive. Deletion is one-way, and afterward that ZIP is the only place the original text still exists. Details in taking an account snapshot before cleaning.

What changed after the wipe

The obvious change: my health score went from 41 to 92, with the missing 8 points sitting on a handful of old tweets I deliberately kept. I lost 11 followers and nobody asked why. Searching my own name, the old tweet results dropped off the first two pages of Google over about two weeks, though caches and third-party mirrors still hold fragments. Deletion pulls back your original; it does not pull back someone else's screenshot.

One detail I did not anticipate: anyone who quote-tweeted me now has an empty quote box in their thread. That is the only clearly visible sign that I cleaned house. Why scrapers and snapshot sites can still surface old content is its own topic, which I wrote up in why deleted tweets are still visible.

What I would do differently

First, request the archive early rather than on the day you decide to clean. It costs nothing to have a ZIP sitting on your drive, and whether you use it is a separate question. Second, delete by risk before deleting by date. Clearing the few hundred tweets with phone numbers, addresses, and geotags moves your safety needle far more than clearing 2014 in bulk. Third, stop treating cleanup as a one-time project. I now scan a fresh archive every six months, which takes about twenty minutes and beats saving up ten years of mess for one bad weekend.

FAQ

How long does it take to delete 10 years of tweets? My run took 3 days 4 hours, but three days were waiting on X to build the archive. Hands-on time was under 4 hours: 2 minutes to parse 32,000 tweets and 3 hours 10 minutes of background deletion.

How much does deleting 30,000 tweets cost? Per-tweet pricing with volume tiers. I deleted 28,700 tweets for less than a nice dinner, and I could pause or delete only part of the queue.

Can I stop the deletion halfway? Yes. I paused at 11,000 for twenty minutes and resumed from the checkpoint with no duplicates.

Does the 3,200-tweet limit block a ten-year wipe? It blocks scroll-and-delete, not the archive route. Requests go out by tweet ID regardless of timeline position.

Will followers notice? Mostly no. I lost 11 followers and got zero questions. The one visible trace is empty quote boxes where people had quoted my old posts.

Curious what a decade of your own posting is hiding? The check at digital-footprint-health.shop is free and read-only, so you can see the list before deciding to delete anything.