A server event announcement
Use the full date-and-time style for the event’s scheduled instant. Add the relative style after it when you also want readers to see how far away it is.
Create a Discord timestamp for an event, deadline, or server announcement. Enter a date and time with a source zone, or paste Unix seconds. Compare the output in different viewer zones and languages before copying the code.
Discord displays the same instant in each viewer’s time zone and language. These browser previews approximate its presentation; relative rounding may differ.
UTC: 2026-10-23T18:00:00.000Z
| Style | Code to paste | Viewer preview | Copy |
|---|---|---|---|
| Short time (t) | <t:1792778400:t> | 6:00 PM | |
| Time with seconds (T) | <t:1792778400:T> | 6:00:00 PM | |
| Short date (d) | <t:1792778400:d> | 10/23/26 | |
| Long date (D) | <t:1792778400:D> | October 23, 2026 | |
| Date and time (f) | <t:1792778400:f> | October 23, 2026 at 6:00 PM | |
| Full date and time (F) | <t:1792778400:F> | Friday, October 23, 2026 at 6:00 PM | |
| Short date and time (s) | <t:1792778400:s> | 10/23/26, 6:00 PM | |
| Short date and time with seconds (S) | <t:1792778400:S> | 10/23/26, 6:00:00 PM | |
| Relative time (R) | <t:1792778400:R> | in 57 years |
Paste the code directly into a Discord message, without backticks. This tool supports instants from January 1, 1970 through December 31, 2100 in UTC. Browser time-zone data determines DST conversion.
Timestamp generation and preview formatting run in the page without a Discord connection.
Select a date, a 24-hour time, and an IANA zone, or switch the input to Unix seconds. Use current time fills the input with the present instant.
Resolve a repeated daylight-saving hour by choosing its UTC offset. Skipped clock times must be changed. Check the UTC instant and seconds value shown below.
Choose a viewer time zone and language for the preview. Copy one format or all formats. Paste the code into a Discord message without wrapping it in backticks.
Use the full date-and-time style for the event’s scheduled instant. Add the relative style after it when you also want readers to see how far away it is.
1618953630 is a seconds value. A JavaScript-style 13-digit millisecond timestamp must be divided by 1,000 before use. This generator rejects values outside its supported seconds range.
Set the instant to January 1, 2026 at 23:30 UTC, then select Asia/Tokyo for the viewer. The long-date preview shows January 2, 2026.
The nine documented style letters cover time (t, T), date (d, D), date with time (f, F, s, S), and relative time (R). Uppercase and lowercase letters select different presentations. The generated codes include an explicit style. Discord uses f when the style is omitted.
A generated code contains Unix seconds rather than the entered city name. Changing preview settings leaves the code unchanged. These previews use the browser’s international date formatting; punctuation, relative rounding, and exact presentation may differ from Discord.
An input zone gives meaning to the entered local clock time. The conversion checks that time against the zone’s rules for the selected date. During a repeated hour, choosing the first or second occurrence produces different Unix values. A nonexistent spring-forward time is rejected instead of silently moved.
Paste the angle-bracket code directly into a message. Backticks and code blocks prevent normal formatting. Also check that the value uses whole Unix seconds and that the style letter is valid.
They are whole Unix seconds. This tool supports nonnegative values from 0 through 4133980799, covering 1970 through 2100 in UTC.
No. It changes the preview only. To change the event itself, edit the input date, clock time, source zone, or Unix seconds.
Its code represents a fixed instant. The relative display compares that instant with the current time. This page refreshes its relative preview every second; Discord controls its own refresh and rounding.
No. It creates text for you to copy and paste. No Discord account connection is used.