Discord Timestamp Generator
Choose an instant, then copy Discord markup that displays in each viewer's timezone.
Discord timestamp formats
- Unix seconds
- UTC instant
- Device zone
Previews use this browser's language and timezone. Discord controls the final display for each viewer.
Private by design: this tool creates the markup in your browser. It does not put your date, time, timestamp, or generated text in the URL, browser storage, cookies, analytics events, or an application request.
Discord timestamp syntax
Discord's official message-formatting reference uses <t:TIMESTAMP> for the default display and <t:TIMESTAMP:STYLE> for a chosen style. The timestamp is a whole count of seconds from the Unix epoch. Paste the generated markup into a Discord message; Discord then renders that same instant for each viewer's locale and timezone.
| Style | Official meaning | Example syntax |
|---|---|---|
| Default / f | Long date and short time | <t:1618953630> |
| t / T | Short or medium time | <t:1618953630:T> |
| d / D | Short or long date | <t:1618953630:D> |
| f / F | Long or full date with time | <t:1618953630:F> |
| s / S | Short date with short or medium time | <t:1618953630:S> |
| R | Relative time | <t:1618953630:R> |
Local time, UTC offsets, and DST
A local date-and-time field does not contain an offset. This page applies the IANA timezone reported by your browser and shows its resolved numeric UTC offset before generation, updating it as the selected wall time changes. If clocks move forward over the selected wall time, that local time never occurred. If clocks move back over it, the same wall time occurred twice. The tool rejects either case so it cannot quietly generate the wrong instant.
For an exact instant around a clock change, use an ISO value with Z or a numeric offset such as 2026-11-01T01:30:00-04:00. Timezone rules can change, so keep your browser and operating system current.
Range and preview limits
ToolNeko accepts non-negative Unix seconds through 253402300799, which is 9999-12-31T23:59:59Z. This is ToolNeko's safe input range; Discord's public reference does not state a platform minimum or maximum. The on-page preview uses browser internationalization and is an approximation. Discord's own client is the final reference for wording and formatting.
Browser-only privacy
The converter runs locally after the static page loads. It has no Discord login, bot, token, webhook, message sender, server conversion, saved history, or share link. Tool analytics receive only fixed labels for the selected input mode, result status, and copy action. They never receive the entered date, offset, Unix seconds, generated syntax, or clipboard contents.
Frequently asked questions
What is the Discord timestamp format?
Use <t:UNIX_SECONDS> for the default display or <t:UNIX_SECONDS:STYLE> for a specific style. Discord reads the number as seconds and displays the instant in each viewer's locale and timezone.
Which Discord timestamp styles are available?
Discord currently documents t, T, d, D, f, F, s, S, and R. The f style is the default. The R style displays relative time, while the others display a date, time, or both.
Why was my local time rejected during a daylight-saving change?
A spring clock change can skip a wall time, while a fall clock change can repeat one. This tool rejects both cases instead of silently choosing a different instant. Enter an ISO time with an explicit numeric offset or use Unix seconds.
Should I enter seconds or milliseconds?
Enter whole Unix seconds. Discord's message syntax uses seconds. A current millisecond timestamp usually has 13 digits and is rejected here rather than divided automatically.
Is my date or timestamp uploaded or saved?
No. Generation runs in your browser. The tool does not put your input or output in the URL, browser storage, cookies, analytics events, or an application request.