🐦 Twitter Snowflake to Timestamp Converter

Convert Twitter/X snowflake IDs to Unix timestamps instantly

Home › Twitter Snowflake to Timestamp

🔍 Convert Twitter Snowflake ID to Unix Timestamp

Enter Twitter/X snowflake ID to extract Unix timestamp

Unix Timestamp (milliseconds)
Unix Timestamp (seconds)
Tweet Posted On
ISO 8601 Format

How to Convert Twitter Snowflake ID to Unix Timestamp

Converting a Twitter snowflake ID to a Unix timestamp is simple: paste the Twitter ID (from a tweet URL or API response) and click Convert. Our tool instantly extracts the embedded timestamp and displays it in milliseconds, seconds, and human-readable format.

Twitter snowflake IDs encode timestamps in the first 41 bits using the formula: (snowflake_id >> 22) + 1288834974657. This extracts the millisecond offset and adds Twitter's epoch (November 4, 2010) to get the exact Unix timestamp.

Why Convert Twitter Snowflake to Timestamp?

Understanding Twitter's Snowflake Format

Twitter uses a 64-bit snowflake ID structure:

The Twitter epoch is 1288834974657 milliseconds (November 4, 2010, 01:42:54 UTC). All tweet IDs created after this date encode their timestamp relative to this epoch.

Example Conversion

Tweet ID: 1382350606417817604

Calculation: (1382350606417817604 >> 22) + 1288834974657

Result: 1618592259657 ms (April 16, 2021)

Code Examples

JavaScript

const tweetId = 1382350606417817604n; const twitterEpoch = 1288834974657n; const timestamp = (tweetId >> 22n) + twitterEpoch; console.log(Number(timestamp)); // 1618592259657

Python

tweet_id = 1382350606417817604 twitter_epoch = 1288834974657 timestamp = (tweet_id >> 22) + twitter_epoch print(timestamp) # 1618592259657

Common Use Cases

Common Errors & Solutions

❌ Error: "Invalid snowflake ID"

Cause: ID contains non-numeric characters or is too short

Solution: Remove any spaces, letters, or special characters. Valid IDs are 15-19 digits.

Example: abc123 → Invalid | 1382350606417817604 → Valid

❌ Error: "Date seems incorrect"

Cause: Wrong platform epoch being used

Solution: Verify you're using the correct converter for your platform (Twitter).

Tip: Twitter uses epoch: 1288834974657 ms

❌ Error: "Date is in the future"

Cause: ID is too large, corrupted, or not a snowflake ID

Solution: Verify the ID is correct and from Twitter.

Performance & Best Practices

💡 Batch Processing

Processing multiple IDs? Use array mapping for efficiency:

JavaScript 
const ids = ['1382350606417817604', '1383000000000000000'];
const timestamps = ids.map(id => 
    Number((BigInt(id) >> 22n) + 1288834974657n)
);

💡 Input Validation

Always validate before converting to prevent errors:

JavaScript 
function validateSnowflake(id) {
    if (!/^\d{15,19}$/.test(id)) {
        throw new Error('Invalid snowflake ID');
    }
    return true;
}

Frequently Asked Questions

Can I get the exact millisecond a tweet was posted?

Yes! Twitter snowflake IDs encode millisecond-precision timestamps. Our converter extracts the exact millisecond the tweet was created on Twitter's servers.

Do X (formerly Twitter) IDs use the same format?

Yes, X continues to use the same snowflake ID format with the same epoch (November 4, 2010). All tweet IDs from both Twitter and X can be converted using this tool.

Why is Twitter's epoch November 4, 2010?

Twitter launched snowflake IDs on November 4, 2010, replacing sequential IDs. This date became the epoch for all future tweet IDs.

Can I convert timestamps back to tweet IDs?

Not exactly. While you can create a snowflake ID from a timestamp, you can't recreate the original tweet ID because it also contains worker ID and sequence number.