Times are entered in your timezone; Discord shows every reader the same moment in their timezone. The previews below use your locale, so they match what you will see in Discord.
"Event at 8 PM EST" forces every reader to convert timezones, and half of them get it wrong. A Discord timestamp is stored as a Unix time (seconds since 1 January 1970 UTC) and rendered by each client, so the same code shows "20:00" in Berlin and "2:00 PM" in New York — correct for everyone, automatically. The relative style even counts down live, which is why it is the standard way to announce game nights, wipes, maintenance windows and giveaways.
The code is <t:UNIX:STYLE> — for example <t:1755024000:F>. The unix number is the moment itself; the final letter picks one of the seven display styles listed above. Omit the letter entirely and Discord falls back to the f style.
<t:1755024000:R> that Discord renders as a date or time in each reader's own timezone and language — one user sees "in 2 hours", another sees the same moment as "vor 2 Stunden".Pick a date and time above, then copy the code for the style you want and paste it into any Discord message. It works in normal chat, embeds and channel descriptions, on desktop and mobile.
Seven styles: short and long time (t, T), short and long date (d, D), short and long date-time (f, F), and relative (R), which keeps updating — "in 3 minutes", "2 hours ago".
<t:unix:style> code into a normal message and it will render for everyone.