Free publishing tool
Discord timestamp generator
Pick a time, copy the code, paste it into a message. Discord shows it to each reader in their own local time, which is the whole point over typing “9pm EST” and hoping.
Unix seconds
Pick a time above
Short time<t:UNIX:t>
Pick a time above. Hours and minutes.
Long time<t:UNIX:T>
Pick a time above. Hours, minutes and seconds.
Short date<t:UNIX:d>
Pick a time above. Numeric date.
Long date<t:UNIX:D>
Pick a time above. Date with the month spelled out.
Short date and time<t:UNIX:f>
Pick a time above. The default: a tag with no style letter renders exactly like this.
Long date and time<t:UNIX:F>
Pick a time above. Adds the weekday.
Relative<t:UNIX:R>
Pick a time above. Counts down or up from now, and keeps updating inside Discord.
Everyone sees their own timezone
The code holds one instant in UTC. Discord renders it in each reader's local time and language, so a raid, a stream or a deadline lands at the right hour for everyone without anyone converting from "9pm EST". The preview column shows your rendering only; a reader in another zone sees the same code as a different time.
Timestamps work in messages, embeds and bios on desktop and mobile. They do not render inside code blocks, so paste the tag as plain text. The relative style is recalculated live by the Discord client; the preview here refreshes every 30 seconds.
How the code works
A Discord timestamp is a Unix time wrapped in angle brackets: the number of seconds since 1 January 1970, UTC, followed by a letter that picks the display style. The number describes one instant. Each Discord client turns that instant into local time using the device's own timezone and language settings, so a member in Berlin and a member in Denver read the same code as two different clock times, and both are right.
This is the difference between a timestamp and a written time. “Community call at 6pm” is only correct in one timezone and silently wrong in every other; the timestamp is correct in all of them, and the relative style keeps counting down without anyone editing the message.
The seven styles
Leaving the style letter off is the same as choosing f. The relative style is the one to use for anything with a deadline, because it stays correct after the moment has passed: it reads “2 days ago” rather than a date the reader has to compare against today.
| Style | Code | Renders as |
|---|---|---|
| Short time | <t:1789671600:t> | 7:00 PM |
| Long time | <t:1789671600:T> | 7:00:00 PM |
| Short date | <t:1789671600:d> | 09/17/2026 |
| Long date | <t:1789671600:D> | September 17, 2026 |
| Short date and time (the default) | <t:1789671600:f> | September 17, 2026 7:00 PM |
| Long date and time | <t:1789671600:F> | Thursday, September 17, 2026 7:00 PM |
| Relative | <t:1789671600:R> | in 3 hours |
Where it breaks
- Timestamps render in messages, embeds and the About Me section of a profile. They do not render inside a code block, in a channel name or in a channel topic, where you will see the raw code.
- The preview on this page shows how the code renders for you. Other members see their own zone and format, which is the feature, not a bug to report.
- A bot or webhook payload wants the Unix number, not the angle-bracket code. Copy the raw seconds from the row at the top.
- Every Discord ID (a message, a user, a channel) encodes the moment it was created. The decode tab reads that, which is how you recover the exact time of a message without asking anyone.