Snowflake ID Decoder
Decode exact Twitter, Discord and custom Snowflake IDs, inspect UTC timestamps and bit fields, or compose test IDs without rounding.
Exact decimal IDs
IDs stay as decimal strings and BigInt throughout decoding and composition. They never pass through a floating-point number. Paste up to 1,000 IDs; the first invalid ID stops the batch rather than silently dropping a row. JSON includes UTC time, Unix milliseconds, sequence and a padded binary representation.
Platform layouts
Discord uses 42 timestamp bits followed by 5 worker bits, 5 process bits and 12 sequence bits, with epoch 1420070400000 ms. Twitter’s archived 2010 layout uses 41 timestamp bits, 5 datacenter bits, 5 worker bits and 12 sequence bits, with epoch 1288834974657 ms. Choose the correct platform before interpreting a timestamp.
Custom layouts and composition
Custom layouts contain 1–63 timestamp bits and 0–32 bits for each remaining field, with a total of at most 64. Zero-width fields accept only zero. UTC composition requires an ISO timestamp ending in Z and values that fit their bit ranges. It does not allocate IDs across services or guarantee uniqueness.
Reference
Questions & answers
Does a decoded time prove when a record was created?
No. IDs can be composed or assigned elsewhere. A decoded timestamp is only the time stored in this particular format.
Are inputs uploaded or saved?
No. The tool runs locally in a Web Worker and does not send IDs to an API or save them in local storage. Copy and Download use the current result; edits or cancellation discard stale output.