Explore all nine styles
Change the Unix seconds to compare code, browser-local preview, and purpose.
| Style | Discord code | Your browser preview |
|---|
Read the syntax
The full pattern is <t:TIMESTAMP:STYLE>. Discord expects the timestamp in seconds and renders it in the viewer’s timezone and locale Discord docs.
If you omit the style, Discord uses f, the long date with short time.
The nine current styles
| Code | Meaning | Best use |
|---|---|---|
t | Short time | Same-day reminder |
T | Time with seconds | Precise starts |
d | Short date | Compact calendar |
D | Long date | Readable date |
f | Long date + short time | Default event line |
F | Weekday + date + time | Formal announcement |
s | Short date + short time | Dense schedules |
S | Short date + time with seconds | Dense precise logs |
R | Relative time | Countdown or age |
Style and locale control different things
The style controls the amount of information. The viewer’s locale controls wording, date order, and often 12- or 24-hour presentation. Browser formatting follows the same split: Intl.DateTimeFormat accepts both locale and named timezone options MDN.
Choose T to include seconds. Do not choose it to force a 24-hour clock.
Why some generators show seven formats
Several established tools still expose the older seven-style set. The current Discord table also includes s and S. Those two styles matter when a schedule or log needs a compact numeric date and time.
Bottom line
Use F for a self-contained announcement, f for a compact event, R for urgency, and s or S when space matters.
Open the full Discord Time Converter
Sources and test pages
- Discord Developer Documentation — Message Formatting Primary reference for timestamp syntax, seconds, local rendering, and the nine current styles.
- MDN — Intl.DateTimeFormat Reference for locale-sensitive date formatting and named time zones in browsers.