Discord timestamp generator

Pick a date, time and time zone and get codes you can paste into Discord messages. Each reader sees the time in their own time zone. Also converts Unix time and reads codes back.

How timestamp codes work

Discord messages can contain a code such as <t:1794702600:F>. Instead of showing the code, Discord shows the date and time in each reader's own time zone and language. One message, and everyone sees the right local time: no "7:30 PM Eastern, that's 00:30 in London…" in event announcements.

The number is Unix time: the seconds since 1 January 1970 at 00:00 UTC. The letter after it picks the style. This tool turns a date, time and time zone into that number and gives you a code for each style, ready to paste.

Code endingStyleLooks roughly like (US English)
:tShort time7:30 PM
:TLong time7:30:00 PM
:dShort date11/14/2026
:DLong dateNovember 14, 2026
:f or noneShort date and time (the default)November 14, 2026 7:30 PM
:FLong date and timeSaturday, November 14, 2026 7:30 PM
:RRelativein 3 days / 2 hours ago

The exact wording depends on each reader's language settings. The previews on this page use your browser's own date formatting, so they are close to what you will see but may not match character for character. These are the seven long-standing styles; check Discord's own help if you see a newer one mentioned.

Worked example

You are hosting a game night on Saturday 14 November 2026 at 7:30 PM in New York.

  • New York is on Eastern Standard Time (UTC−5) by then, so that is 00:30 UTC on Sunday 15 November.
  • From 1 January 2026 (Unix time 1,767,225,600) to 15 November is 318 days, or 27,475,200 seconds, plus 30 minutes (1,800 seconds): 1794702600.
  • Paste <t:1794702600:F> into your message. A reader in New York sees Saturday 14 November at 7:30 PM, a reader in London sees Sunday 15 November at 00:30, and a reader in Dubai sees Sunday 15 November at 04:30.
  • Add <t:1794702600:R> for a countdown such as "in 3 days" that updates by itself.

Tips

  • Pick the time zone the event is in, not necessarily yours. "Use my time zone" fills in the one your browser reports.
  • Daylight saving is handled. The tool uses your browser's time zone database, so a date after the clocks change gets the right offset. If you pick a time that is skipped when clocks go forward, it is moved forward by the gap.
  • Combine styles: "Starts <t:…:F> (<t:…:R>)" gives both the date and a countdown.
  • Codes need to be typed exactly, with the angle brackets and no spaces. If a code shows as plain text, check for a missing bracket or a wrong letter (the letters are case-sensitive).

FAQ

How do I make a timestamp that shows in everyone's time zone?

Choose the date, time and time zone of your event, then copy one of the codes, such as <t:1794702600:F>, into your message. Each reader sees it converted to their own local time.

What does the R style do?

It shows the time relative to now, such as "in 2 hours" or "3 days ago", and keeps updating as time passes.

What is Unix time?

The number of seconds since 00:00 UTC on 1 January 1970, not counting leap seconds. It is the same everywhere in the world at a given moment, which is why it works for every time zone. Many apps and logs use it, often in milliseconds (13 digits); the converter tab reads both.

Why does the preview differ slightly from what I see in the app?

The app formats the code itself, using your language settings. The preview here uses your browser's formatting, which can differ in small details such as commas, "at", or 12 and 24-hour clocks.

Can I use this for dates before 1970?

No. This tool only makes codes for 1970 and later.

Is anything I type sent anywhere?

No. All conversions run in your browser using its built-in time zone data.