📅 Snowflake to Date Converter

Convert any snowflake ID to date and timestamp instantly

🔥 Popular Snowflake IDs to Try

🐦 TWITTER ID
1800000000000000000
📅 July 13, 2024
💬 DISCORD ID
1234567890123456789
📅 September 7, 2024
📸 INSTAGRAM ID
3950142972
📅 February 15, 2025

💡 Click any ID to decode it instantly

🔍 Convert Snowflake ID to Date

Select platform and enter snowflake ID to see creation date

Creation Date
Unix Timestamp
Time Ago
Worker ID
Sequence Number

How to Convert Snowflake ID to Date

Converting a snowflake ID to a date is simple: select the platform (Twitter, Discord, or Instagram), paste the snowflake ID, and click Convert. Our tool instantly extracts the embedded timestamp and displays the exact creation date, time ago, worker ID, and sequence number.

Snowflake IDs are 64-bit integers where the first 41 bits encode the timestamp in milliseconds since the platform's epoch. By right-shifting the ID by 22 bits and adding the epoch, we recover the original Unix timestamp.

Platform-Specific Epochs

🐦 Twitter/X

Epoch: 1288834974657 ms

Date: November 4, 2010, 01:42:54 UTC

When Twitter launched their snowflake ID system

💬 Discord

Epoch: 1420070400000 ms

Date: January 1, 2015, 00:00:00 UTC

Discord's service launch date

📸 Instagram

Epoch: 0 ms

Date: January 1, 1970, 00:00:00 UTC

Uses Unix epoch with custom sharding

Snowflake ID Structure

Every snowflake ID contains three components encoded in 64 bits:

Common Use Cases

Conversion Formula

The mathematical formula to convert a snowflake ID to timestamp:

JavaScript
const snowflakeId = 1382350606417817604n;
const epoch = 1288834974657n; // Twitter epoch
const timestamp = (snowflakeId >> 22n) + epoch;
console.log(Number(timestamp)); // 1618592259657

// Convert to Date
const date = new Date(Number(timestamp));
console.log(date.toISOString()); // 2021-04-16T14:30:59.657Z

📝 Real Example

Input: 1382350606417817604 (Twitter ID)

Output: 1618592259657 ms → April 16, 2021, 2:30:59 PM UTC

Meaning: This tweet was posted on April 16, 2021

Where >> is the right bit-shift operator. This extracts the 41-bit timestamp from the snowflake ID and adds the platform's epoch to get the Unix timestamp in milliseconds.

Why Different Epochs?

Each platform chose their epoch based on when they implemented snowflake IDs. Using a recent epoch (instead of Unix epoch 1970) extends the 41-bit timestamp lifespan. With 41 bits, you get 69 years from the epoch date. Twitter's IDs work until ~2079, Discord's until ~2084.

Frequently Asked Questions

Can I convert snowflake IDs from any platform?

Yes! Our converter supports Twitter, Discord, Instagram, and custom epochs. Just select the correct platform to ensure accurate date conversion.

What if I don't know which platform the ID is from?

Try each platform option. The correct one will show a reasonable date. Twitter IDs typically start with 1-2, Discord with 1-9, and Instagram varies widely.

Can I batch convert multiple IDs?

Use our main Snowflake Decoder which supports batch processing up to 100 IDs at once.