Paste any tweet ID or Twitter user ID to decode its creation date
💡 Tip: Find tweet IDs in URLs: twitter.com/user/status/ID or x.com/user/status/ID
TWITTER ID
📅 Creation Date
⏱️ Unix Timestamp
🕐 Time Ago
How to Convert Twitter ID to Date
Converting a Twitter ID to a date is simple with our tool. Twitter uses snowflake IDs for tweets and user accounts, and each ID contains an embedded timestamp. Simply paste the ID and click convert to see the exact creation date and time.
Twitter snowflake IDs are 64-bit integers where the first 41 bits encode the timestamp in milliseconds since Twitter's epoch (November 4, 2010, 01:42:54 UTC). By right-shifting the ID by 22 bits and adding the epoch, we recover the original Unix timestamp.
Finding Twitter IDs
Tweet ID from URL: Copy from URL - twitter.com/user/status/1382350606417817604
X.com URLs: Works the same - x.com/user/status/1382350606417817604
User IDs: Use Twitter API, browser developer tools, or third-party tools to get user IDs
Common Use Cases
📊 Research & Analysis
Analyze tweet timing patterns, study viral content spread, and research social media trends.
✅ Fact Checking
Verify exactly when tweets were posted for journalism, investigations, and fact-checking.
📈 Content Strategy
Study when successful tweets were posted to optimize your posting schedule.
⚖️ Legal Evidence
Provide precise timestamps for legal matters, disputes, or documentation.
🤖 Bot Detection
Identify suspicious posting patterns by analyzing tweet timestamps.
📚 Archive Management
Organize and sort saved tweets by their actual creation time.
Twitter Snowflake Date Formula
The mathematical formula to extract date from Twitter ID:
timestamp_ms = (twitter_id >> 22) + 1288834974657
Where 1288834974657 is Twitter's epoch in Unix milliseconds (November 4, 2010). The >> operator right-shifts the ID by 22 bits to extract the timestamp portion.
Understanding Twitter Snowflake IDs
Twitter snowflake IDs are 64-bit integers with three components:
Timestamp (41 bits): Milliseconds since Twitter epoch - 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
Why Twitter Uses Snowflake IDs
Twitter developed snowflake IDs in 2010 to handle 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 decode deleted tweet timestamps?
Yes, if you have the tweet ID 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 IDs?
Yes! Retweets get their own unique ID with a timestamp of when the retweet happened, not when the original tweet was posted.
Are Twitter timestamps accurate?
Yes, timestamps are accurate to the millisecond. They represent the exact moment Twitter's servers created the tweet ID.
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.
Do X.com and twitter.com IDs work the same?
Yes! X (formerly Twitter) uses the same snowflake ID format. IDs from both domains decode identically.
🔥 Popular Twitter IDs to Try
1800000000000000000→ November 9, 2024, 12:26 AM UTC
1700000000000000000→ September 8, 2023, 12:53 AM UTC
1529877576591609861→ May 26, 2022, 1:30 PM UTC
1382350606417817604→ April 14, 2021, 2:30 PM UTC
3950142972→ December 25, 2015 (User ID)
🧠 Understanding Twitter Snowflake IDs
Twitter uses snowflake IDs for tweets, users, and media. Each ID is a 64-bit integer that contains:
41 bits - Timestamp (milliseconds since Twitter epoch: Nov 4, 2010)
10 bits - Machine ID (which Twitter server created it)
12 bits - Sequence number (for IDs created in the same millisecond)
💡 Common Use Cases:
Find when a viral tweet was originally posted
Verify account creation dates for authenticity checks
Track content timeline for research or investigations
Analyze tweet patterns and posting schedules
Verify if an account is genuinely old or recently created