Discord Timestamp Generator
Choose a date, time and time zone to get Discord timestamp codes like <t:1767225600:R>. Discord shows each one in the reader's own time zone and language, so nobody has to convert times for your event, raid or stream.
Last updated:
Decode an existing code or Unix timestamp
All 7 Discord timestamp styles
Previews use your browser's time zone () and language, the same way Discord shows them to each reader.
What readers in other time zones see
| Reader's time zone | Shown as (style f) | UTC offset |
|---|
How to use the Discord Timestamp Generator
- Pick the date and time of your event, or press Set to now.
- Choose the time zone that date and time is in (your own zone is selected by default).
- Compare the 7 styles and their previews: relative (R) is great for countdowns, long date/time (F) for announcements.
- Press Copy next to a code, or write a whole message with {F} and {R} placeholders and copy that.
- Paste it into Discord: after you send, every member sees the time converted to their own clock.
Discord timestamp format reference
Every Discord timestamp has the same shape: <t:UNIX:STYLE>. UNIX is a whole number of seconds since 1 January 1970 00:00:00 UTC (the Unix epoch), and STYLE is one of seven letters. The table uses Unix time 1767225600, which is 1 January 2026 00:00 UTC, as a US-English reader in New York (UTC−5) would see it.
| Style | Code | Example output (en-US, New York) | Good for |
|---|---|---|---|
| Short time | <t:1767225600:t> | 7:00 PM | Daily resets, "today at" times |
| Long time | <t:1767225600:T> | 7:00:00 PM | Precise starts, drops, logs |
| Short date | <t:1767225600:d> | 12/31/2025 | Deadlines, compact tables |
| Long date | <t:1767225600:D> | December 31, 2025 | Birthdays, release dates |
| Short date/time (default) | <t:1767225600:f> or <t:1767225600> | December 31, 2025 7:00 PM | Most event announcements |
| Long date/time | <t:1767225600:F> | Wednesday, December 31, 2025 7:00 PM | Big events where the weekday matters |
| Relative | <t:1767225600:R> | in 2 months / 3 days ago | Countdowns, "posted X ago" |
Note how the same code shows 31 December for a New York reader but 1 January for a reader in London or Tokyo: that is exactly the point. The exact punctuation and word order follow each reader's Discord language setting, so a German-language reader sees day-month order and a 24-hour clock from the very same code.
How the Unix timestamp is calculated
The generator converts the wall-clock time you pick in the chosen time zone into UTC, then counts seconds from the epoch:
Unix = (local date and time − UTC offset of that zone at that moment) − 1970-01-01T00:00:00Z, in seconds
For example, 8:00 PM on 14 March 2026 in New York: daylight saving time started on 8 March, so the offset is UTC−4 and the moment is 00:00 UTC on 15 March, giving 1773532800. The same 8:00 PM a week earlier is still UTC−5. Because the offset is looked up for the exact date, the tool handles daylight-saving changes automatically. Times that do not exist (such as 2:30 AM on the night clocks spring forward) are moved to the nearest real time and flagged.
Discord message, user, channel and server IDs are snowflakes that also contain a time: milliseconds = (ID >> 22) + 1420070400000, where 1420070400000 is the first second of 2015, Discord's own epoch. Paste an ID into the Decode box to turn it back into a date and ready-made timestamp codes.
Tips for event announcements
- Combine two styles: "Raid starts
<t:…:F>(<t:…:R>)" gives readers the exact time plus a live countdown. The message builder above does this with{F}and{R}. - Edit, don't repost: if the time changes, edit the message and swap the number; every reader's view updates at once.
- Use seconds, not milliseconds: a 13-digit JavaScript timestamp (from
Date.now()) must be divided by 1000, or Discord will show a date tens of thousands of years in the future. - Bots: in code, build the string as
`<t:${Math.floor(date.getTime() / 1000)}:R>`(JavaScript) orf"<t:{int(dt.timestamp())}:R>"(Python).
Frequently asked questions
How do Discord timestamps work?
Discord turns the text <t:UNIX:STYLE> into a date or time after the message is sent. UNIX is the number of seconds since 1 January 1970 00:00 UTC, and STYLE is one letter (t, T, d, D, f, F or R). Each reader's Discord app formats that moment in their own time zone and language, so one code works for a worldwide server.
What are the 7 Discord timestamp formats?
t is short time (4:20 PM), T is long time with seconds (4:20:30 PM), d is short date (10/23/2026), D is long date (October 23, 2026), f is short date/time (October 23, 2026 4:20 PM), F is long date/time with the weekday, and R is relative time (in 2 hours, 3 days ago). Exact wording depends on the reader's language settings.
What happens if I leave out the style letter?
A code without a style, such as <t:1767225600>, is shown in the default short date/time style, the same as :f.
Does the relative (R) timestamp update by itself?
Yes. A relative timestamp keeps counting while the message is on screen, switching from "in 5 minutes" to "in 4 minutes" and eventually to "5 minutes ago", which makes it handy as a simple countdown for events.
Why does the time zone I choose matter?
The time zone tells the generator what moment you mean. 8:00 PM in New York and 8:00 PM in London are different Unix timestamps. Pick the zone the event was planned in; Discord then converts that single moment for every reader.
Where do Discord timestamps work?
They are converted in normal messages, replies, forum posts and in bot embed descriptions and field values. Places that do not support markdown, such as usernames, nicknames, channel names and embed footers, show the raw <t:…> code instead.
How do I find when a Discord message was sent?
Turn on Developer Mode in Discord's settings, right-click the message and choose Copy Message ID, then paste the ID into the Decode box. Discord IDs are snowflakes: the ID shifted right by 22 bits plus 1420070400000 is the creation time in milliseconds.
Are all the tools on FreeToolCabin tested for quality and accuracy?
Yes! Every tool on our site undergoes automated Q/A testing in real browser environments to ensure high precision, correct output, and zero errors. If you happen to spot a bug or have a suggestion, please contact us at [email protected] and our team will review it right away.