Discord Timestamp

Discord timestamp markup embeds a Unix second and a style letter so each member’s client formats the same instant in that member’s locale. The token looks like <t:unix:style>. Hard-coding “3 PM EST” in a 2026 announcement forces every reader to convert. This generator builds copy-ready tokens from Unix seconds, from an existing Discord token, or from a picked calendar date—without uploading chat history.

The seven style letters

R is Relative: a live phrase such as “in two hours” or “three days ago” that Discord updates as time passes. t is short time of day. T is long time of day, typically with seconds. d is a compact calendar date. D is a long calendar date. f combines a short date with time. F combines a long date with time. Pick one style per mention. Stacking several styles for the same instant is usually noise in a channel.

Discord evaluates the Unix second in UTC, then formats for the viewer. Two people reading the same token see different clock faces and the same underlying moment. That is the point for multi-region communities. Relative (R) is the right default for countdowns and “starts soon” pings. Long date/time (F) is the right default for launches, raids, and meetings that will still be read next week.

Short styles keep chat compact when the date is already clear from surrounding text. Evergreen documentation should prefer F or D so an archived message in 2026 still names the civil day after Relative has flipped to “a year ago.” Preview the chosen letter in a private Discord channel before pinning a public post.

Seconds versus milliseconds

Discord expects Unix seconds, not milliseconds. A thirteen-digit Date.now() value pasted raw looks centuries off because the client treats it as seconds since 1970. This tool treats a long digit string as milliseconds and divides by 1,000. Prefer sending seconds from a server Instant. If a bot already has milliseconds, divide once before wrapping the token.

A ten-digit second is the usual width for current civil time. If the value field shows thirteen digits after a copy from browser DevTools, assume milliseconds until the UTC preview looks like the intended day in 2026. If the preview is in the far future, you still have milliseconds. If the preview is in 1970, you may have pasted a truncated or hex value—decode seconds on the Unix timestamp page first.

Noon local versus UTC midnight is the other common miss. Picking a calendar date here encodes a civil day; Discord still stores UTC seconds. A DST spring-forward in the reader’s zone changes the printed clock, not the stored second. Check the UTC preview line, then confirm the style in Discord itself.

Paste, generate, and preview in Discord

Enter Unix seconds, paste a full token such as <t:…:R>, or choose a calendar date. Convert to see every style letter with copy-ready markup plus a UTC preview. Decoding an existing token regenerates all seven styles from the same second so you can switch R to F without re-picking the instant.

Always preview in a Discord sandbox or staff channel. Relative text depends on “now” at read time; a token that looks right at 09:00 will read differently at 18:00. Absolute F and D do not drift that way. For a full-page ticking timer instead of chat markup, use the countdown creator.

For recurring weekly events, generate a fresh token each week rather than reusing an old Relative stamp that already passed. Keep a spreadsheet column of Unix seconds if you schedule many drops; test one row here first. Bots should emit tokens from a true UTC Instant, not from a floating local string concatenated with a style letter.

What Discord timestamps are not

They are a chat convenience, not a legal clock for contracts. Store ISO-8601 with offsets or Unix seconds in your own systems; render Discord markup only in announcement channels. Interchange strings belong on the ISO 8601 converter when the next hop is an API rather than a Discord client.

Conversion runs in the browser for ordinary use. You are not required to upload message history to generate markup for 2026 announcements. If a token looks wrong after paste, check milliseconds versus seconds, UTC midnight versus local noon, and whether the style letter is one of t, T, d, D, f, F, or R.

Bots, Instant, and mixing styles

A Discord bot that schedules raids should format tokens on the server from a UTC Instant, then send one style per event. Mixing R in the reminder and F in the event post is reasonable: the reminder expires, the event post remains readable. Mixing t, T, d, D, f, and F in a single sentence repeats the same instant six ways and reads like a test dump.

Slash-command UIs that ask for a local datetime must convert that civil clock through a named zone before taking Unix seconds. A “tomorrow at 8” string without a zone is not an Instant. After conversion, paste the seconds here, copy F for the announcement, and copy R only for a same-day nudge. Preview both tokens in Discord; Relative depends on the reader’s “now,” while F does not.

Role-mention pings that include an R token still need an F somewhere in the same message if the channel is logged for people who read it the next morning. Pins that survive all of 2026 should drop R entirely. If you later change the event time, regenerate the token; Discord will not rewrite an old second just because you edited surrounding prose.