This Discord snowflake to timestamp converter reads the date and time hidden inside any Discord ID. Paste a user, message, channel or server ID and you get the exact creation moment in UTC and in your local time, plus a ready-made Discord timestamp code. It is handy for moderators, bot developers and anyone curious about an account’s age.
Runs entirely in your browser — nothing is uploaded. The first valid ID fills the cards; every line appears in the CSV.
How the Discord Snowflake to Timestamp Converter Works
Every Discord ID is a 64-bit number called a snowflake. Its top 42 bits store the milliseconds elapsed since Discord’s own epoch, the first moment of 2015 in UTC. The Discord snowflake to timestamp tool shifts those bits down, adds the epoch back and turns the result into a normal Unix time. The low 22 bits name the internal worker, the process and a per-process counter, which matter only when debugging.
Formula: Unix ms = floor(ID ÷ 2^22) + 1,420,070,400,000. Worker = floor(ID ÷ 2^17) mod 32. Process = floor(ID ÷ 2^12) mod 32. Increment = ID mod 4,096. In Twitter (X) mode the epoch is 1,288,834,974,657 instead, and the two middle fields are the datacenter and worker. The math runs on BigInt, so 19-digit IDs never lose precision.
- Platform — Discord (epoch January 1, 2015, 00:00 UTC) or Twitter (X) (epoch November 4, 2010).
- Snowflake IDs — one numeric ID per line, up to 20 digits. Spaces are stripped and invalid lines are flagged.
- Copy, Download CSV, Clear — copy or save every result as CSV (ID, UTC ISO time, Unix seconds, Unix ms), or empty the box.
Example Scenarios
| Platform | Snowflake ID (input) | UTC time (output) | Unix ms | Bit fields |
|---|---|---|---|---|
| Discord | 175928847299117063 | 2016-04-30 11:18:25.796 | 1462015105796 | 1 / 0 / 7 |
| Discord | 80351110224678912 | 2015-08-10 17:26:37.529 | 1439227597529 | 0 / 1 / 0 |
| Discord | 1000000000000000000 | 2022-07-22 11:22:59.101 | 1658488979101 | 18 / 0 / 0 |
| Discord | 1234567890123456789 | 2024-04-29 18:12:02.167 | 1714414322167 | 20 / 24 / 277 |
| Twitter (X) | 1445078208190291968 | 2021-10-04 17:27:47.744 | 1633368467744 | 11 / 18 / 0 |
Discord ID to Date: Tips for Accurate Results
To copy any ID, turn on Developer Mode in User Settings under Advanced. Then right-click a user, message, channel or server (long-press on mobile) and choose the Copy ID option. A few habits keep the Discord snowflake to timestamp result honest.
- For a Discord account creation date, copy the user ID, not a message ID. A message ID gives the moment that message was sent.
- A server ID reveals when the server was created, and a channel ID when that channel was made.
- Keep IDs as text. Spreadsheets store numbers with about 15 significant digits, so a pasted 18-digit ID gets rounded and the date shifts.
- In your own code, avoid plain JavaScript numbers above 9,007,199,254,740,991; this snowflake id decoder uses BigInt for that reason.
- The twitter snowflake converter mode only makes sense for IDs created after late 2010, when Twitter switched from sequential IDs.
The embedded time records when an ID was generated, so it cannot be changed later by editing a profile, but it says nothing about who controls the account today. For the full bit layout and other services that use the scheme, read Wikipedia’s article on Snowflake IDs.
Discord Snowflake to Timestamp FAQ
How do I turn a Discord snowflake to timestamp format for chat?
Paste the ID and the tool shows a code such as <t:1462015105:F>. Send that code in any Discord message and it renders as a full date and time in each reader’s own time zone. Swap the F for R to show relative time instead, such as 3 years ago.How accurate is the converted time?
It is exact to the millisecond. Discord’s servers write the time into the ID when the object is created, so there is no lookup or estimate involved. The only extra step is the time zone: the UTC value is fixed, while the local value follows the clock settings of your device.How do I find a Discord account creation date?
Enable Developer Mode in User Settings under Advanced, right-click the person’s name and copy their user ID. Paste it here and the UTC time shown is when the account was registered. Nothing is sent to Discord or anywhere else, so the user is never notified that you checked.Does this snowflake id decoder work for Twitter IDs?
Yes. Switch the platform toggle to Twitter (X) and the tool uses the November 4, 2010 epoch instead of the 2015 Discord one. Post and user IDs created after Twitter adopted snowflakes decode correctly, while older sequential IDs return dates that mean nothing, so check the year looks sensible.Can I generate a snowflake from a timestamp?
You can reverse the rule: subtract the epoch from a Unix time in milliseconds, then multiply by 2^22. Bots use numbers made this way as before and after limits when paging through message history. This page only decodes IDs, but the formula section above shows the exact steps to build one.Why does my ID show a strange date such as 2015 or the future?
Usually the number is wrong. A truncated or rounded ID, often from a spreadsheet, shifts the date, and very small numbers decode to the epoch itself. Check the platform toggle too: a Twitter ID read as a Discord ID lands about four years too late.Related Tools
Snowflakes are just large binary numbers, so the binary to decimal converter for checking bit fields helps when you inspect the worker and process bits. Need the creation time for someone in another city? The time zone converter for UTC and local times handles that, and the date calculator for adding or subtracting days shows how long ago an ID was made. Keep the Discord snowflake to timestamp tool bookmarked next to them.