Discord Timestamp Generator

How to use it

1. Choose the date, the time and the time zone the event is planned in. "Use current time" fills in one hour from now.
2. Or paste a Unix timestamp (or a whole code like <t:1794684600:R>) into the Unix field to jump to that moment.
3. Check the preview next to each style. It shows the time as a reader in the selected zone would see it.
4. Click Copy on the style you want and paste the code into your Discord message. Send it and Discord renders the time.

How Discord timestamps work

A Discord timestamp is a short code you type into a message. Discord replaces it with a date or time. The code looks like this: <t:1794684600:F>.

It has three parts. t says "this is a timestamp". The long number is a Unix timestamp: the count of seconds since 1 January 1970, 00:00 UTC. The last letter is the style. You can leave the style out and Discord uses f, the long date with short time.

The useful part is what the reader sees. Discord's developer documentation says a timestamp is displayed in the user's own time zone and locale. You write one code, and each person sees it converted for them. That is why moderators use it for events: nobody has to ask "what time is that for me?"

Worked example: a game night on 14 November 2026

Say your community meets on Saturday, 14 November 2026, at 19:30 UTC. To get the Unix value, run this in a terminal with Bun installed:

bun -e 'console.log(Date.UTC(2026, 10, 14, 19, 30, 0) / 1000)'

Months start at 0 in JavaScript, so November is 10. The result is 1794684600. The generator above does the same calculation when you pick the date, the time and the zone.

Now post <t:1794684600:F>. Here is what three readers see:

One code, three different clocks, and even a different weekday in Tokyo. The exact wording depends on the reader's language and region, so a reader in Germany sees the text in German. The table shows English (US) format, the same one the previews in the tool use.

All nine formats

The table below uses the same moment as above, as seen from New York. Style R depends on the current time, so it is shown as a pattern.

The official reference lists nine styles: t, T, d, D, f, F, s, S and R. If you leave the style out, Discord uses f. Some older guides list only seven styles, so check the table below if a format is missing from one.

Which style should you use?

• Event announcements: use F for the full date and R next to it. Example: "Starts <t:1794684600:F> (<t:1794684600:R>)".
• Countdowns: R alone. It shows "in 3 hours" and keeps counting as the message sits in the channel.
• Giveaways: put the end time in f or F, and add R so people see how long is left.
• Schedules and logs: s or S gives a compact date and time on one line.
• Daily reminders: t for just the clock time.

Using timestamps in a real announcement

Here is a full message a moderator might post. Copy it, swap the number, and send.

Movie night is on <t:1794684600:F>. That is <t:1794684600:R>. Doors open at <t:1794684600:t>.

Three codes, one number. Readers get the weekday and date, a live countdown and the plain clock time, all in their own zone. If you change the event time, you only need to replace the number in each code.

For a recurring event, keep a note with the Unix value for the next date. Add 604800 seconds (7 days) to get the same time next week. Across a daylight saving change, check the result in the generator, because the local clock time can shift by an hour.

Common mistakes

Milliseconds instead of seconds

JavaScript's Date.now() returns milliseconds. A current value has 13 digits, such as 1794684600000. Discord expects seconds, which is 10 digits today. Paste 13 digits and the date lands tens of thousands of years in the future. Divide by 1000. The Unix field in this tool accepts both and converts for you.

A missing colon or bracket

The code needs both angle brackets and a colon after t. <t1794684600> or <t:1794684600:F shows up as plain text. Copy the code with the button instead of typing it.

Wrong time zone when you enter the time

The Unix number is always in UTC, so the zone only matters when you convert from a clock time. If you plan an event for 19:30 and your computer is set to a different zone than your community, the number will be off. Pick the zone of the event in the Time zone list.

Daylight saving time

A Unix timestamp is one fixed moment. It does not shift when clocks change. This helps readers, since Discord converts using their local rules. It can hurt you for a weekly event: "19:30 Berlin time every Saturday" is a different Unix value after the clocks change. Generate a fresh code for each date. The generator handles the offset for the date you pick.

Text that does not render inside code

Inside backticks or a code block, Discord shows the code as typed. Keep timestamps in normal text.

How to get a Unix timestamp without the tool

• Linux or macOS terminal: date +%s for now, or date -d "2026-11-14 19:30 UTC" +%s on GNU systems.
• JavaScript: Math.floor(Date.now() / 1000) for now, or Date.UTC(2026, 10, 14, 19, 30) / 1000 for a date.
• Reverse check: paste the number into the Unix field here and read the date back.

Sources

• Discord Developer Documentation, API Reference (message formatting, timestamp styles): syntax <t:TIMESTAMP:STYLE>, the nine styles, default style f, display in the user's time zone and locale.
• Discord Support: Markdown Text 101: general formatting reference for messages.

Checked October 2026.