Developer Tools
Snowflake ID Decoder
Paste a Twitter, Discord, or Reddit snowflake ID and instantly see when it was created, plus the worker and sequence bits hidden inside. Switch epochs for each platform — all decoded locally in your browser.
Timestamp (ms)
—
ISO date (UTC)
—
Local time
—
Worker ID
—
Process ID
—
Sequence
—
What makes this tool different
Multi-platform epochs
Decode with Twitter, Discord, or Reddit epochs — each platform starts its clock at a different moment.
Full bit breakdown
See the timestamp, worker ID, process ID, and sequence fields exactly as the ID encodes them.
ISO date output
Get the creation time as both raw milliseconds and a readable ISO 8601 date.
100% in-browser privacy
All decoding happens locally. Your IDs never leave your device.
About this tool
Snowflake ID Decoder: everything you need to know
Every tweet, Discord message, and Reddit post has a hidden timestamp baked into its ID. Snowflake IDs — the 64-bit integers that power distributed ID generation — store the creation time in their most significant bits, so decoding an ID reveals exactly when the object was created, down to the millisecond.
This snowflake ID decoder splits any 64-bit ID into its three fields: the 41-bit timestamp, the 10-bit worker or machine ID, and the 12-bit sequence. Choose the platform that issued the ID — Twitter, Discord, or Reddit — and the correct epoch is applied so the date is accurate.
The timestamp output appears two ways: raw Unix milliseconds and a human-readable ISO 8601 date. That makes the tool useful for support work (when was this account created?), audit trails, and understanding ID ranges in datasets.
The worker ID and sequence fields are interesting too. The worker bits reveal which machine or shard generated the ID, and the sequence shows how many IDs were issued in that millisecond. Together they explain why a platform can mint thousands of unique IDs per millisecond across many machines.
Because the format is so widely copied, the decoder also works for any system that follows the Twitter-style layout with a known epoch. Paste an ID, verify it decodes to a sensible time, and you have confirmed the system's snowflake layout.
Privacy is built into the design. Decoding runs entirely in your browser — your IDs never leave your device. Open the DevTools Network tab and you will see zero requests.
FAQ
Snowflake ID Decoder — frequently asked questions
What is a snowflake ID and how is it structured?
A snowflake ID is a 64-bit integer Twitter introduced for distributed IDs. It packs a 41-bit millisecond timestamp (relative to a platform epoch), a 10-bit worker/machine ID, and a 12-bit sequence into a single number. The format is now used by Discord, Reddit, Instagram, and many internal systems.
How do I decode a Twitter / Discord / Reddit snowflake ID?
Split the 64-bit value into its fields: shift right by 22 bits for the timestamp, extract the 10 worker bits, and take the low 12 bits as the sequence. Add the platform epoch to the timestamp and you get the creation time. This tool does that math for you.
Why are snowflake IDs sortable by time?
Because the timestamp occupies the most significant bits, comparing two snowflake IDs numerically is the same as comparing their creation times. That makes snowflake IDs naturally ordered, which is why they are popular for primary keys in distributed databases.
What epoch does each platform use?
Twitter uses epoch 1288834974657 (November 2010), Discord uses 1420070400000 (January 2015), and Reddit uses 1546300800000 (January 2019). The decoder applies the selected platform's epoch automatically.
Can a snowflake ID be generated locally?
Yes. If you know the epoch, take the current time in milliseconds, subtract the epoch, shift left 22 bits, add a worker ID and a sequence counter. The result is a valid snowflake that sorts correctly with platform IDs.
Is the snowflake ID decoder free and private?
Yes. OpenToolLab's snowflake ID decoder is completely free, requires no signup, and decodes IDs entirely in your browser — nothing is sent anywhere.
What is the difference between a snowflake ID and a UUID?
Snowflake IDs are 64-bit, sortable by creation time, and only unique within a single system — while UUIDs are 128-bit, effectively globally unique, and (in v4) carry no ordering information. Use snowflakes when you need time-ordered IDs; use UUIDs when you need maximum uniqueness across independent systems.
Why do Discord and Twitter use snowflake IDs instead of auto-increment numbers?
Because IDs are generated across many servers at once, an auto-increment counter on one database would be a bottleneck and a single point of failure. Snowflake IDs let any server mint a unique, time-ordered ID locally — no coordination, no central counter, and the timestamp is embedded for free.
Keep exploring