Snowflake ID Decoder

Convert Twitter, Discord & Instagram Snowflake IDs to Date & Timestamp

Convert Twitter/X Snowflake IDs to dates and timestamps instantly. Every tweet ID contains its creation time. Also decode Discord IDs and Instagram IDs to reveal when they were created. Snowflake IDs contain embedded timestamps. This tool extracts them instantly. Learn how Snowflake IDs work →

Generate Sample Snowflake ID

Generate a Snowflake ID for any timestamp to see how they're constructed.

Try These Examples

Snowflake ID Structure

1 Sign Always 0
41 Timestamp Milliseconds since epoch
5 Worker Machine ID (0-31)
5 Process Process ID (0-31)
12 Sequence Counter (0-4095)

Platform Epochs

Platform Epoch (Unix ms) Date
Discord 1420070400000 Jan 1, 2015 00:00:00 UTC
Twitter/X 1288834974657 Nov 4, 2010 01:42:54 UTC
Instagram 0 Unix epoch (custom sharding)

Understanding Snowflake IDs

What is a Snowflake ID?

A Snowflake ID is a 64-bit unique identifier designed for distributed systems. Created by Twitter in 2010, it allows multiple servers to generate unique IDs independently without any coordination. Discord, Instagram, and many other platforms have adopted this approach.

Unlike auto-increment IDs that require a central database, or random UUIDs that can't be sorted by time, Snowflake IDs are both distributed and time-ordered. You can sort them chronologically and extract the creation timestamp.

How to Decode a Twitter/X Snowflake ID

Every Twitter/X tweet ID, user ID, and other entity ID is a Snowflake containing its creation timestamp. Twitter created the Snowflake system in 2010 to handle their massive scale. To decode a Twitter Snowflake ID manually:

  • Right-shift by 22 bits: This extracts the timestamp portion from the 64-bit ID
  • Add Twitter's epoch: 1288834974657 (November 4, 2010, 01:42:54.657 UTC) - this is when Twitter launched Snowflake
  • Convert to date: The result is Unix milliseconds, which you can convert to a readable date

For example, to find when a tweet was posted, just paste the tweet ID into this tool above and select "Twitter/X" as the platform. The tool automatically extracts the date and time when the tweet was created!

How to Decode a Discord ID

Every Discord ID, whether it's a user, message, server, or channel, is a Snowflake containing its creation time. To decode manually:

  • Right-shift by 22 bits: This extracts the timestamp portion
  • Add Discord's epoch: 1420070400000 (January 1, 2015)
  • Convert to date: The result is Unix milliseconds

Or just paste the ID above and let this tool do it for you!

Why Companies Use Snowflake IDs

  • No coordination needed: Each server generates IDs independently using its worker ID
  • Time-sortable: Newer IDs are always larger. Great for chronological queries
  • Compact: 64 bits vs 128-bit UUIDs. Fits in a single database integer
  • High throughput: 4,096 IDs per millisecond per machine (4M+ IDs/second cluster-wide)
  • Embedded metadata: Extract creation time without a database lookup

The Math Behind Decoding

A Snowflake ID encodes data using bit positions:

  • Bits 63: Sign bit (always 0 for positive numbers)
  • Bits 22-62: Timestamp. milliseconds since platform epoch
  • Bits 17-21: Worker ID. Which machine generated this
  • Bits 12-16: Process ID. Which process on that machine
  • Bits 0-11: Sequence. counter for same-millisecond IDs

To extract each component, use bit shifting and masking. This tool performs these operations automatically.

Snowflake ID FAQ

What is a Snowflake ID?

A Snowflake ID is a 64-bit unique identifier that encodes a timestamp, machine ID, and sequence number. It allows distributed systems to generate unique IDs without central coordination. Discord, Twitter/X, and Instagram all use variations of this format.

How do I convert a Twitter Snowflake ID to a date?

Paste any Twitter/X Snowflake ID (like a tweet ID) into this tool and select "Twitter/X" as the platform. The tool automatically extracts the timestamp by right-shifting the ID by 22 bits and adding Twitter's epoch (November 4, 2010). You'll see the exact date and time when the tweet was posted.

How do I decode a tweet ID to find when it was posted?

Every Twitter/X tweet ID is a Snowflake containing its creation timestamp. Just paste the tweet ID into this decoder tool, select "Twitter/X" as the platform, and you'll instantly see when the tweet was posted in UTC, local time, and relative format. No API calls needed!

What is Twitter's Snowflake ID format?

Twitter uses the standard Snowflake ID structure: 41 bits for timestamp (milliseconds since November 4, 2010), 10 bits for machine/datacenter ID, and 12 bits for sequence number. This allows Twitter to generate millions of unique tweet IDs per second across their distributed infrastructure.

How do I decode a Discord ID to timestamp?

Paste the Discord ID into this tool and select "Discord" as the platform. The tool extracts the timestamp by right-shifting the ID by 22 bits and adding Discord's epoch (January 1, 2015). You'll see the exact creation date and time.

Can I find when a Discord account was created?

Yes! Every Discord user ID contains the account creation timestamp. Just paste the user ID into this tool. This works for all Discord IDs: users, servers, channels, messages, roles, and more.

What is the difference between Discord and Twitter Snowflakes?

Both use the same 64-bit structure, but with different epochs. Discord uses January 1, 2015 as their epoch, while Twitter uses November 4, 2010. The internal bit layout for worker/process IDs may also differ slightly.

Why do Snowflake IDs look like random numbers?

They're not random. They're carefully structured. The large numbers result from packing a timestamp, machine ID, and sequence into 64 bits. The timestamp alone can be billions of milliseconds, making the numbers appear random but they're actually sequential over time.

Can I generate my own Snowflake IDs?

Yes! Use the generator section above. You can specify a custom timestamp, worker ID, and sequence number. This is useful for understanding how Snowflakes are constructed or for testing purposes.

Is my data safe using this tool?

Absolutely. This Snowflake decoder runs entirely in your browser using JavaScript. No data is sent to any server. All decoding happens locally on your device.

Want to learn more?

Understand how Snowflake IDs work in distributed systems, why they're better than UUIDs for databases, and how companies like Twitter and Discord scale with them.

Read the Full Guide