Discord Unix Timestamp Examples: Copy-Ready Format Guide

If your server has members in multiple regions, plain text times like "8:00 PM" create constant follow-up questions.

Discord Unix timestamps solve this with one rule: publish a single Unix value, and Discord renders local time for each reader.

Use the Discord Time Converter to generate your Unix value first, then choose the style based on message intent.

If you automate reminders with bots, run a quick health check in the Discord Bot Status Checker before your campaign starts.

Quick syntax refresher

Discord timestamp syntax:

<t:UNIX:STYLE>

• UNIX is seconds since Jan 1, 1970 (UTC)
• STYLE controls how the timestamp appears

Example base value:

<t:1767225600:F>

Use seconds, not milliseconds. If your source gives Date.now(), divide by 1000 and round down.

const unixSeconds = Math.floor(Date.now() / 1000);
const fullFormat = `<t:${unixSeconds}:F>`;

Discord Unix timestamp examples by style

Below are the style variants you will actually use in server operations.

t (short time)

Code:

<t:1767225600:t>

Typical output:

8:00 PM

Best use:

• Recurring events where date context is already obvious
• Same-day reminders in active channels

T (long time with seconds)

Code:

<t:1767225600:T>

Typical output:

8:00:00 PM

Best use:

• Precise countdown checkpoints
• Moderator operations where second-level precision matters

d (short date)

Code:

<t:1767225600:d>

Typical output:

12/31/2026

Best use:

• Changelog dates
• Deadline cards and application windows

D (long date)

Code:

<t:1767225600:D>

Typical output:

December 31, 2026

Best use:

• Formal announcements
• Rules or policy updates with legal style copy

f (short date + time)

Code:

<t:1767225600:f>

Typical output:

December 31, 2026 8:00 PM

Best use:

• Event reminders with full context
• Ticketed sessions where members skim quickly

F (weekday + full date + time)

Code:

<t:1767225600:F>

Typical output:

Thursday, December 31, 2026 8:00 PM

Best use:

• Main event announcement post
• Any message that becomes the source of truth

R (relative time)

Code:

<t:1767225600:R>

Typical output:

in 3 days or 2 hours ago

Best use:

• Countdown urgency
• Last call reminders
• Post-event summaries

Copy-ready message examples

Use these templates directly and replace the Unix value.

Launch announcement

🚀 Launch starts at <t:1767225600:F> (<t:1767225600:R>)
Readiness check opens 15 minutes before start.

Why this works: members see exact local datetime and urgency in one line.

One-hour reminder

⏰ Reminder: session begins at <t:1767225600:t> today.
Time remaining: <t:1767225600:R>

Why this works: short message, fast to scan on mobile.

Deadline notice

📌 Submission deadline: <t:1767225600:D>
Final cutoff countdown: <t:1767225600:R>

Why this works: date clarity plus live urgency, no timezone math needed.

When to choose each format

Use this practical mapping:

• Source-of-truth event posts: F + R
• Fast reminder pings: t + R
• Static reference docs: D
• Precision ops and logs: T

You can combine two formats in one sentence, but avoid stacking three or more. Dense time syntax reduces readability.

Common mistakes that break trust

1. Milliseconds instead of seconds
   • Wrong: <t:1767225600000:F>
   • Right: <t:1767225600:F>
2. Missing angle brackets
   • Wrong: t:1767225600:F
   • Right: <t:1767225600:F>
3. Mixing static timezone labels with dynamic timestamps
   • Avoid writing 8 PM EST next to a Discord timestamp; it confuses readers.

Mobile readability checklist

Before sending an announcement, validate:

• Keep the first line under 70 characters where possible
• Put timestamp tokens on their own line in long messages
• Pair one exact format (F or f) with one urgency format (R)
• Preview in Discord mobile to confirm line breaks

A clear timestamp message saves moderator time and reduces "what time is this for me?" replies.

For reusable reminder cadence, see the related template post at /blog/discord-event-reminder-message-template.