Discord Timestamp Generator
Pick a date, copy the markup for every style • Auto-adjusts to each viewer's timezone
Pick a date and time
Timestamps render in each viewer's own timezone automatically.
| Preview | |
|---|---|
| Short Time | |
| Long Time | |
| Short Date | |
| Long Date | |
| Short Date/Time | |
| Long Date/Time | |
| Relative |
Timestamps that adapt to every reader's timezone
Discord timestamps are more than a date — they are dynamic markup that re-renders in each viewer's local time and can even count down on their own. Here is how the syntax, styles, and timezone engine fit together.
The <t:UNIX:style> markup, decoded
Every Discord timestamp follows one pattern: an opening <t:, a Unix epoch time measured in seconds since 1 January 1970, a colon, an optional style letter, and a closing >. For example, <t:1735689600:F> points to a precise instant, and the F tells Discord to render it as a long date and time.
The epoch number is the same for everyone on Earth — it is the timezone-neutral anchor. The style letter is purely cosmetic. Because you never type a human date directly, there is no ambiguity about day-month order or AM/PM: you pick a moment above and the generator produces the exact code Discord expects.
All seven style codes and when to reach for each
Discord supports seven styles: t short time, T long time with seconds, d short date, D long date, f short date-and-time (the default when no letter is given), F long date-and-time including the weekday, and R relative. Each one reads the same underlying epoch but frames it differently.
Use D or F for one-off announcements where the full date matters, t for quick times inside a sentence, and R for anything that should feel live. The generator shows a preview of all seven at once, so you can copy the style that reads most naturally in your message with a single click.
Why every reader sees their own local time
The single biggest reason to use timestamps is timezone safety. Instead of writing 'the raid starts at 8 PM EST / 1 AM UTC / 10 AM JST', you post one <t:UNIX:F> code and Discord converts it to each member's device clock automatically. Nobody has to do the math, and nobody shows up an hour early.
This works because the epoch value is absolute. Discord's client reads your operating-system timezone at render time and formats the moment accordingly, so the exact same message is correct for a reader in Los Angeles, London, or Sydney.
Live countdowns for events and scheduling
The relative style, <t:UNIX:R>, is the only one that changes after you send it. It renders as 'in 3 hours' before an event and flips to '2 hours ago' afterward, recalculating every time the message is viewed. That makes it perfect for event descriptions, giveaway end times, and scheduled maintenance notices.
Pair a fixed style with a relative one for the best of both — for example 'Starts <t:UNIX:F> (<t:UNIX:R>)' shows the exact local date and a self-updating countdown side by side. Everything is generated in your browser, so there is no account, upload, or tracking.
Frequently Asked Questions
What is a Discord timestamp and how does the <t:UNIX:style> format work?
A Discord timestamp is markup written as <t:UNIX:style>, where UNIX is a Unix epoch time in seconds and the style letter sets the display format. Discord replaces the code with a formatted, timezone-aware date that every reader sees in their own local clock.
What are all the Discord timestamp format codes (t, T, d, D, f, F, R)?
There are seven style letters: t (short time), T (long time with seconds), d (short date), D (long date), f (short date and time, the default), F (long date and time with weekday), and R (relative, like 'in 2 hours'). This generator outputs all seven for any date.
How do I get the Unix timestamp for a Discord message?
Pick the date and time you want in the generator above and it converts your selection to a Unix epoch value automatically, then wraps it in the full <t:UNIX:style> code. Copy the style you need and paste it straight into Discord — no manual epoch math required.
Do Discord timestamps automatically adjust to each user's timezone?
Yes. Discord renders the same code in each reader's local timezone, so a member in New York and one in Tokyo both see the correct moment in their own time. That makes timestamps ideal for scheduling events without listing several time zones side by side.
How do I make a Discord countdown timer or relative timestamp?
Use the relative style, <t:UNIX:R>. It renders as 'in 3 hours' or '2 days ago' and recalculates on its own as time passes, so an event code quietly counts down. Pick your target date above and copy the R-style output to drop a live countdown into any message.