Discord Timestamp Generator

The syntax, exactly

A Discord timestamp is written as <t:UNIX:STYLE>. The angle brackets are required, there are no spaces anywhere inside, UNIX is a count of whole seconds since 1 January 1970 UTC, and STYLE is a single letter. If you leave the style off and post <t:1773477000>, Discord falls back to the f style.

The reason this is worth the trouble is that the number you post is an absolute point in time with no timezone attached. Discord converts it on each viewer's own client, so a reader in Perth and a reader in London see the same event written in their own local time without you doing any conversion or writing "8pm AEDT" and hoping.

A worked example

Say the event is Saturday 14 March 2026 at 7:30:00 pm, and your device clock is set to Sydney time, which is UTC+11 in March. Enter 2026-03-14 in the date field and 19:30:00 in the time field. The tool builds a date object in your local timezone, divides the millisecond value by 1000 and rounds down, and prints the result under the table:

Unix timestamp: 1773477000

That single number produces all seven tags:

• <t:1773477000:t> renders as 7:30 pm
• <t:1773477000:T> renders as 7:30:00 pm
• <t:1773477000:d> renders as 14/03/2026
• <t:1773477000:D> renders as 14 March 2026
• <t:1773477000:f> renders as 14 March 2026 7:30 pm
• <t:1773477000:F> renders as Saturday, 14 March 2026 7:30 pm
• <t:1773477000:R> renders as a live countdown, for example "in 3 days", recalculated whenever the message is looked at

Post that same message and someone reading it in Perth sees 4:30 pm, and someone reading it in London sees 8:30 am, all from the one number. The preview column on this page is the tool's own rendering of each style so you can compare them at a glance. Discord itself formats using the viewer's language and region setting, so the exact date order and the am/pm styling may differ slightly from the preview.

What each style letter is for

t and T give time only, with T adding seconds. Use them when the date is already obvious from context, such as a reminder posted on the day.

d and D give date only, short and long. D is the safer of the two for an international audience, because a numeric short date is ambiguous between day-first and month-first readers while a written-out month never is.

f and F give date and time together, with F adding the weekday. F is the best default for an announcement, since the weekday is the part people actually plan around.

R gives relative time and is the one people remember. It counts down before the event and counts up afterwards, which makes it excellent for deadlines and terrible for anything archival, because a message saying "2 years ago" tells a future reader nothing useful. Posting an F and an R next to each other gives you both.

Things that catch people out

• Milliseconds instead of seconds. Most programming languages and APIs hand you a 13-digit millisecond value. Discord wants the 10-digit second value. Paste the long one and your event lands tens of thousands of years in the future. If your number has 13 digits, drop the last three.
• Your timezone, not theirs. The fields above read your device's clock. If you are scheduling something for a server based elsewhere, enter the time as it would be on your own clock at that moment, not the local time at the destination.
• Daylight saving. The conversion uses your device's rules for the specific date you chose, not today's offset, so a date on the other side of a daylight saving change is handled correctly. If your device timezone is wrong, every timestamp you generate will be wrong by the same amount.
• Code blocks. Text inside backticks is displayed literally, so a timestamp wrapped in code formatting shows the raw tag instead of a date. That is also the trick for showing someone the syntax.
• Seconds you cannot see. The seconds you type are baked into the number even though only the T style displays them. For a countdown to a round minute, set seconds to 00.

Where this is worth the effort

Anywhere a group spans more than one timezone. Raid and scrim start times, a giveaway closing time, a stream going live, an application deadline, a meeting in a work server, a patch dropping. The same tag also works in messages sent by bots and inside embed titles, descriptions and field values, which is why bot developers reach for it constantly instead of formatting dates themselves.

A pattern worth stealing for event announcements: put the F style in the body so the full date is unambiguous, then put the R style at the end so anyone scrolling past sees how long they have left.

Related tools

If you already have a Unix timestamp and want to read it, or you need to go the other way from a timestamp back to a date, the Unix Timestamp Converter handles both directions and copes with millisecond values. For dressing up the surrounding message, Fancy Text Generator restyles headings in Discord message text, and Invisible Character is useful for spacing tricks in nicknames and embeds.

Questions people ask

Why does my timestamp show a date thousands of years away?

You have used a millisecond value where Discord expects seconds. A 13-digit number needs its last three digits removed to become the 10-digit value the tag takes.

Which timezone does the date and time field use?

Whatever your device is set to. The tool converts from your local clock to an absolute Unix second count, and Discord then converts back into each reader's own local time.

Why does the tool's preview look different from what Discord shows me?

The preview here is generated on this page with one fixed presentation. Discord formats the same instant according to the language and region configured in each viewer's client, so the ordering of day and month can differ. The underlying instant is identical.

Can I use these timestamps in bot messages and embeds?

Yes. The tag is rendered client-side by Discord, so it behaves the same in a message you type, a message a bot sends, and inside embed descriptions and fields.

Is there a style that does not change as time passes?

All six of the non-relative styles show a fixed date or time. Only R moves, because it is calculated against the moment of viewing. Use F rather than R for anything meant to be read months later.