🕐 Discord Timestamp Generator

What is the Discord Timestamp Generator?

A Discord timestamp is a small piece of markup written as t:UNIX:STYLE, wrapped in angle brackets, where UNIX is the number of seconds since the Unix epoch (1 January 1970, 00:00:00 UTC) and STYLE is a single letter that controls the format. Because the moment is stored as one absolute instant in UTC, Discord can render it correctly for everyone: a reader in Tokyo and a reader in New York see the same instant shown on their own local clock. That is far more reliable than typing an abbreviation like 8 PM EST by hand, which readers routinely misread or fail to convert. A Discord timestamp generator like this one removes the arithmetic entirely by computing the Unix seconds and formatting the code for you.

There are seven styles, and each is a single case sensitive letter. Lowercase t gives a short time such as 4:30 PM, and uppercase T adds seconds. Lowercase d gives a short numeric date, while uppercase D spells out the month. The default style f shows a short date and time together, and F produces the long, formal version that also includes the day of the week. The most popular style by far is R, the relative format, which renders phrases such as in 3 hours or 2 days ago and keeps counting on its own, so a countdown to an event stays accurate without anyone editing the message.

The markup behaves the same wherever it appears: a normal channel message, an embed field, a bot reply, a slash command response, or a scheduled server event description. To use it you copy the whole code including the angle brackets and paste it into the Discord message box. While you type, it appears as raw text, but the moment the message is sent Discord converts it into a styled, time zone aware timestamp. Hovering over any timestamp in the Discord client reveals the full long date, so readers can always confirm the exact moment.

A key detail people miss is that the value must be in seconds, not milliseconds. JavaScript, many APIs, and browser tools report time in milliseconds since the epoch, which is a 13 digit number. Discord expects the 10 digit seconds value, so you divide by 1000 and drop the decimals. Paste a millisecond value by mistake and Discord will happily render a date tens of thousands of years in the future. This tool always outputs seconds, so you can copy straight into chat without checking the digit count.

The relative R style deserves special attention because it is why timestamps are so useful for communities. Since Discord recomputes the phrase every time the message is viewed, a single posted message can read in 5 hours for one member and 20 minutes ago for another who opens it later, all from the same code. That makes it perfect for giveaways, raid or stream start times, application deadlines, and reminder bots that need one message to stay correct for an entire international server. Combine R with a static style like F in the same line to show both the exact time and the live countdown side by side.

Because the format is plain text markup, it works identically on desktop, the web app, and the mobile apps, and it never depends on the sender's time zone. The sender's local settings only matter at the point of choosing the moment; once the Unix seconds are baked into the code, the displayed result is driven entirely by each viewer's own device. That separation of the stored instant from the displayed format is the whole reason Discord timestamps exist, and it is what makes this Discord timestamp generator a reliable way to communicate time across a global audience.

When to use it

• Announcing an event, stream, giveaway, or raid start time so every member sees it in their own time zone with zero manual conversion.
• Posting a self-updating countdown with the relative (R) style, for example an application or submission deadline that always shows how long is left.
• Writing bot messages, embeds, or slash command replies that include a correctly localised date or time for an international user base.
• Documenting when something happened, such as a moderation action, a patch release, or an incident, with an unambiguous absolute time.
• Scheduling recurring community meetings or voice calls where members span many countries and daylight saving rules differ.
• Pairing a relative countdown with a full formal date on the same line so readers get both the live counter and the exact moment at a glance.

How to use the Discord Timestamp Generator

1. Pick the date and time you want using the date and time picker.
2. Leave the UTC box unticked to treat your input as your local time, or tick it to enter the time directly in UTC.
3. Read off the computed Unix timestamp in seconds and check the live preview for each of the seven styles.
4. Press Copy next to the style you want. The tool copies the full code including the angle brackets.
5. Paste the copied code into the Discord message box and send. It renders as a localised timestamp once the message posts.

Formula & method

Worked examples

The seven Discord timestamp styles and how each one renders

Seconds vs milliseconds, a common source of wrong dates

Common mistakes to avoid

• Using milliseconds instead of seconds. Discord expects the timestamp in seconds, not milliseconds. If you paste a 13 digit millisecond value, Discord shows a date tens of thousands of years in the future. Divide by 1000 and drop the decimals first, or just use this tool, which always outputs seconds.
• Leaving out the angle brackets. The code only renders when it is wrapped in angle brackets, in the exact form this tool copies. Pasting just the inner part means Discord treats it as plain text and shows the raw code instead of a formatted time.
• Mixing up local time and UTC. The Unix timestamp is always an absolute UTC instant. If you type a local time but compute it as if it were UTC, the result is off by your time zone offset. Use the UTC tick box to be explicit about which one you mean.
• Using the wrong case for the style letter. The style letters are case sensitive. Lowercase t and d are the short forms while uppercase T and D are the long forms, and f and F differ in the same way. Swapping the case changes the format, so copy the letter exactly.
• Expecting the preview to match every reader exactly. The preview here uses your own browser locale and time zone. Discord shows each reader the same instant in their own settings, so the exact wording and 12 or 24 hour format can differ from person to person.
• Trying to timestamp a time zone rather than a moment. A timestamp encodes one fixed instant, not a floating wall clock time. If you want 3 PM in every reader local zone, timestamps cannot do that. They always point to a single global moment that is then displayed locally.

Glossary

Unix timestamp

The number of seconds elapsed since the Unix epoch, 1 January 1970 at 00:00:00 UTC. Discord uses this to store an absolute instant.

Epoch

The fixed reference moment from which Unix time is counted: midnight UTC on 1 January 1970.

Style letter

The single character after the second colon (t, T, d, D, f, F, or R) that tells Discord how to format the date and time. It is case sensitive.

Relative timestamp

The R style, which renders phrases like in 2 hours or 3 days ago and keeps updating on its own each time the message is viewed.

UTC

Coordinated Universal Time, the global reference time zone with no daylight saving, used as the basis for Unix timestamps.

Seconds vs milliseconds

Discord needs the 10 digit seconds value. A 13 digit millisecond value must be divided by 1000, otherwise the date is thrown far into the future.

Angle brackets

The less-than and greater-than characters that must wrap the whole code. Without them Discord shows the raw text instead of a formatted timestamp.

Locale

The language and regional formatting settings of a reader device, which decide the exact wording and 12 or 24 hour clock a timestamp uses.

Frequently asked questions