Discord Timestamp Generator

Continue in the tool

More pages for this tool

discord id to creation date

Discord ID to date: how to read the snowflake

Open the ID (snowflake) tab of the generator and paste the ID or the message link. It returns the date in UTC and in your zone, the internal fields of the number and a ready tag. Below, the math behind the result, which you can also do by hand.

What a snowflake stores and how to extract the date

Almost every Discord identifier (user, server, channel, message, role) is a snowflake: a 64-bit integer created at the moment the object is born. The top 42 bits hold the milliseconds since the Discord epoch, 1420070400000, which is the start of 2015. The remaining 22 bits split into 5 of worker, 5 of process and 12 of increment, which tell apart IDs generated in the same millisecond. Because time takes the most significant part of the number, bigger IDs are newer.
To extract the date, shift the ID 22 bits to the right and add the epoch: (ID >> 22) + 1420070400000 gives Unix milliseconds. With ID 175928847299117063, from the Discord documentation, the shift gives 41944705796, and adding the epoch yields 1462015105796, or April 30, 2016, 11:18:25 UTC. The other fields come from masks: worker is (ID & 0x3E0000) >> 17, process is (ID & 0x1F000) >> 12 and increment is ID & 0xFFF, which here are 1, 0 and 7. In JavaScript, use BigInt, because 64 bits exceed the precision limit of the Number type.
A message link, like discord.com/channels/server/channel/message, carries three snowflakes, so it yields three dates: the server's, the channel's and the message's. Private conversation links replace the server with @me. The reverse path also exists: (milliseconds - 1420070400000) << 22 gives the smallest possible ID for an instant, useful in pagination and time-based API queries. Watch out for a very small ID: if the time field is zero, the date falls on 2015-01-01, and the number is almost never a real ID.

Checked examples

ID from the Discord documentation

Input: 175928847299117063
Expected output: 2016-04-30 11:18:25.796 UTC

Worker 1, process 0, increment 7.

The math step by step

Input: 175928847299117063 >> 22
Expected output: 41944705796 + 1420070400000 = 1462015105796

1462015105796 ms since 1970 is the date above.

Smallest ID of January 1, 2026 (UTC)

Input: 2026-01-01 00:00:00 UTC
Expected output: 1456074443980800000

(1767225600000 - 1420070400000) << 22.

Smallest ID of 2023-11-14 22:13:20 UTC

Input: Unix 1700000000
Expected output: 1174109840998400000

Any ID greater than or equal to this is from 2023-11-14 22:13:20 UTC or later.

ID zero

Input: 0
Expected output: 2015-01-01 00:00:00 UTC

That is the Discord epoch itself.

Full tool FAQ

How do I make a timestamp in Discord?

Write '<t:SECONDS>' or '<t:SECONDS:STYLE>' in the message, with SECONDS as Unix time. For example '<t:1618953630:F>' shows the full date for 2021-04-20 21:20:30 UTC, adjusted to the reader's time zone. Pick the date, time and event zone here and copy the finished tag.

What are the Discord timestamp styles?

Unix in seconds or milliseconds?

Does the time change for each person?

How do I show a countdown?

Why does my timestamp show the wrong time?

What happens with daylight saving time?

How do I find out when an account, server or message was created?

How does the Discord snowflake work?

Is my data sent anywhere?

Frequently asked questions

How do I find a user or server ID?

In Discord, enable developer mode in the app settings and use the copy ID option in the context menu of the user, server, channel or message. The copied ID is the number to paste into the ID (snowflake) tab.

Is the ID date the account creation date?

For a user ID, yes: it is the moment the ID was generated, that is, the account creation. For a server, channel or message, it is the moment that object was created, not when anyone joined it.

Why not use Number in JavaScript?

A snowflake has up to 64 bits, and the Number type only represents exact integers up to 2^53. With Number, the last digits of the ID get corrupted and the date comes out wrong. The tool uses BigInt for the whole calculation.

Can two IDs have the same date?

Yes, if they were created in the same millisecond. The date is equal, and what tells the IDs apart are the worker, process and increment fields.

Next steps

Tag	How it shows	UTC	Actions
`<t:1618953630:F>`	Tuesday, April 20, 2021 at 9:20 PM	2021-04-20T21:20:30Z
`<t:1618953630:R>`	…	2021-04-20T21:20:30Z

Tag

How it shows

UTC

