Discord Timestamp Generator

Discord dynamic timestamps explained

Discord can render a Unix timestamp as a localized date or relative phrase for every reader. Paste a tag like <t:1715429912:F> into a message and Discord expands it using each user’s timezone and language. The raw value is always Unix seconds (UTC). This generator builds every official style flag so you can copy-paste ready markup — entirely in your browser, with no data leaving the tab.

Reference instant: 1715429912 is Saturday, May 11, 2024 at 12:18:32 UTC (not a 2026 date). Relative style :R will show phrases such as “2 years ago” that update as time passes.

All Discord style flags (with examples)

Append a style letter after the Unix seconds. Without a style, Discord defaults to a short datetime similar to :f.

:t — short time. Example: <t:1715429912:t> → about 12:18 (localized).
:T — long time. Example: <t:1715429912:T> → about 12:18:32.
:d — short date. Example: <t:1715429912:d> → about 05/11/2024 (locale-dependent).
:D — long date. Example: <t:1715429912:D> → about May 11, 2024.
:f — short date/time. Example: <t:1715429912:f> → date plus short time.
:F — long date/time. Example: <t:1715429912:F> → full weekday, date, and time.
:R — relative. Example: <t:1715429912:R> → “2 years ago” / “in 3 hours” style text that refreshes.

Pick :R for countdowns and “how long ago,” :F for event announcements, and :t/:T when only the clock matter.

How Discord localizes for each reader

The tag stores one absolute UTC second. Discord’s client converts that second into the reader’s configured timezone and formats it with their locale (12-hour vs 24-hour, day/month order, translated relative phrases). A raider in Tokyo and a raider in New York therefore see different clock faces from the same <t:…> string — which is exactly why community managers prefer Discord timestamps over writing “8pm EST.”

Use cases: events, reminders, and raid times

Event announcements — post <t:unix:F> plus <t:unix:R> so everyone sees both the absolute local time and a live countdown.
Reminders / bots — schedule jobs in Unix seconds, then emit Discord tags in channel messages without hard-coding zones.
Raid and game nights — one tag replaces long lists of converted times for NA/EU/ASIA guilds.
Support / ops — share an incident start as <t:unix:f> so on-call staff in any region align quickly.

Common mistakes

Milliseconds instead of seconds. Discord expects 10-digit-scale Unix seconds. Pasting 1715429912000 yields a nonsense far-future date. Divide JavaScript Date.now() by 1000.
Wrong style letter. Flags are case-sensitive: :t ≠ :T, and :f ≠ :F. A typo silently falls back or looks odd.
Writing local wall time as if it were UTC. Convert the intended instant to UTC Unix seconds first, then wrap it. This tool accepts Unix seconds or ISO dates and shows every style at once.
Forgetting the angle brackets. Discord only expands tags written as <t:UNIX:STYLE> with the angle brackets included.

Generate from “now” or ISO

Click Use now to fill the current Unix second, or paste an ISO 8601 value such as 2024-05-11T12:18:32Z. The results grid lists every style with a one-click copy. For deeper epoch background, read the epoch time explained guide. Need a duration between two raid times? Use the timestamp difference calculator. Comparing across zones? Try the timezone converter.

Privacy: generation is 100% in-browser — your timestamps never leave this tab, and no Discord account is required to build the tags.

Frequently asked questions

What Discord timestamp style flags exist?

Discord supports t (short time), T (long time), d (short date), D (long date), f (short date/time), F (long date/time), and R (relative). Example for 1715429912: and .

Why does the same Discord tag show different times for different people?

Discord localizes tags using each reader’s client timezone and locale. The underlying value is always UTC Unix seconds; only the display changes.

Should I paste milliseconds into a Discord timestamp?

No. Discord expects Unix seconds. A 13-digit millisecond value produces a wrong far-future date. Convert milliseconds by dividing by 1000 first — e.g. 1715429912000 → 1715429912.

How do I generate a Discord timestamp from now or an ISO date?

Use the “Use now” button for the current UTC second, or paste an ISO 8601 string / Unix seconds into the input. Copy any style row into your Discord message.

Does UnixLi send my Discord timestamps to a server?

No. Generation runs 100% in your browser. Unix seconds and preview strings never leave your tab — there is no upload or account required.

What is the difference between :f and :F?

Both combine date and time. :f is the shorter datetime form; :F is the longer, more formal datetime. Prefer :R for relative phrases like “in 2 hours” or “3 days ago.”