Loading
Pick a date and time, then copy the Discord markdown code. Timestamps display in each user's local timezone automatically.
| Style | Syntax | Preview | Copy |
|---|---|---|---|
| Short time | <t:1785747480:t> | 8:58 AM | |
| Long time | <t:1785747480:T> | 8:58:00 AM | |
| Short date | <t:1785747480:d> | 08/03/2026 | |
| Long date | <t:1785747480:D> | August 3, 2026 | |
| Short date/time | <t:1785747480:f> | August 3, 2026 at 8:58 AM | |
| Long date/time | <t:1785747480:F> | Monday, August 3, 2026 at 8:58 AM | |
| Relative | <t:1785747480:R> | a few seconds ago |
Practical use cases for dynamic time codes.
The most common use is coordinating events across time zones. If your gaming group spans multiple countries, posting a timestamp means everyone sees the event time in their local clock. No more "wait, is that EST or PST?" confusion.
Server admins use timestamps for scheduled maintenance windows, tournament start times, and deadline announcements. The relative format (R) is particularly useful for countdowns: "Event starts <t:1722700200:R>" will show "in 3 hours" and count down automatically.
Content creators and moderators also use timestamps to document when rules were last updated, when events occurred, or when temporary channels will close. The long date format (F) works well for permanent records.
The @time shortcut vs. manual syntax.
Discord added a native "@time" feature that lets you type natural language time references directly in the message box. Typing "@time tomorrow at 3pm" generates a timestamp inline.
The manual syntax (<t:UNIX:FORMAT>) still has advantages: you get full control over the display format, you can prepare timestamps in advance, and you can use exact times down to the second. The generator above handles the Unix conversion so you don't need to do the math yourself.
Common questions about Discord time codes.
More gaming and Discord utilities.