Snowflake ID Parser
Decode and generate Snowflake IDs
Paste a Snowflake ID first to decode timestamp and node info immediately; generator mode notes are available in Advanced mode.
Fixed Twitter layout: sign 0 + time 41 + datacenter 5 + worker 5 + sequence 12 bits; epoch 1288834974657 ms. Composes test IDs without coordinating nodes or sequences.
The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.
About this tool
Inspect the fixed classic Twitter Snowflake layout: one zero sign bit, 41 elapsed-millisecond bits, 5 datacenter bits, 5 worker bits and 12 sequence bits. The epoch is 1288834974657 ms and cannot be changed. Decimal IDs from 0 to 9223372036854775807 are parsed exactly with BigInt. Test generation supports timestamps through 3487858230208 ms. This tool composes fields; it does not coordinate nodes, advance sequences or ensure unique production IDs. Other Snowflake layouts may decode incorrectly here.
Production Snippets
Example
text
9223372036854775807
Timestamp: 3487858230208 ms
Datacenter: 31 · Worker: 31 · Sequence: 4095Failure Clinic (Common Pitfalls)
Snowflake layouts are not interchangeable
Cause: Different services can choose different epochs and bit allocations.
Fix: Use this fixed Twitter interpretation only when it matches the producer’s specification.
Scenario Recipes
Decode the largest supported Twitter-layout ID
Goal: Check field boundaries without losing integer precision.
- Paste 9223372036854775807 and decode.
- Confirm timestamp 3487858230208, datacenter 31, worker 31 and sequence 4095.
- Try 9223372036854775808 and confirm the range error.
Result: The displayed 64-bit representation retains a zero sign bit for every accepted value.
Frequently Asked Questions
Which Snowflake layout and epoch are supported?
Only the fixed classic Twitter layout: 0 sign bit + 41 timestamp + 5 datacenter + 5 worker + 12 sequence bits, with epoch 1288834974657 ms. There is no layout or epoch selector.
What ID syntax and range can I decode?
Use a decimal string of 1–19 digits from 0 to 9223372036854775807. Signs, fractions, scientific notation and hexadecimal prefixes are rejected. BigInt preserves exact integer digits.
What generation fields are valid?
Timestamp is an integer from 1288834974657 to 3487858230208 ms; datacenter and worker are each integers 0–31; sequence is an integer 0–4095.
Does generating IDs guarantee uniqueness?
No. Reusing the same fields creates the same ID. The tool does not coordinate nodes, reserve worker numbers or increment sequences; it is a test-field composer.
Does an extracted time prove the ID origin?
No. It is an interpretation under this layout and epoch. IDs using another layout or chosen timestamp need their own specification.
Is input uploaded or saved?
Parsing and test generation run in the browser with no ID-content upload. This tool does not save its inputs in localStorage; copying places selected values on your clipboard.
Keep browsing