🕐

Discord Timestamp Generator

Pick a date and time to instantly generate every Discord timestamp format with live previews. Copy and paste directly into Discord.

Unix timestamp: 0


All timestamp formats

Short Time00:00
<t:0:t>
Long Time00:00:00
<t:0:T>
Short Date01/01/1970
<t:0:d>
Long Date1 January 1970
<t:0:D>
Short Date/Time1 January 1970 00:00
<t:0:f>
Long Date/TimeThursday, 1 January 1970 00:00
<t:0:F>
Relative57 years ago
<t:0:R>
Default (relative)495760 hours ago
<t:0>
All formats at once

Copy all timestamp formats to paste into Discord

How the calculation works

Discord renders special timestamp tags like <t:1234567890:F> as localized, automatically adjusted times — each viewer sees the time in their own timezone.

The number inside is a Unix timestamp: seconds since January 1, 1970 UTC. This tool converts your selected local date and time to that Unix value and generates all 8 Discord-supported format codes.

The format letter controls how Discord displays it: t = short time, T = long time, d = short date, D = long date, f = short datetime, F = long datetime, R = relative. No letter defaults to relative.

Frequently asked questions

Do Discord timestamps adjust for each viewer's timezone?

Yes — that's the whole point. When you paste <t:1234567890:F> into Discord, every viewer sees the time converted to their own local timezone automatically. No more '3pm EST — convert to your timezone'.

Where can I use Discord timestamps?

In any Discord message, channel description, or server announcement. They render in the desktop app, mobile app, and web app. They do NOT render in bot embed fields or titles — only in message content.

What does the R format look like?

The R (relative) format shows something like '2 hours ago' or 'in 3 days' and updates in real time as viewers see the message — without needing a page refresh.

Why is my time off by an hour?

Make sure you're entering the time in your local timezone. The tool uses your browser's local time. If you travel or change timezone settings, the resulting timestamp will still be correct because it's stored as UTC internally.

Related tools