Snowflake ID Decoder
Decode an unsigned decimal ID with an optional epochMs using the fixed Twitter-compatible 41/5/5/12 layout. It does not detect layouts or call an API.
About this snowflake id decoder
Decode an unsigned decimal ID with an optional epochMs using the fixed Twitter-compatible 41/5/5/12 layout. It does not detect layouts or call an API Transforms and validates developer data structures locally, preventing confidential payload exposure during data wrangling.
Syntax parsing & data transformation logic
Reads an unsigned decimal 64-bit Snowflake ID or JSON with id and optional epochMs, uses BigInt to split a Twitter-compatible 41/5/5/12 layout, then prints UTC timestamp, datacenter, worker and sequence.
Worked conversion & output 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:
Syntax constraints & input size limits
Assumes the Twitter-compatible layout and default epoch 1288834974657 ms; other Snowflake schemes can decode incorrectly. IDs outside unsigned 64-bit range and timestamps outside JavaScript Date range error.
Data conversions and formatting in Snowflake ID Decoder reflect standard structured syntax. Verify parsed outputs against your target runtime before deployment.
Local client execution boundary
Data parsing and transformations in Snowflake ID Decoder execute in the local browser tab without remote data transmission.
Data format specifications & language standards
Data interchange formats and language grammar specifications:
- Standard Browser Web API / Algorithm Implementation (No single external RFC/ISO standard)
Snowflake ID Decoder verification · Audit standards
How to use it
- Enter an unsigned 64-bit Snowflake ID, or JSON with `id` and optional `epochMs`.
- Split the value using the Twitter-compatible 41/5/5/12 bit layout and add the configured epoch to the timestamp field.
- Read UTC timestamp, datacenter, worker and sequence values.
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.