Discord Timestamp Formats: All 9 Codes Explained

How Discord timestamp syntax works

Discord describes timestamps as a custom part of its message formatting. A basic tag contains t, a colon, and a Unix timestamp wrapped in angle brackets. Add another colon and a style letter to choose the presentation:

<t:1754208000>
<t:1754208000:F>

The number 1754208000 identifies one instant. It does not carry a country, language, or timezone name. According to the current Discord API message-formatting reference, timestamps are expressed in seconds and displayed in the user’s timezone and locale. One reader may therefore see a 12-hour clock and month-first date while another sees a 24-hour clock and day-first date. Both renderings can identify the same instant.

Style letters are case-sensitive. t and T are different, as are d and D, f and F, and s and S. A generator should preserve the selected case exactly. If you want a ready-to-paste tag without doing the epoch calculation, use the LiveParse Discord Timestamp Generator.

All nine Discord timestamp formats

The table uses the names in Discord’s current developer documentation. Output descriptions are structural rather than fixed English examples because punctuation, date order, month names, and 12- or 24-hour clocks can vary by viewer.

Choose between time-only, date-only, and combined styles

Use t or T only when the surrounding sentence establishes the day. “Today at <t:…:t>” can be concise in a short-lived conversation, but it becomes unclear when someone finds the message later. The uppercase T adds seconds; that precision is useful for coordinated launches or incident timelines but usually adds noise to a casual event.

Use d or D when the clock time does not matter. The numeric d form is compact, yet its order follows locale, so one viewer’s month/day arrangement can differ from another’s. The written D form can be easier to scan when the exact date deserves more space.

The combined formats serve most scheduling messages. Lowercase f includes a long date and short time and is the documented default. Uppercase F adds the weekday, which is helpful for a raid, class, release, or community meeting. The compact s and S forms retain both date and time in less space; uppercase S includes seconds. These forms are especially useful in dense status lists or generated tables where a written month would dominate the row.

Use the R style for relative time

The R style asks the client to present the instant relative to the time of viewing. Depending on the instant and viewer, that can appear as wording equivalent to “in 2 hours” or “3 days ago.” It is useful for a countdown, submission window, maintenance start, or incident age. Avoid promising an exact refresh interval: Discord documents the style as Relative Time but does not specify a second-by-second update contract in the message-formatting table.

Relative text supplies urgency but can hide the calendar date. Pair it with an absolute style when people may revisit the message, cross a midnight boundary, or need to add the event to another system.

Event starts <t:1754208000:F> (<t:1754208000:R>).

Both tags must use the same Unix value. If one number is regenerated later, the displayed date and relative description can disagree. A one-click combined template in the Discord timestamp generator avoids that copy error.

Copy-ready announcement patterns

Replace the sample number by generating the intended date and source timezone. The surrounding wording remains static while Discord formats each tag for the reader.

Community event: <t:1754208000:F> — <t:1754208000:R>.
Submissions close <t:1754208000:F> (<t:1754208000:R>).
Release window opens <t:1754208000:f>.
Maintenance begins <t:1754208000:F> and is expected to last 30 minutes.
Incident began <t:1754208000:R> at <t:1754208000:T>.

Keep durations separate from instants. The timestamp identifies when maintenance begins; “30 minutes” describes an interval. Do not convert a duration such as 1,800 seconds into a date relative to 1970. For accessibility and resilience, give the timestamp a plain-language label such as “starts,” “closes,” or “began” instead of posting an unexplained tag by itself.

Understand source time, viewer timezone, and locale

Creating the Unix value and displaying it are two separate operations. First, the generator interprets the date and time in a source timezone and resolves it to one instant. Then Discord displays that instant using each viewer’s timezone and locale. The tag itself contains only Unix seconds and the style letter; it does not preserve the source timezone name.

This distinction matters for daylight saving time. A regional zone such as America/New_York has historical and seasonal rules, while a fixed offset such as UTC-05:00 does not adjust itself. During a spring transition, some local clock times do not occur. During a fall transition, one local time can occur twice. When scheduling near either boundary, use an IANA regional timezone, review the resolved UTC instant, and make an explicit choice if the local input is ambiguous.

A browser preview is only an approximation of what one reader may see. Discord’s documentation explicitly makes locale and timezone viewer-dependent, so a generator should not claim that punctuation or English wording will match every client. Validate the instant and style, then expect presentation differences that preserve the same moment.

Discord timestamps use seconds, not milliseconds

Discord’s reference says timestamp values are expressed in seconds. This differs from JavaScript’s Date.now(), which returns milliseconds. Around the present, Unix seconds are usually 10 digits while milliseconds are usually 13. Pasting a millisecond value directly into a Discord timestamp can produce an invalid or wildly distant date instead of the intended event.

Unix seconds:      1754208000     ← use inside <t:...:F>
Unix milliseconds: 1754208000000  ← divide by 1,000 first

Correct: <t:1754208000:F>
Wrong unit: <t:1754208000000:F>

If the millisecond value is divisible by 1,000, exact conversion is simple integer division. If it contains a sub-second remainder, choose and document whether to floor, round, or reject it; the inline tag cannot communicate that extra precision. Do not rely only on digit count for historical or far-future values. The seconds vs milliseconds guide explains reliable unit detection, and the Unix Timestamp Converter can inspect seconds, milliseconds, microseconds, and nanoseconds directly.

How to decode an existing timestamp tag

To decode <t:1754208000:F>, remove the angle brackets and split on colons. The first field, t, identifies timestamp markup. The second field, 1754208000, is the Unix-seconds value. The optional third field, F, selects the style. If no third field exists, use the default f interpretation described in Discord’s table.

1. Preserve the original tag. Do not edit the number while trying to read it.
2. Validate the shell. It should have angle brackets, a lowercase leading t, and colon-separated fields.
3. Validate seconds. Treat the middle field as Unix seconds and check that it resolves to a plausible date.
4. Validate the style. Accept only t, T, d, D, f, F, s, S, or R.
5. Convert or restyle. Decode the number with the generator, then change only the final style letter to preserve the instant.

Developers parsing user input can start from a strict shape such as ^<t:(\d+)(?::([tTdDfFsSR]))?>$, then separately enforce the application’s allowed date range. A matching shape does not prove that a client will accept an extreme timestamp.

Inline timestamp or Discord Scheduled Event?

An inline timestamp is useful inside an announcement, checklist, incident update, or generated message. It is lightweight and keeps the time beside the surrounding explanation. A Discord Scheduled Event is a separate server feature with event details and an Interested workflow that can notify participating members when the event goes live. Discord documents the setup and permission model in its Scheduled Events support guide.

Use the feature that matches the job. A short deadline may need only F plus R. A community session that benefits from discovery and participation tracking may warrant a Scheduled Event, with inline timestamps repeated in channel announcements. The two approaches can complement each other.

Troubleshooting a tag that stays as raw text

• Check angle brackets and colons. The complete shape is <t:UNIX_SECONDS:STYLE>, not parentheses, braces, or an ISO date.
• Use whole Unix seconds. Convert a millisecond API value before placing it in the tag.
• Check letter case. Only the nine documented, case-sensitive styles belong in the style position.
• Remove code formatting. Backticks are useful for showing raw syntax in a tutorial but intentionally present text as code rather than normal message formatting.
• Test the intended context. Discord documents inline timestamp message formatting, but distinct fields and surfaces can have different formatting behavior.
• Check range and plausibility. A syntactically valid integer can still represent an unsupported or unintended date.

LiveParse is not affiliated with or endorsed by Discord.