Find Twitter(X) ID
Get numeric ID for any Twitter/X profile instantly
Your numeric Twitter ID will appear here after searching.
What an X (Twitter) user ID is
Every X account has an @handle and a numeric user ID. The handle is rented — you can change it whenever you like, and once released it can be claimed by someone else. The ID is permanent and unique to the account for its entire life.
This is why the X API v2 works almost entirely in IDs. If you follow an account by handle and the owner rebrands, you silently lose them; follow by ID and the link holds.
What you can paste in the box
The box accepts:
-
A handle with or without the @ —
xor@x -
A profile URL on either domain —
x.com/usernameortwitter.com/username -
URLs carrying tracking parameters — anything after
?is discarded
A link to a single post is not a profile link. Open the author profile and copy that URL instead.
Reading the ID: what the number tells you
X user IDs are allocated in ascending order, so the length of the number is a rough age indicator. Accounts from 2006–2008 have IDs under 10 million; accounts created in the last few years run to 18 or 19 digits.
That is a practical signal. An account presenting itself as long-established but carrying a very recent ID is worth a second look before you trust it.
Why a lookup fails, and what to do
A lookup can come back empty for these reasons:
- The handle is misspelled. X handles are limited to letters, numbers and underscores — no dots and no dashes.
- The account is suspended or deleted. Suspended accounts stop returning public data entirely.
- The account is protected. The ID may still resolve, but posts and followers are not accessible.
- X aggressively rate-limits unauthenticated reads. This is the most common temporary failure — wait a minute and retry.
Where the ID is used
X API v2 identifies accounts by numeric ID across nearly every endpoint — /2/users/{id}, timelines, followers, list membership and mute or block management. Passing a handle where an ID is expected is one of the most common integration errors.
Embedded timelines, third-party analytics dashboards and archiving tools ask for the same value. Because handles can be changed and then claimed by somebody else, the ID is also the only safe thing to store if you are tracking accounts over time.
A practical habit: store the ID as your key and keep the handle as a display field you refresh. Then a rebrand updates a label instead of breaking a record.
Frequently asked questions
Is this free?
Yes, free with no account and no quota. The captcha only exists to prevent bulk automated use.
Does the account holder get notified?
No. This reads public profile metadata and generates no notification or profile view.
Does it still work now that Twitter is X?
Yes. Both twitter.com and x.com URLs are accepted, and the underlying user IDs were unchanged by the rename.
Can I convert an ID back into a handle?
Not here — this tool only resolves handle to ID.
What do I need the ID for?
X API v2 endpoints, embedded timelines, list management and most third-party analytics tools identify accounts by numeric ID rather than handle.
Does the ID change if the account goes private or gets renamed?
No. Protecting an account, renaming it, or changing the display name leaves the numeric ID untouched. The only way an ID disappears is permanent deletion of the account itself.
Can two accounts ever share an ID?
No. IDs are unique and never recycled, even after an account is deleted. Handles are the opposite — a released handle can be registered by someone else, which is precisely why handles make poor identifiers.