Discord Timestamp Format Codes: All 7 Styles Explained

If you have ever typed "the event starts at 9 PM EST" in a Discord announcement and immediately had someone in a different timezone ask what time that is for them — this guide is for you.

Discord has a built-in timestamp system that automatically converts any date or time into every viewer's local timezone. You paste one tag, every server member sees the correct time for their location. No conversions, no confusion.

This guide covers every format code, when to use each one, and how to generate timestamps without doing Unix math yourself.

What Is a Discord Timestamp?

A Discord timestamp is a special tag you type in any channel, DM, or bot message. The format is:

<t:UNIX_TIMESTAMP:FORMAT_CODE>

Where UNIX_TIMESTAMP is the number of seconds since January 1, 1970 (UTC), and FORMAT_CODE is a single letter that controls how the date/time displays.

When Discord renders this tag, it replaces it with a human-readable time in each viewer's own local timezone. Someone in New York and someone in Tokyo both see the event time correctly — no manual conversion required.

You can also use the tag without a format code: <t:1234567890> defaults to the f (short date/time) style.

All 7 Discord Timestamp Format Codes

Using a Unix timestamp of 1732752000 (November 28, 2024, 00:00 UTC) as the example:

Code Tag Example Output Example Style Name
t <t:1732752000:t> 12:00 AM Short Time
T <t:1732752000:T> 12:00:00 AM Long Time
d <t:1732752000:d> 11/28/2024 Short Date
D <t:1732752000:D> November 28, 2024 Long Date
f <t:1732752000:f> November 28, 2024 12:00 AM Short Date/Time
F <t:1732752000:F> Thursday, November 28, 2024 12:00 AM Long Date/Time
R <t:1732752000:R> 5 months ago Relative Time

Important: All outputs are rendered in the viewer's local timezone. The examples above show UTC — your server members will each see their own local equivalent.

When to Use Each Format Code

:t and :T — Time Only

Use these when the date is already established and you only need to communicate a time. Good for recurring events ("weekly voice chat at <t:UNIX:t>") or when you have already stated the date and just need to reinforce the time.

:T adds seconds — useful for countdown precision or game events where seconds matter.

:d and :D — Date Only

Use these for deadlines, release dates, or anniversaries where the time is not relevant. :D (November 28, 2024) is more readable and less ambiguous than :d (11/28/2024) for international audiences, since date format order varies by country.

:f — The Default and Most Versatile

:f is the format code most server owners reach for. It combines date and time in a compact format, and it is what Discord renders when you omit the format code entirely. Use it for event announcements, scheduled streams, and anything where members need both the date and the time at a glance.

:F — Full Date with Day of Week

:F adds the day of the week (Thursday, November 28...) which makes it the best choice for events that recur weekly or where the day-of-week context helps people plan. "The tournament starts on :F" is more scannable than just a date when members are checking it against their own week.

:R — Relative Time (The Most Powerful One)

:R is the only format that updates live. It renders as "in 3 days," "in 2 hours," "5 minutes ago," and continues updating as time passes. This makes it ideal for:

  • Countdown timers: "Server maintenance starts <t:UNIX:R>"
  • Event reminders that stay relevant: "Tournament signup closes <t:UNIX:R>"
  • Post-event references: "The stream ended <t:UNIX:R>" (becomes "2 hours ago")

A common pattern is combining :f and :R in the same message: "Event starts <t:UNIX:f> (<t:UNIX:R>)". This gives members both the exact time and a live countdown.

How to Generate a Discord Timestamp (Without Unix Math)

Converting a human-readable date like "April 25, 2026 at 8:00 PM" to a Unix timestamp in your head is not practical. You need a generator.

Use our free Discord Timestamp Generator — pick a date and time, get all 7 format codes instantly with one-click copy buttons. No math, no manual conversion, no ads.

Steps:

  1. Open the Discord Timestamp Generator
  2. Select your date and time in the picker (it respects your local timezone automatically)
  3. All 7 format codes generate in real time
  4. Click the copy button next to whichever format you want
  5. Paste directly into Discord

Real-World Examples

Server Event Announcement

🎮 Game Night this Saturday!
Time: <t:1745614800:F> (<t:1745614800:R>)
Join #voice-chat when the time comes.

This renders as "Saturday, April 26, 2026 7:00 PM" with a live countdown. Every member sees their own local time.

Deadline Reminder

📝 Art contest submissions close <t:1745614800:D>.
That's <t:1745614800:R> — don't miss it!

Maintenance Window

⚠️ Bot maintenance scheduled for <t:1745614800:f>.
Expected duration: 30 minutes.

Weekly Recurring Event

📅 Next study session: <t:1745614800:F>
Same time every week — bookmark this channel.

Frequently Asked Questions

Why does my timestamp show the wrong time?

Discord timestamps are stored as UTC and converted to the viewer's local timezone by the Discord client. If the rendered time looks wrong to you, check your device's system timezone settings — Discord uses the OS timezone, not any setting inside Discord itself.

Can I use timestamps in bot messages?

Yes. Discord timestamp tags work in all text content that Discord renders — server channels, DMs, threads, forum posts, and bot messages. Bots can include them in message content, embed descriptions, embed fields, and embed footers. They do not work inside embed titles.

Does :R update in real time on all devices?

Yes. The :R relative format updates live on desktop, browser, and mobile clients. The timestamp is fixed in the message — the Discord client calculates the relative display dynamically based on the current time.

What is a Unix timestamp?

A Unix timestamp is the number of seconds elapsed since January 1, 1970 at 00:00:00 UTC, also called the Unix Epoch. It is the standard way computers represent moments in time without timezone ambiguity. Discord's timestamp tags use Unix time (seconds, not milliseconds) as their base. Our generator handles the conversion for you automatically.

Can I combine multiple format codes in one message?

Yes, and it is encouraged. Using :F for the full date/time alongside :R for a live countdown is the most common combination. Each <t:UNIX:FORMAT> tag is independent — use as many as needed in a single message.

What happens if I send a timestamp that is in the past?

It renders normally as a date/time, and the :R format shows "X days ago" or "X months ago." There is no error or special behavior for past timestamps.