DiscordFree Tool

Discord Timestamp Generator

Pick a date and time, copy the code, paste it into any Discord message. Discord turns <t:1790884800:F> into the date in each reader's own time zone, so a stream start posted from Europe reads correctly in Los Angeles. All nine styles from Discord's developer docs, with a live preview and one-click copy.

Pick a date and time
  • Short time
    <t:UNIX:t>
    …
  • Medium time
    <t:UNIX:T>
    …
  • Short date
    <t:UNIX:d>
    …
  • Long date
    <t:UNIX:D>
    …
  • Long date, short time (default)
    <t:UNIX:f>
    …
  • Full date, short time
    <t:UNIX:F>
    …
  • Short date, short time
    <t:UNIX:s>
    …
  • Short date, medium time
    <t:UNIX:S>
    …
  • Relative (updates live)
    <t:UNIX:R>
    …
  • Stream announcement (date + countdown)
    <t:UNIX:F> (<t:UNIX:R>)
    …

Previews use your browser's language. Discord renders the same code in each reader's own time zone and locale, so separators and the 12/24-hour clock can differ slightly from what you see here.

How to Use a Timestamp in a Discord Message

  1. 1Set the date and time above. If you are scheduling for another region, pick the time zone the time is written in — the code is the same instant either way.
  2. 2Copy the style you want. For a stream announcement, the combined row gives you the full date plus a live countdown.
  3. 3Paste the code into any Discord message, as plain text — not inside backticks or a code block, which would show the raw code.
  4. 4Send it. Discord replaces the code with a highlighted date, and every reader sees it converted to their own clock.

The pattern that works for streamers is one line in your announcements channel: Live on Twitch <t:1790884800:F> (<t:1790884800:R>). Viewers get the exact date in their zone and a countdown that stays current. It pairs well with a Go Live session in your own server for community nights. Timestamps combine with the rest of Discord's Markdown too — bold, headers, small text — all covered in our Discord text formatting cheat sheet.

What Each Timestamp Style Shows

Discord's developer documentation lists nine styles. The examples are Discord's own, for the same instant (1618953630) seen by a reader who uses a 24-hour clock. Your readers see the same layout in their own language and clock format.

CodeStyleDiscord's exampleUse it for
<t:…:t>Short Time16:20Same-day times: “raid at 16:20”.
<t:…:T>Medium Time16:20:30When seconds matter — drop windows, countdown starts.
<t:…:d>Short Date20/04/2021Deadlines and compact lists.
<t:…:D>Long DateApril 20, 2021Events where the day matters, not the hour.
<t:…:f>Long Date, Short TimeApril 20, 2021 at 16:20The default: <t:UNIX> with no letter renders this.
<t:…:F>Full Date, Short TimeTuesday, April 20, 2021 at 16:20Stream schedules — the weekday removes doubt.
<t:…:s>Short Date, Short Time20/04/2021, 16:20Tables, logs and pinned schedules.
<t:…:S>Short Date, Medium Time20/04/2021, 16:20:30Moderation notes and incident logs.
<t:…:R>Relative Time4 years agoCountdowns: “starts in 2 hours”. Updates on its own.

Source: Discord Developer Docs, Timestamp Styles, checked September 27, 2026. Plenty of generators still list seven styles; s and S are the newer pair.

Why Every Reader Sees Their Own Local Time

The code does not store a time zone. It stores one instant — the number of seconds since 00:00 UTC on January 1, 1970 — and each Discord client formats that instant with the reader's own time zone and locale. That is the whole point: “8 PM EST” in a message makes half your community do arithmetic and some of them get it wrong around daylight-saving changes. A timestamp cannot be misread.

It also means the time zone picker above only matters to you, the writer. Choose the zone the time is written in — “9 PM in New York” — and the generator works out the instant; the code it produces is identical to what someone in Tokyo would get for the same moment.

Mistakes That Break a Timestamp

  • Milliseconds instead of seconds. A 13-digit number is milliseconds and renders tens of thousands of years ahead. Current dates are 10 digits.
  • Posting it inside backticks. Code formatting shows everything literally, timestamps included. Paste the code as plain text.
  • Wrong letter case. Styles are case-sensitive: t is 16:20, T is 16:20:30.
  • Writing the zone next to it. “<t:1790884800:t> EST” is wrong for everyone outside EST, because the timestamp has already converted itself.

Timestamps in Bots and Webhooks

A bot sends the same string in its message content: build it from Unix seconds (`<t:${Math.floor(date.getTime() / 1000)}:F>` in JavaScript, f"<t:{int(dt.timestamp())}:F>" in Python). Always floor to whole seconds — a decimal breaks the code. If your automation lives on the stream side rather than in Discord, our stream bots roundup compares Nightbot, Moobot, Streamer.bot and the rest.

Frequently Asked Questions

How do I make a timestamp in Discord?

Type <t:UNIX:STYLE> in a message, where UNIX is the moment in Unix seconds and STYLE is one of t, T, d, D, f, F, s, S or R. For example <t:1790884800:F> shows Thursday, October 1, 2026 at 20:00 UTC — converted to each reader's own time zone. This generator produces the code for any date so you do not have to calculate the Unix time yourself.

What are all the Discord timestamp formats?

Discord's developer documentation lists nine styles: t (short time), T (medium time, with seconds), d (short date), D (long date), f (long date with short time, the default), F (full date with weekday), s (short date and time), S (short date with medium time) and R (relative, such as 'in 3 hours'). Many older guides list only seven; s and S are the newer two.

Why does my Discord timestamp show a date in 1970 or the far future?

The number is in the wrong unit. Discord expects seconds since January 1, 1970 UTC — a 10-digit number for current dates. JavaScript's Date.now() and many APIs return milliseconds, a 13-digit number, which lands tens of thousands of years in the future. Divide by 1,000, or paste the number here and the generator converts it.

Does everyone see the same time in a Discord timestamp?

Everyone sees the same moment, written in their own time zone and locale. Discord's docs say timestamps display 'in the user's timezone and locale', so an 8 PM stream start written in Kyiv shows as 10:00 AM to a viewer in Los Angeles (with both on summer time) without anyone doing the maths.

Why is my timestamp showing as raw text like <t:1790884800:F>?

Usually it is inside backticks or a code block, which show everything literally. Other causes: a missing colon or angle bracket, a style letter Discord does not use, or a decimal or millisecond value. Styles are case-sensitive — t and T are different formats.

Does the relative timestamp update by itself?

Yes. The R style is computed when the message is displayed, so 'in 2 hours' becomes 'in 1 hour' and later '5 minutes ago' without anyone editing the message. That makes it the best choice for countdowns to a stream or event.

Can bots and webhooks use Discord timestamps?

Yes. The <t:UNIX:STYLE> syntax is part of Discord's message formatting, so a bot or webhook puts the same string in its message content. Build it from the Unix time in seconds, for example Math.floor(Date.now() / 1000) in JavaScript or int(time.time()) in Python.

Is this Discord timestamp generator free?

Yes, free and without an account. Everything runs in your browser: the date you pick is never sent anywhere, and the time zone list comes from your browser's own time zone database.