Snowflake ID to timestamp
For example, 175928847299117063 is Sat, Apr 30, 2016, 11:18:25 AM UTC, which is 2016-04-30T11:18:25.796Z in ISO 8601 and 1462015105 in Unix seconds.
Top 42 bits read as milliseconds since the Discord epoch (2015-01-01). As a Twitter/X snowflake it would be 2012-03-03T13:01:20.453Z.
Detected: Discord snowflake ID/t/175928847299117063
Your timezone
UTC · GMT+00:00 · UTC
Sat, Apr 30, 2016, 11:18:25.796 AM
Common formats
UTC
Sat, Apr 30, 2016, 11:18:25.796 AM
ISO 8601
2016-04-30T11:18:25.796Z
Unix (seconds)
1462015105
Unix (millis)
1462015105796
Relative
…
Every Discord ID (user, message, channel, or server) is a snowflake: a 64-bit number whose top 42 bits are a timestamp in milliseconds since January 1, 2015. Paste one below to see exactly when it was created, in your timezone and UTC. Twitter/X uses the same scheme with a 2010 epoch, and the result shows that reading too.
Do it with the API
curl https://parsetime.dev/api/t/175928847299117063?format=discord-snowflakeThe same conversion as JSON: no key, no signup, permissive CORS. Try this call or read the API docs.
Common questions
- How do I get a timestamp out of a Discord snowflake?
- Shift the ID right by 22 bits and add the Discord epoch, 1420070400000 (January 1, 2015 in Unix milliseconds). Or paste the ID above and read the result. The conversion runs in your browser.
- Where do I find a snowflake ID in Discord?
- Enable Developer Mode in Settings → Advanced, then right-click any user, message, channel, or server and choose “Copy ID”. The long number you get is the snowflake.
- Does this work for Twitter/X snowflakes?
- Yes. Tweet and account IDs use the same layout with an epoch of November 4, 2010. The result above shows the Twitter reading alongside the Discord one, and the API accepts ?format=twitter-snowflake to force it.
- Can I convert a snowflake with the API?
- Yes: GET /api/t/<snowflake>?format=discord-snowflake returns the decoded time as JSON, with no key or signup. See the API docs for details.