Discord Snowflake Decoder
Turn any Discord ID into its exact creation date, internal worker & process IDs, and ready-to-paste timestamp markup — all in your browser.
💻 Desktop: Settings → Advanced → turn on Developer Mode, then right-click a name → Copy User ID.
📱 Mobile: Profile tab → ••• (top-right) → Copy User ID.
Decoded snowflake
Enter any Discord ID above to decode its creation date and internals.
Snowflake anatomy (64 bits)
Discord timestamp markup
Paste this into any chat for a live, timezone-aware date.
—
—
Live avatar & banner via the public Lanyard API — falls back to the default avatar when a profile is private or unmonitored.
From a 64-bit ID to an exact creation date
Every Discord ID is a snowflake — a 64-bit number with a timestamp baked into its highest bits. Here is how the ID is structured, how that timestamp is decoded, what the remaining bits mean, and how to grab any object's ID inside Discord — all in your browser.
One unique ID on every Discord object
A snowflake is the unique 64-bit integer Discord stamps onto everything it stores — every user account, message, channel, category, server (guild), role, and custom emoji carries one. You see them as long numbers like 175928847299117063, usually 17 to 20 digits depending on when the object was made. Because Discord operates at massive scale across many machines, it needs IDs that are guaranteed unique without a central counter, and the snowflake format solves that: each ID is minted locally yet can never collide with another anywhere in the platform.
What makes a snowflake special is that the number is not random — it is a tightly packed record of when and where it was generated. The most significant bits hold a millisecond-precision timestamp, and the lower bits hold internal machine and sequence data. That design means the ID itself is a self-contained receipt of its own creation: no database lookup and no API request are needed to learn a message's or account's exact age. This decoder simply unpacks those bit fields and translates the timestamp portion into a human date.
How the creation date falls out of the ID
The top 42 bits of every snowflake store the number of milliseconds since the Discord epoch — a fixed reference point of 2015-01-01 at 00:00:00 UTC, which as a Unix timestamp is 1420070400000. To pull that value out, you shift the whole ID right by 22 bits, discarding the worker, process, and increment fields below, then add the epoch back. In one line: (id >> 22) + 1420070400000 gives the exact Unix millisecond the object was created. Discord counts from 2015 rather than 1970 so the timestamp field stays small enough to fit in 42 bits for decades.
Once the tool has that Unix millisecond value, it renders the moment three ways: in UTC for an unambiguous reference, in your browser's local timezone so it reads naturally, and as a relative age like "created 6 years ago." Because the arithmetic is exact and deterministic, two people decoding the same ID always get the same instant down to the millisecond. Nothing about this step touches the network — it is plain integer math running in your browser, so even a private or deleted account's ID still yields its original creation time.
What each of the 64 bits actually holds
Read from the most significant bit down, a snowflake divides into four fields. The first 42 bits are the millisecond timestamp covered above. The next 5 bits are the internal worker ID, and the 5 bits after that are the internal process ID — together they identify which of Discord's machines and which process on it generated this particular number. The final 12 bits are a per-process increment: a counter that ticks up for each ID a single process mints within the same millisecond, then resets. This tool splits any ID you paste into exactly these four labeled parts.
Those lower 22 bits are what let Discord create many unique IDs in the very same millisecond without coordination between servers. With 5 bits each for worker and process, up to 32 workers and 32 processes can run in parallel, and the 12-bit increment gives each of them 4,096 distinct IDs per millisecond before the counter wraps. Multiply it out and the format can mint millions of collision-free IDs per second across the fleet. For decoding purposes these fields are mostly internal trivia, but they confirm the ID is a genuine, well-formed Discord snowflake.
Enable Developer Mode, then Copy ID
Discord hides raw IDs by default, so first turn on Developer Mode: open User Settings, go to the Advanced tab, and flip the Developer Mode toggle. That adds a Copy ID entry to context menus everywhere in the app. Now right-click almost anything — a user's name or avatar, a specific message, a channel, or the server icon — and choose Copy ID to put that snowflake on your clipboard. On the mobile apps the flow is the same: enable Developer Mode in settings, then long-press an object and tap Copy ID.
Paste any ID you copy into the field above and it decodes instantly. The most popular use is checking account age: copy your own user ID to see the exact second you joined Discord, or copy someone else's to judge how new an account is — a handy signal when screening a suspicious DM or a fresh member. The same trick dates a message, reveals when a channel or server was founded, and works even on accounts you cannot otherwise inspect, since the creation time is locked into the ID and cannot be edited.
Frequently Asked Questions
What is a Discord ID (snowflake)?
A Discord ID, or snowflake, is the unique 64-bit number Discord assigns to every object it stores — users, messages, channels, servers, roles, and emoji. It looks like a long integer such as 175928847299117063. The value is not random: its upper bits encode exactly when the object was created, which is why any ID can be decoded back into a precise timestamp.
How do I find someone's Discord user ID?
First enable Developer Mode under User Settings → Advanced. Then right-click any person's name or avatar — in chat, a member list, or their profile — and choose Copy ID. On mobile, long-press the user and tap Copy ID. Paste that number into the decoder above to reveal exactly when their account was created.
How do I convert a Discord ID to a date/timestamp?
Paste the ID into the tool and it does the math instantly: it shifts the number right by 22 bits and adds Discord's epoch, 1420070400000 milliseconds, giving the exact Unix time the object was minted. You get that moment shown in UTC, in your local timezone, and as a relative age — with no API call.
How do I enable Developer Mode in Discord?
Open User Settings (the gear icon), go to the Advanced tab, and toggle Developer Mode on. That single switch adds the Copy ID option to every right-click and long-press menu across the app. Without it, Discord hides raw IDs, so enabling Developer Mode is the prerequisite for grabbing any snowflake to decode here.
When was my Discord account created?
Copy your own user ID (enable Developer Mode, right-click your name, Copy ID) and paste it above. Because your account's creation millisecond is encoded in the ID's top 42 bits, the decoder shows the precise date and time you signed up — accurate to the second, and impossible to fake by editing a profile.