A post ID identifies a specific post; an account ID identifies an account. A username can change. These tasks need different lookup methods, and an ID does not unlock deleted or protected content.
Find a post ID in its URL
In a URL such as https://x.com/example/status/1234567890123456789, the digits after/status/ are the post ID. This is an illustrative URL, not a verified existing post. Copy the whole numeric string; do not include a query string or trailing path.
Record the original URL with the ID and capture date. A username in the path is not a substitute for the numeric identifier.
Look up an account ID separately
Check an authorized export or documented API response for the account ID. A current username-to-ID lookup requires an available data source and applicable access. A numeric account ID cannot generally be recovered by decoding the username text.
Avoid an unverified converter that asks for your password or promises private account data. This article explains IDs; it does not contain a live username lookup tool.
Store IDs as text
Long IDs exceed the integer precision preserved by some spreadsheet and JavaScript number handling. Keep the original string. In Excel, import the column as Text before loading the values. Changing a rounded number’s display format afterwards does not restore lost digits.
When joining datasets, compare the exact strings and keep account IDs separate from post IDs. See the Excel export guide.
Understand Snowflake limits
Modern X IDs use the Snowflake scheme. Its encoded timestamp can help interpret creation time when the correct epoch and bit layout apply. Do not apply that decoder to every historical ID or treat the result as proof of content or authorship.
The ID remains a reference even when the source is unavailable, but it is not a recovery mechanism. Captured content must have been preserved separately and can still have gaps.
Sources and checks
Reviewed October 16, 2026. X IDs.