Snowflake / Discord ID Bit Decoder | Online Free Tool | Elysia Tools
Elysia Tools
Navigation
Development
Snowflake / Discord ID Bit Decoder
Decode 64-bit Snowflake-style IDs for Discord, Twitter, Mastodon, Sonyflake, Instagram, or a custom bit profile. Extract timestamp, worker/process/machine, sequence fields, align platform epochs, and infer a Discord shard when a shard count is supplied.
Execution
Run this tool
Fill in the form, run the tool, and review the result in one place.
Samples
Examples that match this tool
Related
Continue with connected tools and hubs
Tool usage guide
Learn when to use this tool, what it supports, and how real users apply it.
Key facts
Category
Development
Input types
text, select, number, textarea
Output type
html
Sample coverage
4
API ready
Yes
Overview
Snowflake / Discord ID Bit Decoder analyzes 64-bit Snowflake-style IDs for Discord, Twitter, Mastodon, Sonyflake, Instagram, or a custom bit profile. It extracts timestamp and identifier fields, applies the selected epoch, and can infer a Discord shard when a shard count is provided.
When to use
Inspect the creation time and bit fields inside a Discord or other Snowflake-style ID.
Compare IDs from platforms that use different epochs or field layouts.
Analyze a private Snowflake deployment with a custom epoch and low-bit-first field definition.
How it works
1Enter the 64-bit Snowflake ID in the required input.
2Select Discord, Twitter, Mastodon, Sonyflake, Instagram, or Custom as the platform profile.
3Optionally provide a Discord shard count or configure a custom epoch and timestamp unit.
4For a custom layout, enter a JSON field list ordered from the least significant bits first, then review the decoded HTML result.
Use cases
Discord bot development teams can inspect ID timestamps and estimate shard assignment.
Backend engineers can verify worker, process, machine, and sequence fields in distributed identifiers.
Developers maintaining private Snowflake deployments can test custom bit layouts against a selected epoch.
Examples
1. Decode a Discord ID and infer its shard
Discord bot developer
Background
A developer needs to inspect a Discord Snowflake ID and determine which shard it maps to in an eight-shard setup.
Problem
The timestamp and identifier fields are encoded inside the decimal ID and are not directly readable.
How to use
Enter `109580041603153152`, select Discord, and set the Discord shard count to `8`.
Platform: Discord; shard count: 8.
Outcome
The HTML result presents the decoded Discord timestamp and bit fields and includes the inferred shard.
2. Decode a private 47/5/12 Snowflake profile
Backend engineer
Background
A private identifier service uses a custom epoch and assigns 12 bits to sequence, 5 bits to worker, and 47 bits to timestamp.
Problem
A standard platform profile does not match the service's low-bit-first field layout.
How to use
Enter `1234567890123`, select Custom, set the epoch to `2020-01-01T00:00:00.000Z`, choose milliseconds, and provide the custom field JSON.
FAQ
Which ID formats does the decoder support?
It supports Discord, Twitter, Mastodon, Sonyflake, Instagram, and custom Snowflake-style bit profiles.
Can it decode large 64-bit IDs without losing precision?
Yes. The tool is designed to parse 64-bit Snowflake-style IDs without precision loss.
What does the Discord shard count do?
When supplied, the shard count lets the tool infer a Discord shard for the decoded ID.
How do I define a custom profile?
Select Custom, provide an epoch, choose the timestamp unit, and enter a JSON field list ordered from the least significant bits first.
Which timestamp units are available for custom profiles?
Custom timestamps can use milliseconds, 10-millisecond units, or seconds.