Twitter/X Timestamp Converter

About Twitter/X Timestamp Converter

The Twitter/X Timestamp Converter is a free online tool that extracts the exact date and time a tweet was posted by decoding the Snowflake ID embedded in every tweet URL. It also works in reverse, letting you generate Snowflake IDs from dates for advanced Twitter/X search filtering. Whether you are a journalist verifying tweet timelines, a researcher archiving social media data, or a developer working with the Twitter API, this tool provides millisecond-accurate timestamps instantly.

How It Works

Every tweet on Twitter/X is assigned a unique Snowflake ID — a 64-bit integer that encodes the exact creation time along with machine information. The tool decodes this ID using a simple bit-shift operation:

1. Extract the timestamp: The tool shifts the Snowflake ID right by 22 bits to isolate the 41-bit timestamp portion.
2. Add the epoch offset: It adds the Twitter Snowflake epoch (1,288,834,974,657 ms, corresponding to November 4, 2010, 01:42:54.657 UTC) to convert from Twitter time to Unix time.
3. Convert to human-readable format: The resulting Unix timestamp is formatted into multiple date/time formats and displayed across world timezones.

For the reverse conversion (Date → Snowflake ID), the process is inverted: subtract the epoch, then left-shift by 22 bits to produce a lower-bound Snowflake ID for that moment in time.

How to Use This Tool

1. Choose your conversion mode: Select "Tweet → Time" to decode a tweet's timestamp, or "Time → Tweet ID" to generate a Snowflake ID from a date.
2. Enter your input: Paste a tweet URL from twitter.com or x.com (e.g., https://x.com/user/status/1835436894737400213), enter a numeric Tweet ID directly, or pick a date and time using the date picker.
3. Click Convert: The tool processes your input and displays the results immediately.
4. Review the results: For Tweet → Time, you will see the exact date, time (with millisecond precision), relative time, Snowflake ID anatomy, and world clock display. For Time → Tweet ID, you will see the generated Snowflake ID with ready-to-use search parameters.
5. Copy any result: Click the copy button (⧉) next to any value to copy it to your clipboard.

Understanding Twitter/X Snowflake IDs

Twitter introduced Snowflake IDs in November 2010 to replace auto-incrementing integer IDs. The system was designed to generate unique, time-sortable IDs across distributed data centers without coordination. Each 64-bit Snowflake ID contains four fields:

This design means that each machine can generate up to 4,096 unique IDs per millisecond, and IDs are naturally sorted by time — a larger ID always means a later tweet.

Supported URL Formats

The tool accepts tweet URLs in a variety of formats:

• https://x.com/username/status/1234567890
• https://twitter.com/username/status/1234567890
• https://mobile.twitter.com/username/status/1234567890
• https://vxtwitter.com/username/status/1234567890
• https://fxtwitter.com/username/status/1234567890
• Direct numeric Snowflake IDs (e.g., 1835436894737400213)

Use Cases

• Journalism & fact-checking: Verify when a tweet was actually posted, independent of the displayed timestamp.
• Legal & compliance: Establish precise timelines for tweets relevant to legal proceedings or investigations.
• Social media research: Analyze posting patterns, correlate tweets with real-world events, or audit content timelines.
• Developer tools: Generate Snowflake IDs for use with the Twitter API's since_id and max_id pagination parameters.
• Content auditing: Determine the original posting dates of archived or screenshot-only tweets.
• OSINT (Open Source Intelligence): Cross-reference tweet timestamps with other data sources for intelligence analysis.

FAQ

What is a Twitter/X Snowflake ID?

A Snowflake ID is a unique 64-bit identifier that Twitter (now X) assigns to every tweet, user, and direct message. Introduced in November 2010, each Snowflake ID encodes the exact timestamp of creation along with machine and sequence information, making it possible to extract the precise posting time from any tweet ID.

How does the Snowflake ID encode the timestamp?

The 64-bit Snowflake ID is divided into four parts: 1 unused sign bit, 41 bits for the timestamp (milliseconds since Twitter epoch), 5 bits for the datacenter ID, 5 bits for the worker ID, and 12 bits for a sequence number. The timestamp stores milliseconds elapsed since November 4, 2010, at 01:42:54.657 UTC.

What is the Twitter Snowflake epoch?

The Twitter Snowflake epoch is November 4, 2010, at 01:42:54.657 UTC (Unix timestamp 1288834974657 milliseconds). This is the reference point from which all Snowflake timestamps are calculated. Only tweets posted after this date have Snowflake IDs that encode timestamps.

Can I convert tweets posted before November 2010?

No. Tweets posted before November 4, 2010 used auto-incrementing IDs that do not encode timestamps. The Snowflake ID system was introduced to solve scalability challenges. Only tweets with Snowflake IDs (post-November 2010) can have their timestamps extracted from the ID.

How accurate is the timestamp extraction?

The timestamp is accurate to the millisecond. The Snowflake ID stores the timestamp with millisecond precision, so the extracted date and time are exact to within one millisecond of when Twitter servers generated the ID.

How can I use Snowflake IDs for Twitter/X advanced search?

Use the Time to Tweet ID mode to generate a Snowflake ID for any date, then use since_id and max_id parameters in Twitter API calls or advanced search. For example, to find tweets after January 1, 2024, generate the Snowflake ID for that date and use since_id with that value.