Discord Timestamp Generator by NexLink Core
Discord timestamps render in each member’s own timezone automatically. Post one in an event announcement and everyone sees the time correctly, with no list of conversions and no arguments about whether the restart is at 8pm BST or 8pm EST.
Pick a date and time below, then copy the code you want.
Generate a Timestamp
How Discord Timestamps Work
A Discord timestamp is a Unix timestamp — the number of seconds since 1 January 1970 — wrapped in a special tag:
<t:1735689600:F>t:tells Discord this is a timestamp1735689600is the moment in time, in secondsFis the display style
Discord replaces the whole tag with a formatted date when the message renders. The raw text stays in the message, so it keeps working forever and updates itself as time passes.
The Seven Styles
| Style | Name | Renders roughly as |
|---|---|---|
:t | Short Time | 16:20 |
:T | Long Time | 16:20:30 |
:d | Short Date | 01/01/2025 |
:D | Long Date | 1 January 2025 |
:f | Short Date/Time | 1 January 2025 16:20 |
:F | Long Date/Time | Wednesday, 1 January 2025 16:20 |
:R | Relative | in 3 hours / 2 months ago |
If you leave the style off entirely — <t:1735689600> — Discord falls back to :f.
The exact wording and order depend on each viewer’s language and locale settings, which is the whole point. A member in the US sees 1/1/2025, a member in the UK sees 01/01/2025, and neither has to think about it.
:R is the one to reach for in announcements. “Server restart in 2 hours” stays accurate as people read it at different times, and it counts down on its own without you editing the message.
Using Timestamps Well
Event announcements — pair an absolute style with a relative one so people get both the exact time and the at-a-glance urgency:
Wipe day is <t:1735689600:F> — that's <t:1735689600:R>!Restart notices — a relative timestamp saves you from editing the message as the restart approaches:
Scheduled restart <t:1735689600:R>. Save your progress and log out safely.Event schedules — use short times in a list, since the date is already established by the heading:
**Saturday's events**<t:1735689600:t> — Boss spawn<t:1735693200:t> — PvP tournament<t:1735700400:t> — Build contest judgingTimestamps only render inside Discord message content, embeds and some bot fields. They do not work in channel names, channel topics, server names, nicknames or custom statuses — those show the raw <t:…> text instead.
Converting an Existing Timestamp
Paste any Unix timestamp into the Unix timestamp field to jump straight to it. The date and time fields update, and every style is regenerated.
If the value you have is in milliseconds — 13 digits rather than 10, which is what JavaScript’s Date.now() returns — divide it by 1000 first. Discord expects seconds, and a millisecond value lands roughly fifty thousand years in the future.
Frequently Asked Questions
Do I need a bot for this?
No. Timestamps are built into Discord’s message formatting. Anyone can paste the code into any message.
Why does my timestamp show as plain text?
Three usual causes: the code was auto-corrected (check the angle brackets are < and >, not smart quotes), it was placed inside a code block, or it’s somewhere that doesn’t support formatting such as a channel name.
Can I use a timestamp in a bot embed?
Yes — in embed descriptions, field values, and the author or footer text. Note the footer has its own separate timestamp property, which is often what you actually want there.
How far into the future can I go?
Comfortably further than you need. Discord handles dates well beyond any realistic event schedule, so a year-out anniversary countdown is no problem.
Does the timezone dropdown change what other people see?
No. It only controls how your entered date and time are interpreted when converting to a Unix timestamp. Once generated, the timestamp is an absolute moment, and every viewer sees it in their own timezone regardless of which option you chose.