Discord Timestamp Format: All 7 Codes Explained

The Discord timestamp format is one of those features that separates well-run servers from chaotic ones. Instead of typing "8PM EST" and fielding twenty questions about conversions, you paste a short code and Discord renders the time correctly for every single member, in their own timezone, in their own language. This guide covers all 7 Discord timestamp codes, the exact syntax behind them, and the markdown quirks that trip people up.

If you just want to generate a code right now, our Discord timestamp generator builds them for you with a live preview. But if you run a server, it's worth understanding how the format actually works. It takes five minutes, and you'll never have to look it up again.

The Cheat Sheet: All 7 Discord Timestamp Codes

Here's the full table. Every code uses the same Unix timestamp (1784194890, which is July 16, 2026 at 9:41:30 AM UTC). Example renderings assume a viewer with a US English device set to UTC; your members will each see their own local version.

Bookmark this table or keep the Discord timestamp generator open. Those are your only seven options; Discord doesn't support custom format strings, so there's no way to build something like "Jul 16 @ 9:41" out of the box.

Anatomy of the Syntax: <t:UNIX:STYLE>

Every Discord dynamic timestamp is built from the same three parts wrapped in angle brackets:

<t:1784194890:F>
 │      │      │
 │      │      └─ Style code (one of: t, T, d, D, f, F, R)
 │      └─ Unix timestamp (seconds since Jan 1, 1970 UTC)
 └─ Literal "t" prefix that tells Discord this is a timestamp

Three rules govern the whole thing:

1. The prefix is always a lowercase t. It's not related to the t style code; it just marks the token as a timestamp.
2. The number is a Unix timestamp in seconds. More on this below, because it's the single most common source of broken timestamps.
3. The style letter is optional. <t:1784194890> with no style renders exactly like <t:1784194890:f>, the short date/time format. That's why f is called the default.

Case matters for the style letter. <t:1784194890:d> gives you 07/16/2026, while <t:1784194890:D> gives you July 16, 2026. Uppercase means "longer version" for every pair: t/T, d/D, f/F. Only R stands alone.

The 7 Format Codes in Detail

t — Short Time

Renders just the clock time: 9:41 AM. Use it when the date is already obvious from context, like "Doors open at <t:1784194890:t> tonight." This is the t format Discord users reach for most often in same-day announcements.

T — Long Time

Same as t but with seconds: 9:41:30 AM. Honestly, this one is rare in the wild. It's useful for logging precise moments (raid resets, speedrun splits, incident timelines) and not much else.

d — Short Date

A compact numeric date: 07/16/2026. Note that the order of day and month follows each viewer's locale. An American sees 07/16/2026 while a German member sees 16.07.2026. That's a feature, not a bug; nobody has to decode ambiguous dates.

D — Long Date

The date written out: July 16, 2026. Cleaner for announcements where you want the date to read naturally in a sentence.

f — Short Date/Time (the Default)

Date plus time: July 16, 2026 9:41 AM. If you omit the style letter entirely, this is what Discord renders. It's the safe, all-purpose choice for event posts.

F — Long Date/Time

Everything including the weekday: Thursday, July 16, 2026 9:41 AM. Best for big scheduled events where the day of the week genuinely matters. "Is that a weekend?" gets answered before anyone asks.

R — Relative Time

The crowd favorite: in 2 hours, in 3 days, 5 minutes ago. The relative style is the only Discord dynamic timestamp that updates live while the message sits in chat. A countdown that reads "in 2 hours" now will read "in 20 minutes" later without anyone editing the message. Pair it with an absolute format for the best of both worlds:

Server maintenance starts <t:1784194890:F> (<t:1784194890:R>)

That renders as "Server maintenance starts Thursday, July 16, 2026 9:41 AM (in 2 hours)" and the parenthetical keeps counting down.

Unix Time: The Number Doing All the Work

The middle part of the code is a Unix timestamp: the number of seconds elapsed since January 1, 1970 at 00:00:00 UTC. Right now that number is somewhere north of 1.78 billion. It's timezone-free by definition, which is exactly why Discord can render it correctly for everyone.

Two things to watch:

• Seconds, not milliseconds. Discord expects a 10-digit value for contemporary dates. Many programming languages and APIs (JavaScript's Date.now(), most JSON APIs) hand you 13-digit millisecond values. Paste one of those into a timestamp and Discord will happily render a date around the year 58,000. The fix is simple: divide by 1000 and drop the remainder. 1784194890000 becomes 1784194890.
• Negative numbers work. Dates before 1970 are just negative Unix timestamps, so <t:-86400:D> renders December 31, 1969. You'll rarely need this, but it won't break anything.

You don't have to calculate any of this by hand. Our Unix timestamp converter converts human-readable dates to Unix seconds and back, and it flags millisecond values before they bite you.

Timestamps Render in the Viewer's Timezone (and Locale)

This is the part that confuses new users most, so let's be explicit: you don't choose the timezone. Each viewer's device does.

When you post <t:1784194890:f>, you are not posting "9:41 AM UTC." You're posting a moment in time. A member in New York sees 5:41 AM, a member in London sees 10:41 AM (BST), and a member in Tokyo sees 6:41 PM. All of them are looking at the same message, and all of them are right.

Locale follows the same rule. Date order (07/16 vs 16.07), 12-hour vs 24-hour clocks, month names, and the language of relative strings like "in 2 hours" all come from each viewer's Discord language and system settings. Hovering over a timestamp on desktop shows a tooltip with the full date, which is a handy way to double-check what you posted.

The practical consequence for server admins: never append a timezone label to a dynamic timestamp. Writing "<t:1784194890:t> EST" defeats the entire feature and will actively mislead everyone who isn't in EST, because they're seeing their own local time next to your label.

Markdown Limitations You Should Know

Discord timestamp codes live inside Discord's markdown engine, and the engine has opinions. These are the rules that break timestamps most often:

• No timestamps inside links. [click here](<t:1784194890:f>) doesn't work, and neither does using a timestamp as link text. The markdown link parser and the timestamp parser don't nest.
• No timestamps inside headings. Put # Event at <t:1784194890:t> in a message and the timestamp portion won't render as a heading element properly. Keep timestamps in body text and let headings stay plain.
• Backticks show the raw code. Wrapping a timestamp in ` inline code or a ``` code block tells Discord "render this literally," so your members see <t:1784194890:f> as text. That's useful when you're teaching someone the syntax, and infuriating when you do it by accident.
• Don't straddle bold or italic markers. The full code must sit entirely inside or entirely outside formatting markers. **Starts <t:1784194890:R>** is fine. Splitting the code across the markers, like putting ** between the brackets, breaks parsing.

If a timestamp shows up as raw text in your server, one of these four rules is almost always the culprit. We keep a full troubleshooting checklist in our guide to common timestamp errors.

Which Format Should You Actually Use?

After watching thousands of timestamps get generated on this site, clear patterns emerge:

• Event announcements: F for the headline time, plus R in parentheses for the countdown.
• Deadlines: R alone. "Submissions close in 3 days" is more motivating than a date.
• Same-day pings: t. Nobody needs the date repeated at them.
• Records and logs: f or d, since they read cleanly in history searches.

If you're new to all of this, start with our beginner walkthrough on how to use timestamps. It covers the workflow end to end, including mobile.

Try It Yourself

Reading about the Discord timestamp format is one thing; watching all 7 codes render from your own chosen time is what makes it stick. Open the Discord timestamp generator, pick a date, and copy whichever style fits. Every format is previewed exactly the way Discord will render it, so what you paste is what your members see.