Actions

<t:1618953630:F>

Tuesday, April 20, 2021 at 9:20 PM

2021-04-20T21:20:30Z

<t:1618953630:R>

…

2021-04-20T21:20:30Z

What a snowflake stores and how to extract the date

Almost every Discord identifier (user, server, channel, message, role) is a snowflake: a 64-bit integer created at the moment the object is born. The top 42 bits hold the milliseconds since the Discord epoch, 1420070400000, which is the start of 2015. The remaining 22 bits split into 5 of worker, 5 of process and 12 of increment, which tell apart IDs generated in the same millisecond. Because time takes the most significant part of the number, bigger IDs are newer.

To extract the date, shift the ID 22 bits to the right and add the epoch: (ID >> 22) + 1420070400000 gives Unix milliseconds. With ID 175928847299117063, from the Discord documentation, the shift gives 41944705796, and adding the epoch yields 1462015105796, or April 30, 2016, 11:18:25 UTC. The other fields come from masks: worker is (ID & 0x3E0000) >> 17, process is (ID & 0x1F000) >> 12 and increment is ID & 0xFFF, which here are 1, 0 and 7. In JavaScript, use BigInt, because 64 bits exceed the precision limit of the Number type.

A message link, like discord.com/channels/server/channel/message, carries three snowflakes, so it yields three dates: the server's, the channel's and the message's. Private conversation links replace the server with @me. The reverse path also exists: (milliseconds - 1420070400000) << 22 gives the smallest possible ID for an instant, useful in pagination and time-based API queries. Watch out for a very small ID: if the time field is zero, the date falls on 2015-01-01, and the number is almost never a real ID.

Checked examples

ID from the Discord documentation

Input: 175928847299117063
Expected output: 2016-04-30 11:18:25.796 UTC

Worker 1, process 0, increment 7.

The math step by step

Input: 175928847299117063 >> 22
Expected output: 41944705796 + 1420070400000 = 1462015105796

1462015105796 ms since 1970 is the date above.

Smallest ID of January 1, 2026 (UTC)

Input: 2026-01-01 00:00:00 UTC
Expected output: 1456074443980800000

(1767225600000 - 1420070400000) << 22.

Smallest ID of 2023-11-14 22:13:20 UTC

Input: Unix 1700000000
Expected output: 1174109840998400000

Any ID greater than or equal to this is from 2023-11-14 22:13:20 UTC or later.

ID zero

Input: 0
Expected output: 2015-01-01 00:00:00 UTC

That is the Discord epoch itself.

Full tool FAQ

How do I make a timestamp in Discord?

What are the Discord timestamp styles?

Unix in seconds or milliseconds?

Does the time change for each person?

How do I show a countdown?

Why does my timestamp show the wrong time?

What happens with daylight saving time?

How do I find out when an account, server or message was created?

How does the Discord snowflake work?

Is my data sent anywhere?

Frequently asked questions

How do I find a user or server ID?

Is the ID date the account creation date?

For a user ID, yes: it is the moment the ID was generated, that is, the account creation. For a server, channel or message, it is the moment that object was created, not when anyone joined it.

Why not use Number in JavaScript?

Can two IDs have the same date?

Yes, if they were created in the same millisecond. The date is equal, and what tells the IDs apart are the worker, process and increment fields.

Discord Timestamp Generator

Continue in the tool

More pages for this tool

Discord ID to date: how to read the snowflake

What a snowflake stores and how to extract the date

Checked examples

ID from the Discord documentation

The math step by step

Smallest ID of January 1, 2026 (UTC)

Smallest ID of 2023-11-14 22:13:20 UTC

ID zero

Full tool FAQ

Frequently asked questions

How do I find a user or server ID?

Is the ID date the account creation date?

Why not use Number in JavaScript?

Can two IDs have the same date?

Next steps

Discord Timestamp Generator

Date to ID

Continue in the tool

More pages for this tool

Discord ID to date: how to read the snowflake

What a snowflake stores and how to extract the date

Checked examples

ID from the Discord documentation

The math step by step

Smallest ID of January 1, 2026 (UTC)

Smallest ID of 2023-11-14 22:13:20 UTC

ID zero

Full tool FAQ

Frequently asked questions

How do I find a user or server ID?

Is the ID date the account creation date?

Why not use Number in JavaScript?

Can two IDs have the same date?

Next steps

Date to ID