Discord Timestamp Generator: Time Codes and Formats

How Discord timestamps work

The token is <t:UNIX> or <t:UNIX:STYLE>, where UNIX is a count of seconds since 1970-01-01 UTC and STYLE is one of nine single-letter codes. Discord replaces the token at render time using the viewer's locale and timezone, so the same message reads correctly in Tokyo and Toronto. When you omit the style, Discord uses f (long date with a short time).

Timestamps work in normal chat, webhook messages, embed descriptions and Components V2 Text Displays. Inside a code block the token is shown literally — that is the standard way to show someone the syntax itself.

All nine timestamp styles

Examples use 1767225600 (2026-01-01 00:00 UTC) as an en-US reader in UTC sees it; every reader gets their own language and timezone. The names are the ones in Discord's formatting reference. The s and S styles were added after the original seven, so older references list only seven.

Combine an absolute time with a countdown

Two tokens for the same moment read better than one in an announcement: the full date for people planning ahead, the relative one for people checking right before it starts. Discord renders each token independently, so the pair stays correct in every timezone and the countdown ticks over to “ago” once the moment passes.

Keep relative timestamps out of posts that stay pinned for months — “8 months ago” on a rules post reads as neglect. Use an absolute style there, and restore and update the message when the date itself changes; the editing guide walks through that without reposting.

## 🎮 Community game night
Starts <t:1767225600:F> — that's <t:1767225600:R>.
-# Times show in your own timezone.

Get the unix timestamp in code

Every language counts unix time in seconds from 1970-01-01 UTC, but several return milliseconds by default — the source of the year-57,000 bug below. Both bot libraries also ship a formatter that builds the whole token for you.

• In DWEEB, the clock button in the text toolbar opens the same picker as the generator above and inserts the token where your cursor is.
• In your own code, build the token as <t:SECONDS:STYLE> with an integer — a decimal such as 1767225600.5 is not a valid timestamp.

// JavaScript (browser, Node.js, Deno, Bun) — seconds, not milliseconds
Math.floor(Date.now() / 1000)
Math.floor(new Date("2026-01-01T00:00:00Z").getTime() / 1000) // 1767225600

// discord.js builds the token itself
import { time, TimestampStyles } from "discord.js";
time(new Date("2026-01-01T00:00:00Z"), TimestampStyles.RelativeTime) // "<t:1767225600:R>"

# Python
import time
from datetime import datetime, timezone
int(time.time())
int(datetime(2026, 1, 1, tzinfo=timezone.utc).timestamp())  # 1767225600

# discord.py builds the token itself
discord.utils.format_dt(datetime(2026, 1, 1, tzinfo=timezone.utc), style="R")  # "<t:1767225600:R>"

# macOS / Linux terminal
date +%s

# PowerShell
[DateTimeOffset]::UtcNow.ToUnixTimeSeconds()

# Excel or Google Sheets, for a UTC date and time in A1
=ROUND((A1 - DATE(1970,1,1)) * 86400, 0)

A timestamp in a real webhook payload

Timestamps are plain text inside a message, so a webhook needs nothing special to send one. This Components V2 payload posts an event notice with both an absolute and a relative time; import it into the Discord message builder to preview it, or send it from a script as shown in the cURL webhook guide.

{
  "flags": 32768,
  "components": [
    {
      "type": 10,
      "content": "## Community game night\nStarts <t:1767225600:F> — that's <t:1767225600:R>."
    }
  ]
}

Common mistakes