A Discord timestamp is a piece of message markup, <t:SECONDS:STYLE>, that each reader’s client replaces with a date. The number is a Unix timestamp in seconds and names one instant; the client writes it out in the reader’s own time zone and the language their Discord is set to. That is the whole reason to use one: an event posted as <t:1790000000:t> reads 15:13 in London and 10:13 AM in New York, and nobody has to convert anything. The letter picks the format. Discord documents nine — t and T for the time, d and D for the date, f, F, s and S for both, and R for relative time such as “in 2 hours” — and a tag with no letter is shown as f.
Input is read in one of three ways. A date and time with no offset, such as 2026-10-31 20:00, is wall-clock time in the selected zone, which starts as your browser’s; an explicit offset or Z overrides it. A number is a Unix timestamp whose unit comes from its length: ten digits is seconds, and thirteen is milliseconds, which is converted with a warning because it is the commonest way these tags go wrong. JavaScript’s Date.now() returns milliseconds, Discord reads the number as seconds, and the result is a date some 56,000 years away. An existing tag is decoded exactly as Discord would read it, so a broken one reproduces the broken date and the warning gives the tag that was meant. Locale formats such as 10/03/2026 are refused rather than guessed.
Clock changes are handled, not ignored. When the clocks go forward, an hour of wall-clock time never happens; when they go back, an hour happens twice. A skipped time is moved on by the length of the gap and a repeated time takes its first occurrence — the same rules Temporal and java.time apply by default — and either case produces a warning, with the tag for the second occurrence where there is one. The previews come from your browser’s Intl.DateTimeFormat in the chosen zone and language, which reproduces Discord’s documented examples closely, but the real rendering happens in each reader’s client. Relative Time is the loosest: Discord does not publish its rounding or wording, so the preview here is an approximation.