Discord Timestamps: Every Format Code Explained
A Discord timestamp token like <t:1767225600:F> renders as a real date in every reader's own timezone and language — no more "8 PM EST / 1 AM UTC" tables in event posts. There are seven display styles, and the only input you need is a unix timestamp in seconds.
How Discord timestamps work
The token is <t:UNIX> or <t:UNIX:STYLE>, where UNIX is a count of seconds since 1970-01-01 UTC and STYLE is one of seven single-letter codes. Discord replaces the token at render time using the viewer's locale and timezone, so the same message reads correctly in Tokyo and Toronto. When you omit the style, Discord uses f (short date/time).
Timestamps work in normal chat, webhook content, embed text and Components V2 Text Displays. Inside a code block the token is shown literally — that is the standard way to show someone the syntax itself.
All seven timestamp styles
Examples below use 1767225600 (2026-01-01 00:00 UTC) as seen by an en-US reader in UTC. Every reader sees their own language and timezone.
| Style | Name | Example output |
|---|---|---|
| <t:1767225600:t> | Short time | 12:00 AM |
| <t:1767225600:T> | Long time | 12:00:00 AM |
| <t:1767225600:f> | Short date/time (default) | January 1, 2026 12:00 AM |
| <t:1767225600:F> | Long date/time | Thursday, January 1, 2026 12:00 AM |
| <t:1767225600:d> | Short date | 1/1/2026 |
| <t:1767225600:D> | Long date | January 1, 2026 |
| <t:1767225600:R> | Relative | “in 3 days” / “2 hours ago” — updates live |
Get the unix timestamp
DWEEB's picker previews every style with the same formatter its message preview uses, so the row you click is exactly what the channel will show.
- In DWEEB, use the clock button in the text toolbar: pick a date, time and style, preview each style live, and the token is inserted for you.
- Terminal: date +%s prints the current unix time.
- JavaScript: Math.floor(Date.now() / 1000).
- Python: int(time.time()).
A timestamp in a real webhook payload
{
"flags": 32768,
"components": [
{
"type": 10,
"content": "## Community game night\nStarts <t:1767225600:F> — that's <t:1767225600:R>."
}
]
}Common mistakes
| Symptom | Cause | Fix |
|---|---|---|
| A date in the year 57,000 | Milliseconds were pasted instead of seconds | Divide by 1000 and round down |
| The literal <t:…> text shows in chat | The token is inside a code block or inline code | Move it out of the code span |
| Time is wrong for some readers | A written timezone was added next to the token | Let the token carry the time; drop the hardcoded zone |
| "2 years ago" in an evergreen post | Relative style ages with the message | Use an absolute style like F for rules and pinned posts |
Put the guide into practice
Open the exact workflow in DWEEB. Nothing posts until you review and confirm it.
Insert a timestamp with the visual picker →