Discord Timestamp Generator

Continue in the tool

More pages for this tool

convert unix to discord timestamp

Convert Unix, ISO and milliseconds to a Discord timestamp

In the generator, switch the mode to Unix and paste the value, or keep Date and time and use an ISO date in the Batch tab. The tool detects milliseconds, drops fractions and shows the result's UTC so you can check it before copying.

Where the number comes from and the most common mistakes

Unix time counts the seconds since January 1, 1970, 00:00:00 UTC, with no zone and no daylight saving. Discord expects exactly that in whole seconds. To get the current value, use Math.floor(Date.now() / 1000) in JavaScript, int(time.time()) in Python or date +%s in a Linux terminal. Each language has a different default unit, and that is the reason for the most frequent mistake: Date.now() in JavaScript returns milliseconds, with 13 digits in 2026, and pasting that number straight into the tag points to a very distant year.
An ISO date with an offset already defines the instant unambiguously: 2026-10-23T20:00:00-03:00 is the same moment as 2026-10-23T23:00:00Z and as Unix 1792796400. Without the offset, the date is just wall-clock time and depends on the zone. In the generator, a date without offset applies in the chosen event zone, and with an offset or Z the chosen zone is ignored. The extremes deserve attention too: 2147483648 is January 19, 2038 at 03:14:08 UTC, the point where signed 32-bit integers overflow, and the tool accepts dates up to the year 9999.
Fractions of a second do not exist in the tag. A value like 1618953630.9 is truncated to 1618953630, and so is a millisecond value like 1618953630900, because Discord works in whole seconds. Dates before 1970 would give negative Unix, and the tool does not accept them. After pasting the value, check the UTC shown at the top of the result: if the year or the hour look strange, the problem is almost always the unit or the zone, not the tag.

Checked examples

Unix in seconds

Input: 1618953630
Expected output: <t:1618953630:F>

2021-04-20 at 21:20:30 UTC.

Same value in milliseconds

Input: 1618953630000
Expected output: <t:1618953630:F>

Detected as milliseconds and divided by 1000.

ISO date with offset

Input: 2026-10-23T20:00:00-03:00
Expected output: <t:1792796400:F>

It is the same instant as 2026-10-23T23:00:00Z.

One billion seconds

Input: 1000000000
Expected output: <t:1000000000:F>

2001-09-09 at 01:46:40 UTC.

Signed 32-bit limit

Input: 2147483648
Expected output: <t:2147483648:F>

2038-01-19 at 03:14:08 UTC.

A recent round value

Input: 1700000000
Expected output: <t:1700000000:F>

2023-11-14 at 22:13:20 UTC.

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 know if my number is in seconds or milliseconds?

Count the digits. Between 2001 and 2286, a Unix value in seconds has 10 digits and in milliseconds has 13. In 2026 the value in seconds sits around 1.77 to 1.80 billion. The generator treats anything from 100 billion up as milliseconds and warns when it converts.

Why does the tag show a different time from what I calculated?

Because the tag is shown in the reader's zone. If you computed the Unix value from wall-clock time, confirm which zone it was in. The UTC shown by the generator is the neutral reference to compare against.

Can I generate hundreds of tags at once?

The Batch tab takes up to 200 lines at a time, each in Unix, ISO, dd/mm/yyyy or a relative delay, and copies all tags or a table with the input beside it.

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

Where the number comes from and the most common mistakes

Unix time counts the seconds since January 1, 1970, 00:00:00 UTC, with no zone and no daylight saving. Discord expects exactly that in whole seconds. To get the current value, use Math.floor(Date.now() / 1000) in JavaScript, int(time.time()) in Python or date +%s in a Linux terminal. Each language has a different default unit, and that is the reason for the most frequent mistake: Date.now() in JavaScript returns milliseconds, with 13 digits in 2026, and pasting that number straight into the tag points to a very distant year.

An ISO date with an offset already defines the instant unambiguously: 2026-10-23T20:00:00-03:00 is the same moment as 2026-10-23T23:00:00Z and as Unix 1792796400. Without the offset, the date is just wall-clock time and depends on the zone. In the generator, a date without offset applies in the chosen event zone, and with an offset or Z the chosen zone is ignored. The extremes deserve attention too: 2147483648 is January 19, 2038 at 03:14:08 UTC, the point where signed 32-bit integers overflow, and the tool accepts dates up to the year 9999.

Fractions of a second do not exist in the tag. A value like 1618953630.9 is truncated to 1618953630, and so is a millisecond value like 1618953630900, because Discord works in whole seconds. Dates before 1970 would give negative Unix, and the tool does not accept them. After pasting the value, check the UTC shown at the top of the result: if the year or the hour look strange, the problem is almost always the unit or the zone, not the tag.

Checked examples

Unix in seconds

Input: 1618953630
Expected output: <t:1618953630:F>

2021-04-20 at 21:20:30 UTC.

Same value in milliseconds

Input: 1618953630000
Expected output: <t:1618953630:F>

Detected as milliseconds and divided by 1000.

ISO date with offset

Input: 2026-10-23T20:00:00-03:00
Expected output: <t:1792796400:F>

It is the same instant as 2026-10-23T23:00:00Z.

One billion seconds

Input: 1000000000
Expected output: <t:1000000000:F>

2001-09-09 at 01:46:40 UTC.

Signed 32-bit limit

Input: 2147483648
Expected output: <t:2147483648:F>

2038-01-19 at 03:14:08 UTC.

A recent round value

Input: 1700000000
Expected output: <t:1700000000:F>

2023-11-14 at 22:13:20 UTC.

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 know if my number is in seconds or milliseconds?

Why does the tag show a different time from what I calculated?

Can I generate hundreds of tags at once?

The Batch tab takes up to 200 lines at a time, each in Unix, ISO, dd/mm/yyyy or a relative delay, and copies all tags or a table with the input beside it.

Discord Timestamp Generator

Continue in the tool

More pages for this tool

Convert Unix, ISO and milliseconds to a Discord timestamp

Where the number comes from and the most common mistakes

Checked examples

Unix in seconds

Same value in milliseconds

ISO date with offset

One billion seconds

Signed 32-bit limit

A recent round value

Full tool FAQ

Frequently asked questions

How do I know if my number is in seconds or milliseconds?

Why does the tag show a different time from what I calculated?

Can I generate hundreds of tags at once?

Next steps

Discord Timestamp Generator

Date to ID

Continue in the tool

More pages for this tool

Convert Unix, ISO and milliseconds to a Discord timestamp

Where the number comes from and the most common mistakes

Checked examples

Unix in seconds

Same value in milliseconds

ISO date with offset

One billion seconds

Signed 32-bit limit

A recent round value

Full tool FAQ

Frequently asked questions

How do I know if my number is in seconds or milliseconds?

Why does the tag show a different time from what I calculated?

Can I generate hundreds of tags at once?

Next steps

Date to ID