Tool
Discord timestamp generator
A Discord timestamp renders in each reader's own timezone. Pick an instant, copy the markup, and everyone in the channel sees it in their local time — which is the entire reason the syntax exists.
Unix seconds —
| Style | Markup to copy | Renders as | Copy |
|---|---|---|---|
| t |
<t:0:t>
|
— | |
| T |
<t:0:T>
|
— | |
| d |
<t:0:d>
|
— | |
| D |
<t:0:D>
|
— | |
| f default |
<t:0:f>
|
— | |
| F |
<t:0:F>
|
— | |
| s |
<t:0:s>
|
— | |
| S |
<t:0:S>
|
— | |
| R |
<t:0:R>
|
— |
The syntax
A timestamp is written <t:UNIX:STYLE>, where UNIX is the instant in seconds since 1970 — not milliseconds, which is the single most common way to land four decades in the future. Leave the style off and Discord uses f.
Discord resolves the instant on each reader's client, so the same message reads 16:20 to one person and 09:20 to another. That is why nothing on this page promises what you will see: the examples in the table below are Discord's own, from its documentation.
| Style | Name | Discord's example | Written as |
|---|---|---|---|
| t | Short Time | 16:20 | <t:1618928400:t> |
| T | Medium Time | 16:20:30 | <t:1618928400:T> |
| d | Short Date | 20/04/2021 | <t:1618928400:d> |
| D | Long Date | April 20, 2021 | <t:1618928400:D> |
| f | Long Date, Short Time Used when no style is given | April 20, 2021 at 16:20 | <t:1618928400:f> |
| F | Full Date, Short Time | Tuesday, April 20, 2021 at 16:20 | <t:1618928400:F> |
| s | Short Date, Short Time | 20/04/2021, 16:20 | <t:1618928400:s> |
| S | Short Date, Medium Time | 20/04/2021, 16:20:30 | <t:1618928400:S> |
| R | Relative Time | 4 years ago | <t:1618928400:R> |
Transcribed from Discord's developer reference, retrieved 2026-08-30. The style table has grown before — s and S are newer than the rest, and several generators still on the first page of results do not offer them.
What people get wrong
- Milliseconds instead of seconds
- Most languages hand you milliseconds. Passing them straight through puts the date somewhere around the year 54000, and Discord renders it without complaint.
- Expecting a fixed time
- There is no style that pins a timestamp to one timezone. If a message must say a specific wall-clock time in a specific place, write that text yourself.
- Relative time in an edited message
- Style
Rcounts from the instant you encoded, not from when the message was posted or edited. It keeps counting forever. - Timestamps in an embed title
- The markup resolves in message content and embed descriptions and fields, but not everywhere an embed takes text. Test before shipping a bot that relies on it.