Snowflake ID Decoder (Discord, Twitter/X)
Turn a Discord or Twitter/X snowflake ID into its creation time and worker, process and sequence fields, or turn a date into the snowflake for searching by time.
Bits: 64-bit ID = 42-bit timestamp (milliseconds since the epoch) · 5 bits · 5 bits · 12-bit sequence. Times are UTC.
Discord, Twitter/X and many other systems give every message, user and post a 64-bit "snowflake" ID that starts with its creation time. This decoder turns IDs into the exact UTC time and the worker, process and sequence fields, and the reverse direction turns a date into the smallest ID for that moment — handy for Discord’s before/after search and API pagination.
How to use this tool
- Paste one or more IDs (copy them with Discord’s developer mode, or from a post URL).
- Pick the platform so the right epoch is used, or enter a custom epoch.
- Read the creation time and the internal fields.
- To search by time, switch to Date → ID and use the smallest ID as the after or since parameter.
Formula
timestamp (ms) = (ID >> 22) + epoch; field 1 = (ID >> 17) & 31; field 2 = (ID >> 12) & 31; sequence = ID & 4095. In reverse, ID = (ms − epoch) << 22.
Discord’s epoch is 1420070400000 (1 January 2015 UTC); Twitter’s is 1288834974657 (4 November 2010). IDs exceed JavaScript’s safe integer range, so the page uses BigInt arithmetic.
Example
Discord’s documentation example 175928847299117063 shifts right by 22 bits to 41,944,705,796 ms after the Discord epoch: 2016-04-30 11:18:25.796 UTC, internal worker 1, process 0, increment 7. The smallest ID for that millisecond is 175928847298985984.
Frequently asked questions
Can I find out who posted from an ID?
No. A snowflake only encodes the time and which internal worker created it; it carries no user information.
Why does a large ID lose digits in spreadsheets?
Snowflakes are bigger than 2^53, the largest whole number a double-precision float holds exactly. Keep them as text, as this page does.
Do other services use snowflakes?
Many do, with their own epochs and bit layouts. Use the custom epoch if a service documents one; the 22-bit split shown here matches Discord and Twitter.
Sources
Last updated:
Page address with these inputs: https://kakao.mobile/tools/snowflake-id-decoder/
Cite or embed this tool
kakaoCalc. (2026, November 8). Snowflake ID Decoder (Discord, Twitter/X). https://kakao.mobile/tools/snowflake-id-decoder/
“Snowflake ID Decoder (Discord, Twitter/X).” kakaoCalc, 8 Nov. 2026, kakao.mobile/tools/snowflake-id-decoder/.
Paste this code into your page. The widget runs in your visitors' browsers, shows no ads and keeps a link back to this page. Embedding terms