Skip to content
Free Tool Arena

Developer Utilities · Free tool

Discord Timestamp Generator

Pick a date and time, get all Discord timestamp formats (short date, long date, relative). Copy-paste ready.

Updated June 2026
Unix seconds: 1780333020
<t:1780333020:t>Short time (16:20)
<t:1780333020:T>Long time (16:20:30)
<t:1780333020:d>Short date (20/04/2026)
<t:1780333020:D>Long date (20 April 2026)
<t:1780333020:f>Short datetime (20 April 2026 16:20)
<t:1780333020:F>Long datetime (Monday, 20 April 2026 16:20)
<t:1780333020:R>Relative (in 2 hours / 3 days ago)
Found this useful?EmailBuy Me a Coffee

Advertisement

What it does

Discord renders timestamps differently for every viewer based on their timezone — instead of saying "the meeting starts at 18:00 UTC" and forcing everyone to convert, you paste a dynamic timestamp like <t:1746554400:F> and each viewer sees it in their own local time. This tool builds those timestamp strings for any date you pick, in all 7 formats Discord supports.

The 7 formats:

  • :t — short time (16:20)
  • :T — long time (16:20:30)
  • :d — short date (20/04/2026)
  • :D — long date (20 April 2026)
  • :f — short date+time (20 April 2026 16:20) — the default if you omit the suffix
  • :F — long date+time (Monday, 20 April 2026 16:20)
  • :R — relative ("in 3 hours" / "5 minutes ago")

The number after <t: is a Unix timestamp (seconds since 1970-01-01 UTC). Discord computes the locale and timezone client-side, so each user sees the time in their own settings — perfect for events, reminders, scheduled drops, or anything date-sensitive in a server with people across timezones.

Embed this tool on your siteShow snippet

Paste this snippet into any page. Loads on-demand (lazy), no tracking scripts, and sized to most dashboards. Replace the height to fit your layout.

<iframe src="https://freetoolarena.com/embed/discord-timestamp" width="100%" height="720" frameborder="0" loading="lazy" title="Discord Timestamp Generator" style="border:1px solid #e2e8f0;border-radius:12px;max-width:720px;"></iframe>
Embed docs →

Example input & output

Input

Pick April 23, 2026 at 18:00 in your local time

Output

<t:1745424000:F> renders as "Thursday, 23 April 2026 18:00" for you, and equivalently in each viewer's local timezone.

Type or paste this directly into Discord chat. The angle brackets are required — Discord matches the pattern exactly to render the timestamp.

How to use it

  1. Pick a date and time using the date/time inputs (defaults to now).
  2. The timestamp is in your local timezone — change the timezone dropdown if you're scheduling something in a different region.
  3. Each format renders side-by-side with a live preview of how Discord will display it for someone in your timezone.
  4. Click Copy on the format you want. Paste into Discord chat — it'll render automatically when sent (no escape, no markup).
  5. For relative timestamps (:R), Discord updates them live — "in 3 hours" becomes "in 2 hours" without anyone re-rendering the message.

When to use this tool

  • Scheduling a community event (raid, AMA, voice chat) where attendees are in multiple timezones.
  • Setting a deadline for submissions or a giveaway end-time without timezone-confusion replies.
  • Reminding members of a recurring meeting with a fresh relative timestamp each week.
  • Coordinating a release window for a game, drop, or product reveal — the relative format counts down automatically.

When not to use it

  • Discord servers where you're not allowed to use raw markup (very rare; the timestamp uses standard Discord syntax).
  • Embeds and webhook payloads — those have their own ISO-8601 datetime fields; only chat messages render <t:...> dynamically.
  • Other chat platforms (Slack, Teams, Telegram) — they don't support Discord's timestamp syntax.
  • Time-sensitive messages where you want everyone to see UTC explicitly (just write "18:00 UTC" instead).

Frequently asked questions

Why does Discord support these timestamps but other chat apps don't?
Discord added them in 2021 specifically because so much of its userbase coordinates events across global timezones. Slack and Teams have similar concepts (Slack's date markup) but Discord's is the most flexible and widely used.
What's the maximum date Discord supports?
Roughly the year 2106 — Unix timestamps fit in a signed 32-bit integer up to 2,147,483,647, which is January 19, 2038 03:14:07 UTC. Discord uses 64-bit timestamps internally so dates beyond that work, though the server may render odd results for far-future dates.
Why does my :R relative timestamp not update?
It does — Discord re-renders it every minute on the client. If you don't see it ticking, your client is using a cached message or you're testing in a snapshot tool that doesn't re-evaluate.
Can I use these in DMs?
Yes. Timestamp markup works in any Discord context where you can send a normal message — server channels, DMs, threads, group DMs.
Will these display correctly for users on the Discord mobile app?
Yes. The mobile apps (iOS and Android) render timestamps using the device's locale and timezone, identical to the desktop client.
Is the conversion timezone-aware?
Yes. The Unix timestamp is always in UTC seconds, but the input picker uses your browser's local timezone by default. Change the timezone dropdown to schedule "6 PM in Tokyo" — the tool computes the correct UTC seconds for that wall time.

Advertisement

Learn more

Explore more developer utilities tools

100% in-browserNo downloadsNo sign-upMalware-freeHow we keep this safe →

Found this useful?

The tools stay free thanks to readers who chip in or spread the word.

Buy Me a Coffee