Snowflake ID to Date Converter - Decode Twitter & Discord IDs (Free)

Last updated March 22, 2026

Platform Comparison

Same number decoded with different platform epochs:

Number: 1529877576591609861

Twitter (epoch 2010): 2022-05-26 ✅ (correct for Twitter)
Discord (epoch 2015): 2063-07-14 ❌ (wrong platform)
Instagram (epoch 2011): 2022-03-xx (different result)

Always select the correct platform when decoding!

Common Use Cases

• Determining when a tweet was posted from its ID
• Checking Discord account age for moderation purposes
• Analyzing temporal distribution of social media data
• Verifying that API responses contain IDs from expected time periods
• Reconstructing timelines from Snowflake ID sequences
• Database archiving based on ID-derived creation dates

All conversion happens entirely in your browser. Your Snowflake IDs are never transmitted to any server.

Snowflake ID Structure

Every snowflake ID contains three components encoded in 64 bits:

• Timestamp (41 bits): Milliseconds since platform epoch - allows IDs to work for 69 years
• Worker ID (10 bits): Identifies which machine generated the ID (0-1023)
• Sequence (12 bits): Counter for IDs generated in same millisecond (0-4095)

Common Use Cases

• Finding Tweet Timestamps: Determine exactly when a tweet was posted from its ID
• Discord Account Age: See when Discord accounts were created from user IDs
• Message Timestamps: Find when Discord messages were sent
• Instagram Post Dates: Decode Instagram media IDs to post creation times
• Forensic Analysis: Investigate timeline of events using ID timestamps
• Data Migration: Understand data creation patterns when migrating systems

Conversion Formula

The mathematical formula to convert a snowflake ID to timestamp:

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

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.

Input: 1529877576591609861

Platform: Twitter
Epoch:    2010-11-04 01:42:54 UTC

Output:
  Date:     May 26, 2022
  Time:     6:00:00 PM UTC
  Full:     2022-05-26T18:00:00.123Z
  Relative: about 2 years ago

Input: 1085000000000000000

Platform: Discord
Epoch:    2015-01-01 00:00:00 UTC

Output:
  Date:     March 14, 2023
  Time:     (approximate)
  Full:     2023-03-14T00:00:00.000Z
  Account age: ~1 year old (as of 2024)

Use case: Discord moderators check account age
to identify potentially suspicious new accounts.

Input: 1700000000000000000 (Twitter)

Output formats:
  ISO 8601:          2023-09-14T09:26:08.000Z
  RFC 2822:          Thu, 14 Sep 2023 09:26:08 +0000
  Unix timestamp:    1694683568
  Unix ms:           1694683568000
  Human readable:    September 14, 2023 at 9:26 AM UTC
  Relative:          about 6 months ago
  Date only:         2023-09-14
  Time only:         09:26:08 UTC