Twitter (X) ID Finder
Convert any @username to its permanent numeric user ID, or paste an ID to get the handle back. Free, instant, no login.
Free, no login. Powered by the GetXAPI user lookup endpoint.
Why the numeric ID matters
A Twitter / X handle is not a stable identifier. Users rename, accounts get recycled, and a handle you stored last month can point at a different person today. The numeric user ID is assigned once at account creation and never changes, which is why every serious integration keys its data on the ID, not the username.
This tool resolves either direction in one call. To do the same thing inside your own product, the GetXAPI user lookup returns the full profile (ID, follower counts, bio, creation date, verification) at $0.001 per request, with no X developer account. See the pricing for the full rate card, or the Python tutorial for a code walkthrough.
Username to ID, and ID to username
This tool works both directions. Type an @username to get its numeric ID, or paste a numeric ID to get the current handle and profile back. The reverse lookup (ID to username) is the one people reach for most: when you have IDs saved from an old export and the handles may have changed, the ID is the only thing that still resolves reliably, because it never changes even after a rename.
What developers use the ID for
- A stable primary key: store follower, tweet, and profile data against the ID so a rename never orphans your records.
- Faster API calls: looking an account up by ID is quicker than by username, so ID-keyed pipelines run leaner.
- Deduplication: the same account can appear under different handles over time, the ID collapses them into one.
All of this is available programmatically: the followers and user endpoints return the numeric ID on every profile, so you can resolve handles and IDs at scale instead of one at a time.
Resolve IDs programmatically
Same lookup, in your code. $0.001 per call, no developer account, $0.10 in free credits at signup.
Frequently Asked Questions
Every Twitter / X account has two identifiers: the @username (handle) you see, and a permanent numeric user ID assigned when the account was created. The numeric ID never changes, even if the account renames its handle, which is why developers key their data on the ID rather than the username.
Yes. Paste the numeric ID instead of a handle and the tool resolves it back to the current @username and profile. This is useful when you have IDs stored from an old export and the handles may have changed.
The numeric ID is the only stable key for an account. Usernames can be changed, recycled, or squatted, so building on the handle breaks your data when a user renames. Storing the numeric ID keeps your records correct across renames.
Developers use the numeric ID as the primary key for an account: to store follower and tweet data against a stable identifier, to deduplicate accounts across exports, and as the input to API calls (looking up an ID is faster than looking up a username). Because it never changes, it keeps datasets correct even after users rename.
Enter the @username above and this tool returns the numeric ID instantly. Under the hood it calls the GetXAPI user lookup endpoint, the same call you can make programmatically at $0.001 per request.
Yes, it is free and needs no login or developer account. If you need to resolve IDs in bulk or inside your own app, the same lookup is available programmatically through GetXAPI at $0.001 per call.
Paste the numeric ID into the tool above instead of a handle. It resolves the ID back to the current @username and full profile. This is the reverse lookup, and it is the reliable way to recover handles from IDs you stored in an old export, since the ID never changes even when the handle does.
If the account is renamed, look it up by its current handle and you will get the same ID it always had. If the account is fully suspended or deleted, X no longer serves its profile, so neither this tool nor any API can resolve it, the only way to recover it is from data you captured before the account went down.
Next read
Continue exploring related pages:
How to get a Twitter / X API key
Two paths, official console vs 30-second GetXAPI signup with $0.10 free credits.
Twitter followers API
Export any account's followers and following with cursor pagination, $0.05 per 1,000.
Python Twitter API tutorial
Fetch tweets, users, followers, and search in Python with plain requests, full code, no X developer account.
GetXAPI pricing
Brand pricing page with endpoint-level costs and quick totals.