Finding Twitter User IDs

finding_twitter_user_id.md

Finding Twitter User IDs

User accounts on Twitter are commonly identified by screen name, which may be changed by operators when they take over an account, or have been sitting on an old account for a long time and want to transition it into malicious use.

User IDs, however, are permanent. There are several services out there that will try to find them for you but it seems like a bad idea to me, since you're alerting them to the fact that there's something interesting about this account. There's also plenty of bad advice that uses many long-since-abandoned Twitter API endpoints.

As of this writing (2018-02-18) you can view source and search for /profile_banners/, which will show something like this:

.enhanced-mini-profile .mini-profile .profile-summary {
  background-image: url(https://pbs.twimg.com/profile_banners/2622731/1401943819/mobile);
}

The number after profile_banners/ is the account's Twitter user ID, which won't change if the account's screen name is changed. Here, 2622731 is my personal Twitter ID. (Expect to see much later numbers for more recent accounts; mine is quite old.)

Deleted Accounts?

If someone has just deleted their account it's often possible to find it in Google's most recent cache. Try searching for this:

twitter thatRecentlyDeletedUserName

Click the little down-arrow in the green URL, just below the blue headline, and then choose Cached. If it works, you'll see a page from http://webcache.googleusercontent.com/ with a View Source link somewhere near the top. Search as shown above.

ID to User Name?

To translate an ID to the current user name, visit the Intents url. Here's mine:

https://twitter.com/intent/user?user_id=2622731

This will show my current Twitter user name, which is @kentbrew. You should follow me, of course. :)

Haven't looked at this in a while. It looks like one of document.scripts has a type of application/ld+json. If you try this on a profile page:

Their JSON structures change faster than their URL structures.

At the moment this works:

id = JSON.parse(
document.evaluate(
    '//script[@type="application/ld+json"]', 
    document.lastChild, 
    null,
    XPathResult.ANY_TYPE, null).iterateNext().textContent
).mainEntity.identifier;

This has been working for a much longer time:

id = document.querySelector('img[src*="https://pbs.twimg.com/profile_banners/"]').src.split('https://pbs.twimg.com/profile_banners/')[1].split('/')[0]

Tested on https://twitter.com/i/user/12 and https://twitter.com/jack (and their client-side redirects), the intermediate src returns https://pbs.twimg.com/profile_banners/12/1742427520/600x200 where 12 is the Twitter user ID.

You can also run this from a profile header URL like https://x.com/jack/header_photo where the intermediate src is https://pbs.twimg.com/profile_banners/12/1742427520/1500x500

And @Sardonyx001 : twid does not return 12 here but 39508140 which is my own Twitter user ID instead of the currently displayed user profile.

@jpluimers Yes it's saved in your browser cookies so it returns your own ID.
Thank you for your solution it works with any account!

const script = document.querySelector('script[type="application/ld+json"][data-testid="UserProfileSchema-test"]');
if (script) {
const data = JSON.parse(script.textContent);
const userId = data.mainEntity?.identifier;
console.log("User ID:", userId);
}