Discord Timestamp Generator
Turn a date and time into a Discord <t:…> timestamp tag that shows in each viewer's own time zone.
About this tool
Turn a date and time into a Discord timestamp tag like <t:1717416840:F>. When you paste one of these into a Discord message it renders in each reader's own time zone and language, and the relative styles ("in 3 hours", "2 days ago") update live. Pick the date and time, choose whether you mean your local time or UTC, and copy whichever of the seven formats you need. Everything is computed in your browser.
The underlying idea. Discord's message format supports <t:UNIX_TIMESTAMP:STYLE>, where the timestamp is the number of seconds since January 1, 1970 UTC (the same Unix time every computer uses internally) and the style letter picks how it's displayed. Because the tag stores one absolute moment in time rather than a pre-formatted string, Discord's client renders it in whatever time zone and locale each reader has configured — a 9pm EST event shows correctly as 2am the next day GMT for a reader in London, without either of you doing the time-zone math.
The seven display styles:
| Code | Style | Example |
|---|---|---|
t | Short time | 9:41 PM |
T | Long time | 9:41:30 PM |
d | Short date | 06/03/2024 |
D | Long date | June 3, 2024 |
f | Short date/time (the default with no style letter) | June 3, 2024 9:41 PM |
F | Long date/time | Monday, June 3, 2024 9:41 PM |
R | Relative | in 3 hours / 2 days ago |
Worked example. The Unix timestamp 1717416840 is June 3, 2024, 12:14 PM UTC. Wrapping it as <t:1717416840:F> renders "Monday, June 3, 2024 12:14 PM" for a UTC reader, and the exact equivalent local time for anyone else — the same tag, different displayed text per reader.
Local time vs. UTC. The "Interpret that as" selector matters because a date/time picker has no inherent time zone — 9:00 PM could mean 9:00 PM in your zone or 9:00 PM UTC, and those are different moments. Pick "My local time" for "I mean 9pm where I am right now," or "UTC" if you're working from a UTC-denominated schedule or another tool's UTC output.
Common uses: announcing an event, stream, or raid start time to a server spanning multiple time zones; a countdown that reads naturally ("starts in 2 hours") without a bot; timestamping a giveaway or vote deadline so "ends soon" is unambiguous no matter where a reader lives.
For the underlying Unix timestamp on its own (e.g. for an API or script), use the Unix timestamp converter; for a plain visual countdown outside Discord, the countdown timer.
Frequently asked questions
- Why use a timestamp tag instead of just typing the time?
- Because your server's members are in different time zones. The tag stores a single moment as a Unix timestamp and Discord displays it correctly for everyone, so nobody has to do the maths.
- What do the letters mean?
tshort time,Tlong time,dshort date,Dlong date,fshort date/time (the default),Fday of week + date/time,Rrelative.- Does it need the Discord API?
- No. The tag is just text built from a Unix timestamp. This tool generates it offline; Discord does the rendering when you send the message.
- Should I pick "My local time" or "UTC"?
- "My local time" if you're thinking "9pm where I am right now." Pick "UTC" only if the time you're entering is already expressed in UTC, such as from a server schedule or another tool's UTC output.
- Why does the relative style ("in 3 hours") keep changing?
- It's not a fixed string — Discord recalculates it live against the reader's current clock every time the message is viewed, which is exactly what makes it useful for something like a countdown that never goes stale.
- Can I use these tags outside Discord?
- No — the
<t:...:F>syntax is specific to Discord's own message renderer. Pasting it into another app or website will just show the literal text, not a formatted date. - Does the timestamp tag work in scheduled/slash command messages too?
- Yes — it's plain text, so it works anywhere Discord renders message content: regular messages, embeds, and bot-sent text alike.