Snowflake and Prefixed ID Decoder

Decode supported snowflake layouts with relevant fields shown for the selected mode.

On-device No sign-up Free to use

Inspect input controls

Showing an example. Edit to see your own.

?

Decode mode only. This default is a synthetic layout example, not a verified issued ID. Zero maps to the selected epoch.

?

Custom layout only. Integer Unix milliseconds; the resulting date must stay within UTC years 0001 to 9999.

?

Prefix mode only. The suffix is kept literally and is not decoded or treated as a snowflake.

?

Prefix mode splits at the first exact occurrence; later separators remain in the suffix.

?

Custom widths must total 64. If the top bit is reserved, it must be zero.

Processed in your browser. Your inputs stay on this device.

Result

Showing an example.

Decode the synthetic Discord-layout number 4194305 as one millisecond after its epoch.

Decoded UTC timestamp: 2015-01-01T00:00:00.001Z.

Loading the tool. Your result will appear here.

https://usefreetools.net/snowflake-prefixed-id-decoder · 20 November 2026

Was this helpful?

How to use Snowflake and Prefixed ID Decoder

  1. Choose Decode a decimal snowflake or Split a prefixed identifier.
  2. For decoding, enter the full decimal ID and select Discord, the original Twitter layout or Custom. A custom layout needs its epoch in Unix milliseconds and bit widths totaling 64.
  3. For splitting, enter the prefixed text and literal separator. Both sides of its first occurrence must be nonempty; later separators remain in the suffix.
  4. Read or copy the UTC date and component fields, or the prefix and suffix. Keep the assumed layout with decoded results; the tool cannot identify who issued the value.

Example: Snowflake and Prefixed ID Decoder

Decode the synthetic Discord-layout number 4194305 as one millisecond after its epoch.

You add
Operation: decode; Snowflake layout: discord; Decimal snowflake identifier: 4194305; Custom epoch (Unix milliseconds): 1420070400000; Custom timestamp bits: 42; Custom first worker/group bits: 5; Custom second worker/group bits: 5; Custom sequence bits: 12; Custom reserved top bits: 0; Prefixed identifier: user_00123; Literal prefix separator: _
You get
Decoded UTC timestamp: 2015-01-01T00:00:00.001Z.

Options

Named layouts
Discord uses a 2015-01-01 epoch with 42 timestamp bits, two five-bit internal fields and 12 sequence bits. The Twitter preset follows the original 2010 implementation, with its own epoch and a reserved top bit; it does not describe every current identifier.
Custom layout
Enter the Unix-millisecond epoch and all five bit widths. Timestamp, group fields, sequence and reserved bits must total 64. If a top bit is reserved, the entered ID must leave it zero.
Prefix splitting
The first exact separator divides prefix and suffix. Leading zeros and additional separators remain in the suffix, which is not interpreted as a number, timestamp or encoded service ID.

Supported inputs and limits

  • Decode one unsigned 64-bit decimal identifier, written as 1 to 20 digits without exponent notation.
  • Integer parsing preserves all bits.
  • Custom widths allow 1 to 64 timestamp bits, 0 to 63 bits for each worker/group field and sequence, and 0 or 1 reserved bit, totaling 64.
  • The epoch and decoded UTC date must lie within years 0001 to 9999.
  • Prefix input accepts 1 to 256 characters and a 1 to 8 character literal separator, without controls.
More details

The selected layout is an assumption, not evidence of origin or authenticity.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

A decoded date depends on the entered convention

The decoder uses integer arithmetic so a 64-bit decimal identifier is not rounded through JavaScript Number. Its timestamp is a UTC interpretation under your selected epoch and bit allocation. A plausible date does not establish which system issued an identifier or whether it is genuine. Keep the layout name with copied results when comparing records.

Questions about Snowflake and Prefixed ID Decoder

Is every large number a Discord ID?

No. The selected layout is an assumption. The tool cannot establish where an identifier came from.

Why use integer text?

Large IDs exceed JavaScript’s safe Number range. Decimal text is parsed with BigInt to preserve every bit.

Does prefix mode inspect the suffix?

It splits at the selected separator. The suffix stays text rather than being guessed as a snowflake.

Page updated · Project managed by Tony Hines · Report a problem with Snowflake and Prefixed ID Decoder