Discord Dynamic Timestamps — Complete Format Guide

A Discord dynamic timestamp is a message tag using the syntax <t:UNIX_TIMESTAMP:FORMAT_CODE> that automatically displays the correct date and time in each viewer's own local timezone and clock preference — no manual timezone conversion needed from anyone.

Discord dynamic timestamps are one of the most useful features in the platform — and one of the most misunderstood. They're not just a way to show a time in a message. They're auto-updating, timezone-neutral tags that display differently for every person who reads them, automatically converting to each viewer's local timezone without any extra work from the sender.

Since January 2026, Discord also added the @time mention feature — you can type @time directly in the chat box, pick a date and time from a built-in picker, and Discord generates the dynamic timestamp tag for you without needing any external generator or manual Unix timestamp math. It's the easiest method available and most guides still don't mention it.

This guide covers every format code, exactly what each one outputs, how the syntax works, and how to generate them correctly every time.

What Makes a Discord Timestamp Dynamic

A standard time like "5:00 PM" is static — it means 5:00 PM in whatever timezone the sender is in, and everyone else has to do the conversion themselves.

A Discord dynamic timestamp tag like <t:1783338240:t> is different. Discord reads the Unix timestamp inside it, converts it to each viewer's local timezone automatically, and displays it in their own clock format — 12-hour or 24-hour depending on their personal Discord settings. The sender never has to think about timezones at all.

These tags are also called inline timestamps because they sit directly inside message text, not in a separate embed or attachment.

The Syntax

Every Discord dynamic timestamp follows this exact syntax:

<t:UNIX_TIMESTAMP:FORMAT_CODE>

• <t: — opens the tag
• UNIX_TIMESTAMP — a 10-digit number representing seconds since January 1 1970 (the epoch reference point)
• :FORMAT_CODE — a single letter that controls how the timestamp displays
• > — closes the tag

If you omit the FORMAT_CODE entirely and use just <t:UNIX_TIMESTAMP>, Discord defaults to the Short Date/Time (:f) format automatically.

All 7 Discord Timestamp Format Codes

All examples above are what a viewer in a given local timezone would see — someone in a different timezone sees the same moment converted to their own clock automatically.

Short Time — :t

Displays the time only, without a date. Good for recurring events where the date is already known — "the meeting starts at <t:1783338240:t>" reads cleanly as just the clock time.

Long Time — :T

Same as short time but includes seconds. Rarely needed for everyday server use but useful for precise technical logging or moderation records where exact seconds matter.

Short Date — :d

Displays the date in numeric format (MM/DD/YYYY). Compact and clean for reference lists, pinned messages, or anywhere a brief date reference is needed without a time component.

Long Date — :D

Displays the full written date — "July 6, 2026" — without a time. Best for birthday lists, anniversary dates, and event dates where the exact time doesn't need to be shown.

Short Date/Time — :f

The default format when no format code is specified. Shows both the date and time in a clean readable format. This is the most commonly used format code for event announcements and server scheduling.

Long Date/Time — :F

The most complete format — includes the full day of the week, written month, date, year, and time. Best for formal announcements, changelogs, and any message where maximum clarity matters.

Relative Time — :R

The most powerful format for countdowns and recency. It displays auto-updating text like "in 3 days," "in 2 hours," or "3 days ago" — and it keeps updating live as time passes. Every time someone reads the message, it shows the current relative distance from that moment.

How 12-Hour vs 24-Hour Display Works

Whether a Discord dynamic timestamp shows "5:00 PM" or "17:00" is not controlled by the sender — it's controlled by each viewer's personal Discord settings. Go to Discord settings → Language & Time to toggle between 12-hour and 24-hour display. This setting only affects how you see timestamps — it doesn't change what other people see.

How to Generate the Unix Timestamp

The Unix timestamp is the number of seconds since January 1 1970. You don't need to calculate this manually.

Easiest method (January 2026+): Type @time directly in any Discord message box, pick your date and time from the picker, and Discord inserts the fully formatted dynamic timestamp tag automatically.

Generator method: Use the Discord Timestamp Generator — pick your date and time visually, choose your format code, and copy the ready-to-paste code snippet.

Manual conversion: Use the Unix Timestamp Converter to convert any date and time to a 10-digit Unix timestamp in seconds, then wrap it in the syntax yourself.

Using Dynamic Timestamps in Zapier Automations

If you're using Zapier to automate Discord messages or announcements, you can generate dynamic timestamp tags inside your workflow without a separate tool.

Method 1 — Convert a date from a previous step: Add a Formatter action → choose Date/Time → select the Unix timestamp option. This outputs a plain Unix timestamp number in seconds. Map your date field as the input, test the step to confirm the output number, then wrap it in Discord's syntax in your message text: <t:YOURUNIXNUMBER:f>

Method 2 — Use the current time: In the Zap editor, open the Library and select the Current time (UNIX) system variable. Paste it into your message text wrapped in Discord's syntax — this outputs the exact time the Zap runs as a dynamic timestamp.

Important note: some tools and code steps output milliseconds (13 digits). Discord requires seconds (10 digits). If your timestamp displays a wildly wrong date, divide the number by 1000 using a Formatter Numbers step first. The syntax also only works inside Discord message text fields — it won't render in channel names or other non-message areas.

Common Mistakes to Avoid

Using milliseconds instead of seconds — Discord requires seconds (10 digits) — a 13-digit milliseconds number will display a date thousands of years in the future. Always verify your Unix timestamp is 10 digits.

Forgetting the format code letter — The code is case-sensitive — :f and :F produce completely different outputs. Lowercase :f is Short Date/Time, uppercase :F is Long Date/Time. :t and :T also differ — lowercase is Short Time, uppercase is Long Time.

Omitting the colon before the format code — The syntax requires <t:UNIX:f> — not <t:UNIXf> or <t:UNIX f>. Missing the colon between the timestamp and format code breaks the tag entirely.

Assuming 12-hour vs 24-hour is controlled by the sender — It's not — each viewer's personal Discord settings controls their own display. You cannot force a specific clock format for your audience.

Using dynamic timestamp syntax outside message text fields — The <t:> syntax only renders in Discord message text — it won't work in channel names, server descriptions, role names, or other non-message fields.

Typing the Unix number manually and making arithmetic errors — Use the @time mention, the Discord Timestamp Generator, or the Unix Timestamp Converter rather than calculating by hand.

Related Guides

• Discord Timestamp Formats — All 7 Styles Explained
• Discord Timestamp Cheat Sheet
• How to Use Discord Timestamps
• 10 Creative Ways to Use Discord Timestamps in Your Server

Also try our free tools:

• Discord Timestamp Generator — generate any dynamic timestamp instantly
• Unix Timestamp Converter — convert any date to Unix seconds
• Discord Countdown Generator — build live countdown timers