Discord Timestamp Generator

The Discord Timestamp Generator turns any date, time and timezone into a dynamic Discord timestamp — a short code such as <t:1735689600:F> that Discord replaces with a formatted date in each reader's own timezone and language. Post one code and a member in Los Angeles, one in Berlin and one in Tokyo all see the correct local time, with no "that's 3 PM EST, so 9 PM CET" maths in the channel.

What Is a Discord Timestamp?

A Discord timestamp is built from a Unix epoch second — the number of seconds since 1 January 1970 at 00:00 UTC. Because that number describes one fixed instant on the planet, Discord's client can safely render it however the reader's device is configured. The syntax is:

<t:UNIX_TIMESTAMP:STYLE> — for example <t:1735689600:F> renders as a full weekday, date and time.

The style letter is optional. <t:1735689600> behaves exactly like the :f style.

Discord Timestamp Formats

There are seven styles. The examples below use the timestamp 1735689600, which is 1 January 2025 at 00:00 UTC, rendered for a reader in UTC.

How to Use This Generator

1. Pick your timezone: choose the zone your event is scheduled in, or press Use mine to detect it. This is the step people skip, and it is the reason most timestamps come out wrong.
2. Set the date and time: type them in, or click a quick example such as In 1 hour or Next Friday 8 PM.
3. Watch the live preview: the mock Discord message updates as you type and the relative style keeps counting, so you can see the exact wording before you post it.
4. Copy the format you need: press Copy on any row, or press Generate Timestamp Report for the full breakdown with a countdown, the world clock strip and a copy-all block.
5. Paste it into Discord: the code turns into a formatted date the moment the message is sent.

Which Format Should You Use?

Where Discord Timestamps Work

Timestamps render in messages, replies, threads, forum posts, bot embed descriptions and field values, and scheduled event descriptions. They do not render in channel names, channel topics, server or member nicknames, custom status text, poll questions, or button labels — in those places the raw code stays visible as plain text.

Common Mistakes

• Generating the epoch in the wrong timezone. A Unix timestamp is an absolute instant, so "8 PM" means nothing until you say 8 PM where. Always set the timezone first.
• Forgetting daylight saving. The UTC offset of most European and North American zones changes twice a year, so an event three weeks out may not have the offset you have today. Choosing the IANA zone rather than a fixed offset handles this automatically.
• Pasting a millisecond timestamp. JavaScript's Date.now() returns milliseconds, a 13-digit number. Discord expects seconds; a 13-digit value lands tens of thousands of years in the future.
• Using a capital letter by accident. The style letters are case-sensitive: :d and :D are two different formats, and :r is not valid at all.
• Escaping the code by wrapping it in a code block. Inside backticks the timestamp stays literal text and never renders.

Frequently Asked Questions

What is a Discord timestamp?

A Discord timestamp is a short markdown code built from a Unix epoch second, written as t:1735689600:F between angle brackets. When you post it, Discord replaces the code with a formatted date and time rendered in each reader's own timezone and language, so nobody has to convert time zones by hand.

How do I make a Discord timestamp?

Convert your date and time into a Unix timestamp, then wrap it in the timestamp syntax with a style letter, for example t:1735689600:F. This generator does the conversion for you: pick a timezone, set the date and time, then copy the format you want.

What are the Discord timestamp formats?

There are seven styles. t is short time, T is long time with seconds, d is a short numeric date, D is a long date with the month name, f is short date and time, F is long date and time including the weekday, and R is a relative time such as in 3 hours. Leaving the style off is the same as f.

Why does my Discord timestamp show the wrong time?

Almost always because the epoch number was generated in the wrong timezone. A Unix timestamp is a fixed instant in UTC, so entering 8 PM without telling the converter which timezone that 8 PM belongs to shifts the result by your offset. Select the correct timezone before you copy, and remember that daylight saving changes the offset for part of the year.

Do Discord timestamps work everywhere?

They work in normal messages, replies, threads, forum posts, embed descriptions and field values sent by bots, and scheduled event descriptions. They do not render in channel names, channel topics, nicknames, custom status text, poll questions or button labels, where they stay as plain text.

Can I edit a Discord timestamp after posting?

Yes. The code is ordinary message text, so editing the message and changing the epoch number updates the displayed time for everyone. Relative timestamps update on their own and need no edit, which makes the R style the best choice for countdowns to an event.

What is the Unix timestamp Discord uses?

Discord uses Unix time in whole seconds, counted from 1 January 1970 at 00:00 UTC. If your source gives milliseconds, which is what JavaScript Date.now returns, divide by 1000 and drop the decimals before pasting the number into a timestamp code.

Additional Resources

• Unix Time - Wikipedia
• IANA Time Zone Database - Wikipedia
• Daylight Saving Time - Wikipedia