Discord Snowflake Decoder: When Was This ID Created?
Discord Snowflake Decoder: When Was This ID Created? Every Discord ID is a 64-bit snowflake with a millisecond timestamp packed into its top bits, so the decoder above reads that field and shows the exact creation date for each ID you paste. The calculation runs in your browser.
What the decoder shows for each ID
Paste one ID per line and the tool returns a card for each one. A card lists the creation date in your local timezone, the same moment in UTC as an ISO 8601 string, the Unix timestamp in seconds and in milliseconds, the offset from the Discord epoch, the internal worker ID, process ID, and increment, a paste-ready Discord timestamp, and the full 64-bit value written out in binary.
The Discord timestamp line is the practical one. Copy it into a message and Discord renders the creation moment in the local timezone of whoever reads it. That turns a raw identifier into a readable date without asking anyone else to run a calculation.
Nothing leaves your browser. There is no upload step and no sign-in, which matters when you are checking an ID that came from a report, a log line, or a message you would rather not hand to a third party.
How to decode a snowflake by hand
Discord documents the layout at https://discord.com/developers/docs/reference#snowflakes. The value is 64 bits wide and split into four fields: a 42-bit timestamp, a 5-bit internal worker ID, a 5-bit internal process ID, and a 12-bit increment.
The timestamp field starts at bit 22 and counts milliseconds since the Discord epoch, 1420070400000, which is 1 January 2015 at 00:00:00 UTC. The formula is (id >> 22) + 1420070400000. The worker ID comes from (id & 0x3E0000) >> 17, the process ID from (id & 0x1F000) >> 12, and the increment from id & 0xFFF.
Each ID carries the millisecond it was created, so two objects made in the same second still resolve to different milliseconds. That is why a snowflake is more precise than a Unix timestamp rounded to the second, and why the decoder prints milliseconds next to the seconds value.
Discord's ID limits and API rules
Discord IDs are 64-bit unsigned integers, and the API sends them as strings. That is not a quirk to ignore. A 20-digit snowflake is larger than the biggest integer JavaScript can hold without losing precision, so reading one as a number quietly corrupts the trailing digits and gives you a date that is off by months.
The decoder uses BigInt for the same reason. Every bit shift runs on an exact integer, and the largest value it accepts is 18446744073709551615, which is 2 to the power of 64 minus one.
Because the API returns IDs as strings, keep them that way. Do not let a spreadsheet, a JSON parser, or a database driver turn one into a float before you read it back.
Edge cases the decoder catches
Not every string is a Discord ID, and the tool says so instead of returning a wrong date. Text with letters or symbols is rejected as non-numeric. A number with fewer than 17 digits is too short to be a snowflake.
A number above 18446744073709551615 does not fit in 64 bits, so it is rejected as too large. An ID whose timestamp lands in the future is rejected too, since a real Discord object cannot have been created later than today.
The future check catches typos and hand-edited values. Adding a digit to the end of a valid ID multiplies the number by ten, which pushes the timestamp far ahead, and that is a common way to land on a date in 2030.
What the worker ID, process ID, and increment mean
The last 22 bits are internal bookkeeping. The worker ID and the process ID point to which of Discord's internal processes issued the ID, and the increment counts how many IDs that worker handed out since it started up. Discord does not publish the mapping, and the values shift over time.
They still tell you something. Two IDs that share a worker and a process came from the same internal process, so they were usually issued close together. A jump in the worker ID between two IDs from the same server hints at a move to a different part of Discord's fleet.
For live details on a user or a server, the Discord ID lookup tool reads the same snowflake and adds what the API returns when our bot has access to that entity. For the reverse job, the Discord timestamp generator takes a date you pick and produces a tag you can paste into a message.
When the creation date matters
Account age is the first thing a moderator checks on a new member. A Discord ID that decodes to yesterday carries different weight than one that decodes to 2016, and the decode is quick enough to do during a live conversation.
The same reasoning applies to bots, webhooks, and integrations. A webhook created last week has had no time to collect a history, and a server ID that predates a particular feature tells you which API version it was created against.
For bulk work, decoding a list of IDs in one pass turns a wall of identifiers into a timeline. Sort the results and you can see when a channel was created, when a bot joined, and when the earliest of several related objects appeared.
Explore more discord tools on Tolz.me.