Enter the event time
Choose the date and wall-clock time exactly as announced by the event organizer.
Free · no sign-up · browser-based
Pick a date, time, and timezone. Get a Discord timestamp that automatically displays in every member’s local time—ready to copy and paste.
1 · Set the moment
Enter the wall-clock time in the timezone where the event is scheduled.
2 · Copy the code
This preview uses your browser’s locale and timezone, similar to how Discord renders it for you.
<t:0:F>
Choose how the same moment appears. The viewer’s language, timezone, and 12/24-hour preference control the final rendering.
Omitting the style—<t:UNIX>—uses f as the default. The s and S styles are included because they now appear in Discord’s current official reference.
Turn the timestamp into a clear event announcement or live countdown.
Paste a <t:...> code, Unix seconds, or Unix milliseconds to convert it back.
One minute guide
A Discord timestamp represents one exact moment as Unix seconds. Discord then formats that moment for each person who reads the message, so nobody needs to calculate EST to GMT or UTC to JST manually.
Choose the date and wall-clock time exactly as announced by the event organizer.
Use a named region such as America/New_York so daylight saving rules match that date.
Paste the selected <t:UNIX:STYLE> code into Discord and send the message.
Discord renders timestamp markdown after the message is sent. If you only paste it into the composer, seeing the raw code is normal.
Format reference
Use F for a clear event announcement, R for a live relative countdown, and t when the date is already obvious. The less common s and S styles provide compact date-and-time combinations.
| Style | Official meaning | Typical output | Best use |
|---|---|---|---|
t | Short Time | 4:20 PM | Time only, profiles, short reminders |
T | Medium Time | 4:20:30 PM | Logs and second-level precision |
d | Short Date | 04/20/2026 | Compact schedules |
D | Long Date | April 20, 2026 | Readable date without time |
f | Long Date, Short Time | April 20, 2026 at 4:20 PM | General-purpose default |
F | Full Date, Short Time | Monday, April 20, 2026 at 4:20 PM | Events and formal announcements |
s | Short Date, Short Time | 04/20/2026, 4:20 PM | Compact date and time |
S | Short Date, Medium Time | 04/20/2026, 4:20:30 PM | Compact logs with seconds |
R | Relative Time | in 2 hours | Countdowns and recency |
Practical examples
Combine F and R: members get the full local date plus a countdown that updates automatically.
The R style changes from “in 2 hours” to “5 minutes ago” without editing the original message.
Use t to show what a reference time—often your midnight—looks like to another person. Regenerate it after DST changes.
Place timestamp markdown in supported message or embed text. For “started X ago,” generate the start time with R.
Use a full local date and a relative time together so readers know both the exact deadline and how long remains.
A single code replaces long lists of EST, PST, GMT, and JST times and reduces scheduling mistakes.
Timezone accuracy
EST is a fixed UTC−5 label, while New York commonly uses EDT (UTC−4) during daylight saving time. Selecting America/New_York lets the date decide which offset is correct.
Your code contains Unix seconds, not a timezone name. Discord reads that single moment and formats it in the viewer’s own timezone and locale.
When clocks spring forward, a time such as 2:30 AM may not exist. When clocks move back, 1:30 AM can occur twice. This converter detects both cases instead of silently choosing the wrong hour.
A code cannot mean “every Friday at 5 PM.” It points to one date and time. Generate a new timestamp for each recurring event, especially across DST changes.
Questions answered
Generate a code such as <t:UNIX:F>, paste it into a Discord message, and send it. The same code displays in each reader’s own timezone and locale. You do not need to list separate EST, PST, GMT, or JST times.
Discord’s current developer reference lists nine styles: t, T, d, D, f, F, s, S, and R. Many older generators only mention seven because s and S were less commonly documented.
Choose the event time and copy the R style. Discord renders it as relative time—for example, “in 2 hours”—and updates the wording as time passes. It is a live relative label, not an animated seconds counter.
Yes. Use t for hours and minutes or T to include seconds. The visible message omits the date, but the timestamp still represents one exact date and moment underneath.
Choose America/New_York for normal Eastern Time scheduling. It automatically follows the correct EST or EDT offset for the selected date. Use a fixed abbreviation only when you intentionally mean that fixed offset.
Yes. The decoder accepts a full code such as <t:1767225600:R>, plain Unix seconds, or 13-digit Unix milliseconds. You can then load the decoded moment back into the generator.
Discord uses each viewer’s client locale, timezone, and time-format preference. This page previews with your browser settings, so minor punctuation or 12/24-hour differences are possible even though the underlying moment is identical.
Discord’s current formatting reference describes timestamps as Unix seconds but does not publish a practical 2038 cutoff. This tool does not impose that frequently repeated limit; for extremely distant dates, confirm the result in your current Discord client.
No. This is an independent utility and is not affiliated with or endorsed by Discord Inc. The timestamp syntax and style names follow the current public Discord developer reference.
Your selected date, time, timezone, decoded code, and message text are never submitted to this site. Optional Google Analytics can be enabled with your consent; analytics events contain only the feature name (for example, “copy format F”), never the values you entered. Your consent choice is stored locally in your browser.