Decode any Twitter snowflake ID to extract the exact timestamp with millisecond precision
💡 Tip: Works with twitter.com or x.com URLs, or just paste the tweet ID number
TWEET POSTED
UNIX TIMESTAMP
TWEET ID
📌 Try These Examples
Popular Tweet Example
ID: 1382350606417817604
Click to decode →
First Snowflake ID
ID: 1
Click to decode →
Round Number Example
ID: 1800000000000000000
Click to decode →
How to Decode Twitter Snowflake IDs
Decoding Twitter snowflake IDs reveals the exact timestamp when a tweet was posted. Every tweet has a unique snowflake ID embedded in its URL that contains the precise timestamp of when it was created. Simply paste the tweet URL or ID into our decoder, and we'll extract the timestamp to show you the exact date and time with millisecond accuracy.
Twitter uses snowflake IDs for all tweets posted after November 4, 2010. These 64-bit integers contain an embedded timestamp in the first 41 bits, representing milliseconds since Twitter's epoch (November 4, 2010, 01:42:54 UTC). Our snowflake decoder extracts this timestamp instantly.
Finding Tweet IDs
Method 1: From Tweet URL
The tweet ID is the long number at the end of any tweet URL:
twitter.com/username/status/1382350606417817604
Method 2: From X.com URL
Works the same with new X.com URLs:
x.com/username/status/1382350606417817604
Common Use Cases
Verify Tweet Timing: Confirm exactly when a tweet was posted for fact-checking or investigations
Social Media Research: Analyze tweet patterns and timing for research projects
Content Scheduling: Study when successful tweets were posted to optimize your posting schedule
Dispute Resolution: Provide evidence of tweet timing in disputes or legal matters
Bot Detection: Identify suspicious posting patterns by analyzing tweet timestamps
Archive Management: Organize and sort saved tweets by their actual post time
Trend Analysis: Track when viral tweets started spreading
Understanding Twitter Snowflake IDs
Twitter snowflake IDs are 64-bit integers with three components:
Timestamp (41 bits): Milliseconds since Twitter epoch (Nov 4, 2010) - this is what we decode
Worker ID (10 bits): Identifies which Twitter server generated the ID
Sequence (12 bits): Counter for tweets created in the same millisecond
This structure allows Twitter to generate over 4 million unique tweet IDs per second across their distributed infrastructure.
Tweet Timestamp Formula
The mathematical formula to extract timestamp from tweet ID:
Where 1288834974657 is Twitter's epoch in Unix milliseconds. The >> operator right-shifts the ID by 22 bits to extract the timestamp portion.
Why Twitter Uses Snowflake IDs
Twitter developed snowflake IDs in 2010 to solve the challenge of generating unique identifiers at massive scale. Benefits include:
Time-Ordered: Tweets are naturally sorted by post time
Globally Unique: No two tweets will ever have the same ID
Distributed Generation: Multiple servers can generate IDs without coordination
Compact: 64-bit IDs are efficient for storage and URLs
Embedded Metadata: Timestamp is built into the ID itself
Historical Context
Before November 4, 2010, Twitter used sequential integer IDs. These older tweets don't have embedded timestamps and can't be decoded with this tool. The switch to snowflake IDs was necessary as Twitter scaled to handle billions of tweets.
Frequently Asked Questions
Can I find timestamps for deleted tweets?
Yes, if you have the tweet ID or URL saved. The timestamp is encoded in the ID itself, so even if the tweet is deleted, you can still decode when it was originally posted.
Do retweets have different timestamps?
Yes! Retweets get their own unique ID with a timestamp of when the retweet happened, not when the original tweet was posted.
Are tweet timestamps accurate?
Yes, timestamps are accurate to the millisecond. They represent the exact moment Twitter's servers created the tweet ID.
Can I decode timestamps from private accounts?
Yes, as long as you have access to see the tweet and can copy its URL or ID. The timestamp is part of the ID structure itself.
What's the oldest tweet I can decode?
You can decode any tweet posted after November 4, 2010, when Twitter launched snowflake IDs. Tweets before this date use sequential IDs without embedded timestamps.
🔥 Try These Real Examples
1800000000000000000→ November 9, 2024
1700000000000000000→ September 8, 2023
1529877576591609861→ May 26, 2022
1382350606417817604→ April 14, 2021
💡 Click any example to try it instantly!
🔍 How Tweet Timestamps Work
Every tweet ID is a snowflake ID that contains the exact timestamp when it was posted.
Twitter started using snowflake IDs on November 4, 2010, which means you can decode any tweet from 2010 onwards.
The timestamp is embedded in the first 41 bits of the ID. Our tool extracts this timestamp and converts it to a human-readable date and time.