Snowflake ID Decoder
Snowflake ID Decoder: Extracts 41-bit millisecond offset, 5-bit datacenter ID, 5-bit worker ID, and 12-bit sequence counter.
About this snowflake id decoder
Snowflake ID Decoder — browser-based utility.
How this tool works
Implements client-side Snowflake ID Decoder operations. Extracts 41-bit millisecond offset, 5-bit datacenter ID, 5-bit worker ID, and 12-bit sequence counter specifically designed for a distributed backend engineer decodes a 64-bit twitter/discord snowflake id to inspect creation timestamp.
- Input Classification & Format Detection: Automatically distinguishes between second, millisecond, microsecond, and nanosecond timestamp scales, or detects hex/string representation.
- Sanitization & Range Enforcement: Verifies that timestamps fall within valid calendar epochs (-62167219200 to 253402300799) and that UUID strings conform to RFC 4122 hexadecimal grouping.
- Algorithmic Synthesis & Permutation: Generates monotonic timestamp-prefixed binary words or maps characters to standard W3C entity codepoint tables.
- Output Delivery & Verification: Displays human-readable UTC/local dates, hexadecimal representations, and verified entropy statistics.
Worked example
Scenario: Decode a decimal Snowflake with the default epoch.
Sample input:
Processing: Use BigInt shifts for the 41/5/5/12 fields.
Illustrative output:
Limits and verification
Rejects timestamps resulting in dates before the year 0001 or after the year 9999. UUID parsing strictly requires 32 hexadecimal digits separated by standard 8-4-4-4-12 hyphens. Non-ASCII characters in HTML entity decoders are checked against the WHATWG Named Character Reference standard.
Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.
Browser processing boundary
Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.
Relevant references
These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.
- Standard Browser Web API / Algorithm Implementation (No single external RFC/ISO standard)
Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology
How to use it
- Enter, paste, or select your input data into the Snowflake ID Decoder workspace controls.
- Review available parameter fields, units, formats, or options configured for your task.
- Click the action button or observe immediate live calculations rendered in your browser runtime.
- Inspect the resulting output and any diagnostic messages, then copy or download the result if needed.
Frequently asked questions
How does Snowflake Decoder split an ID?+
It accepts unsigned decimal text, or a JSON object with `id` and optional integer `epochMs`, parses with BigInt, then extracts a Twitter-compatible 41/5/5/12 timestamp offset, datacenter, worker, and sequence.
What result does the documented Snowflake ID produce?+
With default epoch 1288834974657, `175928847299117063` renders timestamp `2012-03-03T13:01:20.453Z`, datacenter 1, worker 0, and sequence 7.
Which Snowflake inputs are rejected or limited?+
The ID must be an unsigned decimal integer no larger than 64 bits and epoch must be integer text. A decoded timestamp outside the safe JavaScript Date number range errors; it does not auto-detect Discord or custom layouts.
Does decoding query a platform API?+
No. The page extracts fields from entered text with BigInt in its own result path and has no platform API control. It cannot prove that an ID belongs to a real Twitter-compatible service.