No-Code: Pull Phone Numbers Out of tweets.js
tweets.js is the single most important file inside your X archive. Every tweet you have ever posted, whether 100,000 or 200,000 of them, lives in that one JSON. Finding every tweet that contains a phone number does not actually require learning to code. This post explains why, then gives you two ways to do it.
What tweets.js actually is
After you unzip your X archive, the data folder holds a pile of files, and tweets.js is the biggest and most complete. Each tweet is stored as one record with fields for text, timestamp, and location. Privacy traces like phone numbers and emails hide inside the text field.
Method 1: an on-device check tool, easiest
Load the archive into a 100% on-device check tool. It auto-matches common phone formats, mainland China starting 1 with 11 digits, US plus 1, UK, and others, lists every hit as a separate tweet, and tags a risk level. You write zero code.
Method 2: search without coding
- Open tweets.js in any editor that supports find in file.
- Searching 1 prefix is too broad; instead search a number prefix you remember, like 138 or 139, or plus 1 space.
- Check each hit in context to confirm it is a real phone number and not 138 people attended false positives.
Why on-device beats uploading
| Approach | Pros | Cons |
|---|---|---|
| On-device tool | Precise, no upload, auto-graded | Needs the archive |
| Upload to a site | No install | Archive holds all privacy, risky to send out |
| Pure manual search | No tool needed | Slow, leaky, hard to cover all prefixes |
After you extract them
With the list of phone-number tweets in hand, do not rush to delete all. Judge each by whether this still represents who I am, then clear by risk with the bulk delete. Export an archive snapshot before deleting, as always.
About digital-footprint-health.shop
digital-footprint-health.shop runs a 100% on-device footprint check: load your X archive, parse tweets.js locally, auto-detect phone numbers, emails, and addresses, and give a 0-100 health score. Want to try? Try the free check, read what is inside your X archive, or see how to download your X archive.
Frequently Asked Questions
Can I extract phone numbers from tweets.js without coding?
Yes. Load the archive into an on-device check tool and it auto-matches common phone formats and lists each hit, no code required.
Is it safe to upload my archive to a website for parsing?
Not advised. The archive holds all your tweets and DMs, so uploading sends all that privacy out. Prefer an on-device tool where data never leaves your computer.
Will manual prefix searching miss things?
Yes, especially with one prefix. An on-device tool covers multiple country formats and auto-grades, broader and more accurate than manual search.
Check your own X/Twitter footprint
Free on-device scan. Your archive never leaves your computer.
Start Free CheckRelated Reads
Huge Archives (200MB, 30K Files)? No Problem
A veteran X account routinely produces a 200MB archive with tens of thousands of files, and plenty of online tools choke on it. Here is what is actually inside a large Twitter archive, where the weight comes from, whether a browser can handle it, and how to fix the three errors people hit most.
Snapshot First: Back Up Your Archive Before Cleaning
Deletion is one-way, so a snapshot is your only safety net. Here is what counts as a proper account snapshot, why it has to come before deleting, how to build a backup that survives ten years, and how to handle the privacy risk of the snapshot itself.
What's Inside the X Archive? tweets.js Explained
After you download your X archive, tweets.js is the file that matters — structured JSON of every tweet you ever posted. This post breaks down its internal format and how a privacy check reads it.