Discord Timestamp Generator
Create dynamic <t:...>timestamps that show in every reader's own timezone. Pick a time, copy a format, paste into Discord — free, no signup.
| Style | Code | Shows as | |
|---|---|---|---|
| Short time | <t:...:t> | — | |
| Long time | <t:...:T> | — | |
| Short date | <t:...:d> | — | |
| Long date | <t:...:D> | — | |
| Short date/time (default) | <t:...:f> | — | |
| Long date/time | <t:...:F> | — | |
| Relative time | <t:...:R> | — |
How Discord Timestamps Work
A Discord timestamp is the text <t:UNIX:STYLE>, where UNIX is the number of seconds since January 1, 1970 (UTC) and STYLE is one letter choosing the display format. When you send it, Discord replaces the code with a formatted time in each reader's own timezone and locale — perfect for announcing events, deadlines, and countdowns in international servers. The Rstyle even updates live ("in 2 hours", "3 minutes ago").
Timestamps work in normal messages, embeds, and bot messages on desktop, web, and mobile. For the rest of Discord's formatting — bold, spoilers, code blocks, colored text — see the complete Discord Markdown cheat sheet.
Frequently Asked Questions
How do Discord timestamps work?
Discord timestamps use the format <t:UNIX:STYLE>, where UNIX is a Unix timestamp (seconds since January 1, 1970 UTC) and STYLE is a single letter that picks the display format. Discord renders the timestamp in each reader's own timezone and language automatically.
What timestamp formats does Discord support?
Seven styles: t (short time), T (long time), d (short date), D (long date), f (short date/time, the default), F (long date/time with weekday), and R (relative time like "in 2 hours" that updates live).
Do Discord timestamps adjust for timezones?
Yes — that is their main benefit. You enter the time once in your timezone, and every reader sees it converted to their own local timezone, so nobody has to do timezone math for events.
Why does my Discord timestamp show the wrong time?
The Unix timestamp is timezone-independent, so a wrong display usually means the timestamp was generated for the wrong local time, or your device clock/timezone setting is off. Regenerate the code with the correct local time selected.