Discord Timestamp Format Guide: Every Style Explained

Discord timestamps solve one painful problem: people in different regions reading the same event time.

Instead of typing a static date like 8:00 PM EST, you can send a dynamic code:

<t:1700000000:F>

Discord converts that value to each member's local timezone automatically.

Timestamp syntax

Every timestamp follows this pattern:

<t:UNIX:STYLE>

• UNIX: seconds since January 1, 1970 (UTC)
• STYLE: optional format code, such as R, t, or F

If you skip STYLE, Discord uses a default date/time presentation.

Most useful style codes

R - Relative time

Shows a live phrase like in 2 hours or 3 days ago.

Best for countdowns, launch reminders, and temporary notices.

t and T - Time only

• t shows short time
• T shows long time with seconds

Great for recurring schedules where date context is already clear.

d and D - Date only

• d is compact
• D is full date text

Use these in roadmap updates and changelog posts.

f and F - Date + time

• f is short date/time
• F is full weekday + date + time

Use F for formal server announcements.

Common mistakes to avoid

1. Using milliseconds instead of seconds (Date.now() must be divided by 1000)
2. Forgetting angle brackets around the code
3. Mixing static timezone labels with dynamic timestamps in the same sentence

Quick publishing checklist

Before posting an event message, verify:

• Timestamp preview renders correctly in Discord
• You selected the correct style (R for countdown, F for full detail)
• The message still reads well on mobile

If all three checks pass, your community sees the right time without manual conversion.