Snowflake ID

Snowflakes are 64 bits in binary. (Only 63 are used to fit in a signed integer.) The first 41 bits are a timestamp, representing milliseconds since the chosen epoch. The next 10 bits represent a machine ID, preventing clashes. Twelve more bits represent a per-machine sequence number, to allow creation of multiple snowflakes in the same millisecond. The final number is generally serialized in decimal. Snowflakes are sortable by time, because they are based on the time they were created. has the snowflake ID . The number may be converted to binary as , with pipe symbols denoting the three parts of the ID. • The first 41 (+ 1 top zero bit) bits convert to decimal as . Add the value to the X Epoch of (in Unix time milliseconds), the Unix time of the tweet is therefore : February 10, 2025 13:34:39.256 UTC. • The middle 10 bits are the machine ID. • The last 12 bits decode to , meaning this tweet is the 322'nd snowflake processed this millisecond. == Usage ==

The format was first announced by Twitter in June 2010. Due to implementation challenges, they waited until later in the year to roll out the update. • X (formerly Twitter) uses snowflake IDs for tweets, direct messages, users, lists, and all other objects available over the API. • The 10-bit machine ID field can be further split into sub-fields by a given implementation. For example, the archived version of the original Twitter snowflake library in Scala splits it into a 5-bit data center ID and a 5-bit worker ID. • Discord also uses snowflakes, with their epoch set to , which translates to the zeroth second of the year 2015. • Instagram uses a modified version of the format, with 41 bits for a timestamp, 13 bits for a shard ID, and 10 bits for a sequence number. • Mastodon's modified format has 48 bits for a millisecond-level timestamp, as it uses the UNIX epoch. The remaining 16 bits are for sequence data. == See also ==