Discord Timestamp Generator

Result
Next

Discord lets you embed dynamic timestamps in messages using the syntax <t:UNIX:STYLE>, where UNIX is a Unix epoch (seconds since 1 January 1970 UTC) and STYLE is a one-letter format flag. The client renders each tag in the viewer’s own time zone and locale, so a single message shows the right local time to everyone, anywhere. This generator converts a date, a time and a UTC offset into the correct epoch and prints all seven style variants, short time, long time, short date, long date, short and long date/time, and relative, ready to copy into chat, events or bot embeds.

How to generate a Discord timestamp

  1. 1

    Set the date and time

    Choose the calendar date and the clock time of your event or deadline.

  2. 2

    Pick the time zone

    Select the UTC offset your date and time are written in so the epoch is computed correctly.

  3. 3

    Copy a style

    Pick a primary style, then copy any of the seven <t:UNIX:STYLE> codes and paste it into Discord.

The Discord timestamp format

Discord timestamps use the markup <t:UNIX:STYLE>. UNIX is the number of whole seconds elapsed since the Unix epoch (1970-01-01 00:00:00 UTC); STYLE is an optional single letter. When STYLE is omitted Discord defaults to f (short date/time). The relative style is written <t:UNIX:R> and counts up or down from the present moment whenever the message is viewed.

Worked example

Say your community event starts on 2025-12-31 at 20:00 in UTC+01:00 (Central European Time). Subtract the one-hour offset to reach true UTC (19:00 UTC), which is epoch 1767207600. The tool produces:

<t:1767207600:F>  -> Wednesday, December 31, 2025 8:00 PM
<t:1767207600:R>  -> in 6 months

A reader in New York (UTC-05:00) sees the same F tag rendered as December 31, 2025 2:00 PM automatically, you never hardcode a zone.

The seven styles

Flag Name Example output
t Short time 8:00 PM
T Long time 8:00:00 PM
d Short date 12/31/2025
D Long date December 31, 2025
f Short date/time December 31, 2025 8:00 PM (default)
F Long date/time Wednesday, December 31, 2025 8:00 PM
R Relative in 6 months

Pitfalls

  • Wrong offset. The most common mistake is computing the epoch from local time without subtracting the UTC offset. Always confirm the offset matches the zone your date and time are written in, and remember daylight saving shifts it.
  • Milliseconds. Discord expects seconds, not milliseconds. A 13-digit number renders as a date thousands of years in the future.
  • Plain text fallback. If you mistype the angle brackets or the flag, Discord shows the literal <t:...> text instead of a formatted date.

Frequently Asked Questions

It is the count of whole seconds since 1 January 1970 at 00:00 UTC. Discord uses it as a zone-independent anchor and then renders it in each viewer’s local time zone and language.

That is the point. A <t:UNIX:STYLE> tag is converted to the local time of whoever reads it, so one message displays the correct local time for everyone without you editing anything.

When you write <t:UNIX> without a trailing flag, Discord defaults to the f style (short date and time), for example “December 31, 2025 8:00 PM”.

No. The date, time and time zone you pick are sent to our server only to compute the codes, and in the step-by-step flow they are carried in the page link between steps. They are not stored or shared with third parties.

Related Tools

Tool available in other languages