Discord timestamps: show times in everyone’s own time zone
How the <t:…> timestamp code works, all seven formats with examples, and how to make one in seconds.
Updated , 4 min read
If your server spans time zones, writing “8pm” is a guessing game. Discord timestamps solve it: you write one code and every reader sees the time converted to their own zone and language.
The syntax
A timestamp looks like <t:1790812800:F>. The number is a Unix timestamp: seconds since January 1, 1970, UTC. The letter after it is the style.
The seven styles
| Code | Style | Example |
|---|---|---|
:t | Short time | 8:00 PM |
:T | Long time | 8:00:00 PM |
:d | Short date | 10/02/2026 |
:D | Long date | October 2, 2026 |
:f | Date and time (default) | October 2, 2026 8:00 PM |
:F | Full date and time | Friday, October 2, 2026 8:00 PM |
:R | Relative | in 2 days |
If you leave out the style, Discord uses f.
Make one
The quickest way is the timestamp generator: pick a date and time and copy the style you want. It uses your time zone, so you don’t have to convert anything.
Tips
- For events, combine full and relative:
<t:…:F> (<t:…:R>)shows the date and a live countdown. - Relative timestamps update live, so they’re great in pinned messages.
- Every Discord ID also contains a timestamp. The snowflake decoder reads it.
Questions
Can I use timestamps in channel names?
No. They work in messages, embeds, and channel topics, but not in channel or role names.
Do timestamps work in bot messages?
Yes. Bots use the same <t:unix:style> syntax in message content and embed fields.