The online generator uses the machine ID you enter to create Snowflake-style numeric identifiers in the browser. The results are time-sortable and compact, which makes them useful for fixtures, prototypes, and examples that need integer IDs.
This page does not assign worker IDs, reserve ranges, or coordinate sequence ownership across services. For production distributed systems, keep machine and worker ID allocation in your own infrastructure so independent generators do not collide.
The decoder splits each Snowflake ID into a 42-bit millisecond timestamp, 10-bit machine ID, and 12-bit sequence. This makes it easier to debug ordering, worker assignment, and same-millisecond collisions when you paste IDs from logs or test data.
Common questions and answers about this topic.
A Snowflake ID is a 64-bit unique identifier scheme originally created by Twitter. It encodes a timestamp, worker/datacenter ID, and sequence number into a single integer.
Use Snowflake IDs in distributed systems that need sortable, unique identifiers without central coordination, such as microservices, message queues, and sharded databases.
Snowflake IDs are 64-bit (smaller than 128-bit UUIDs), time-sortable, and include machine/datacenter information. UUIDs are more widely standardized but larger and not inherently sortable.
Yes. Paste one or more decimal Snowflake IDs and the online decoder will split each ID into its timestamp, machine ID, and sequence fields. Decoding stays in your browser.
No. Snowflake ID generation and decoding run entirely in your browser. The IDs are computed locally with JavaScript and never leave your device.