Useful results, ready for the next step
Get the time format you need now, then carry the result into research, monitoring or a TweetAPI workflow when you need the post itself.
Confirm when a post appeared
See UTC, browser-local, ISO 8601, Unix and relative time in one result.
Prepare precise searches
Turn a date into boundary IDs and ready-to-copy TweetAPI search filters.
Normalize a list of IDs
Convert up to 100 Tweet IDs or post URLs and export a clean local CSV.
Private before you ever create an account
The converter runs in your browser. Tweet IDs, post URLs, dates and calculated timestamps are not uploaded, stored or included in analytics.
- No signup or API key required
- No server request to the supplied post URL
- No input stored in cookies, local storage or query strings
Need more than the timestamp?
Use TweetAPI to retrieve the tweet text, author, media and engagement data, enrich a batch of IDs, or build ongoing monitoring.
How the Twitter Snowflake timestamp conversion works
A modern Tweet ID stores its creation offset in the upper bits. The converter uses BigInt so the ID remains exact throughout the calculation:
timestampMs = (BigInt(tweetId) >> 22n) + 1288834974657nShifting right removes the lower 22 worker, datacenter and sequence bits, exposing the millisecond offset. Adding Twitter's epoch converts that offset into a Unix timestamp in milliseconds.
Tweet IDs routinely exceed JavaScript's safe integer precision. Keep the ID as a string at input boundaries and use BigInt for the calculation; converting the validated millisecond timestamp for Date is safe.
Verified example: 1396969503708389379 decodes to 2021-05-24T23:20:58.779Z.
Use it in three steps
- 01Paste a Tweet URL or raw Tweet ID into the converter.
- 02Choose Tweet to date, Date to IDs or Batch convert for your workflow.
- 03Copy the timestamp or boundary values, or export batch results as a local CSV.
The decoded value is the time the ID was assigned; it does not retrieve or independently verify the post. Legacy pre-Snowflake IDs do not encode an exact timestamp, so the tool identifies them without estimating a date.
Sources: X ID documentation and Twitter's archived Snowflake implementation.
Frequently asked questions
Does the converter fetch the Tweet?
No. The Tweet ID or post URL is processed locally in your browser. The supplied URL is never requested.
What can I do with the generated search filters?
Copy them into TweetAPI's search query to narrow results by time or ID. The tool labels the boundary behavior directly in the result.
Are reverse-converted IDs real tweets?
No. They are the inclusive minimum and maximum possible Snowflake values for that millisecond. They define boundaries; they do not identify an actual post.
What is included in the batch CSV?
Each row includes the normalized Tweet ID, UTC and ISO 8601 values, Unix seconds and milliseconds, plus an explicit converted, legacy or invalid status.