❄️ Snowflake ID Decoder
Paste a Snowflake ID and pick the service to see exactly when it was created, plus the machine and sequence bits packed inside.
Created at (UTC)
2016-04-30T11:18:25.796Z
Unix ms: 1,462,015,105,796
Timestamp
1462015105796
Worker ID
1
Process ID
0
Increment
7
64-bit binary (timestamp · machine · sequence)
000000100111000100000110010110101100000100 0000100000 000000000111
A Snowflake ID packs a creation time and machine/sequence info into one 64-bit number. The high 41 bits are a millisecond timestamp measured from the service's own epoch (Discord: 2015-01-01, Twitter/X: 2010-11-04), then 10 bits identify the generating machine (Discord splits this into a 5-bit worker and 5-bit process), and the low 12 bits are a per-millisecond counter. Pick the right service so the timestamp decodes correctly. 🔒 Decoded in your browser.
How the snowflake id decoder works
A Snowflake is a 64-bit ID that many platforms mint instead of a random UUID, and it is not random at all — the top 41 bits are a millisecond timestamp counted from the service's own epoch (Discord uses 2015-01-01, Twitter/X uses 2010-11-04, Instagram uses 2011-08-24). Below that sit machine bits (Discord splits its 10 into a 5-bit worker and 5-bit process) and a 12-bit per-millisecond sequence counter. This tool reads the ID as a BigInt, adds the chosen epoch back onto the timestamp bits to recover the exact creation instant, and unpacks the remaining fields — so you can tell when a Discord message, tweet or post was created straight from its ID.
Pick the correct service first: the same 64-bit number decodes to a completely different date under a different epoch, so a Discord ID read with the Twitter epoch will look decades off. For anything outside the presets, enter the epoch in milliseconds directly. The decoded worker and process IDs identify the generating server, not a user, and the sequence is only meaningful within a single millisecond. Everything runs locally in your browser — nothing about the ID is transmitted.
Frequently asked questions
How do I get the timestamp from a Discord ID?
Paste the ID and leave the service on Discord. The tool shifts the ID right by 22 bits to isolate the timestamp, adds the Discord epoch (1420070400000 ms, i.e. 2015-01-01), and shows the exact UTC creation time of that user, message or channel.
Why do I have to choose the service?
Each platform counts its timestamp from a different starting point (epoch). The bits are identical, but the epoch you add back determines the real date — so a Discord ID decoded with the Twitter epoch will be wrong by about four years. Choosing the service applies the right epoch.
What are the worker and process IDs?
They identify which server and worker generated the ID, so two IDs created in the same millisecond on different machines still differ. Discord splits its 10 machine bits into a 5-bit worker and a 5-bit process; they describe infrastructure, not the user or content.
Can I decode Twitter/X or Instagram IDs too?
Yes — select Twitter/X or Instagram from the list to apply their epochs (2010-11-04 and 2011-08-24). You can also enter a custom epoch in milliseconds for any other Snowflake-style scheme, including a raw Unix-epoch variant.
Is a decoded timestamp exact?
The timestamp is stored to the millisecond and is recovered exactly, so the creation time is precise. It reflects when the ID was minted (message sent, account created, etc.), which is effectively the object's creation time on that platform.
Is the ID sent anywhere?
No — decoding is pure arithmetic done entirely in your browser with BigInt, so nothing is uploaded and it works offline.