Discord Time Zone Converter – Discord Timestamp Generator

Paste one value per line—Unix seconds, a complete <t:…> tag, 2027-01-15, or 2027-01-15 21:00. Date-only lines use midnight in the selected source timezone, while date-and-time lines honor that timezone and its daylight-saving rules.

The batch view reports the number of valid lines, shows the first errors without hiding the rest of the list, and can copy either the selected style or all nine formats for every valid line. Nothing in the batch is uploaded.

The documented timestamp structure is <t:TIMESTAMP>, with the styled form <t:TIMESTAMP:STYLE>. The first t identifies the timestamp construct. TIMESTAMP is a whole Unix timestamp in seconds. The optional final letter asks Discord to render a particular date, time, or relative form.

If the style is omitted, Discord documents f as the default. Therefore <t:1800000000> and <t:1800000000:f> request the same style. Keeping :f visible can make a template easier to review; omitting it makes the tag slightly shorter.

Style letters are case-sensitive. Lowercase t and uppercase T are different styles, as are d/D, f/F, and s/S. Relative time uses uppercase R.

The R style expresses an instant relative to the viewer’s current time. A future value might appear as “in 2 hours,” while a past value might appear as “3 days ago.” Discord owns the final wording, so do not assume every locale chooses the same unit or phrase.

Relative output is excellent for urgency but weak as the only permanent record. After enough time passes, “months ago” no longer identifies the exact calendar date. Pair R with F: Event starts <t:1800000000:F> (<t:1800000000:R>). The first tag anchors the schedule; the second makes remaining time easy to grasp.

This creates a Discord countdown timestamp, not an interactive timer widget or embed. Discord recalculates the relative wording whenever the message is viewed. The generator includes event, deadline, release, and maintenance templates using this pair; they are plain message text, so you can edit the surrounding words after copying.

Discord’s reference specifies seconds. JavaScript’s Date.now() returns milliseconds. A current Unix seconds value is commonly about ten digits, while the same instant in milliseconds is commonly about thirteen. Pasting the larger value as seconds can produce an implausibly distant date.

For example, 1800000000 is seconds; 1800000000000 is milliseconds for the same instant. Convert deliberately by dividing whole milliseconds by 1,000 and deciding how to handle a remainder. In JavaScript, Math.floor(milliseconds / 1000) selects the containing Unix second, including the correct direction before the epoch.

The decoder detects values that resemble modern milliseconds, microseconds, or nanoseconds and offers a seconds conversion rather than silently accepting the wrong scale. For broader work, use the Unix Timestamp Converter and timestamp unit guide.

Paste a tag such as <t:1800000000:S>. The built-in Discord timestamp converter extracts the seconds, keeps the case-sensitive style, converts the instant to the selected source-zone clock, and makes all nine alternatives available. A tag without a style is decoded as default f.

Decoding helps when updating an old event message, reviewing a bot template, or checking a unit mistake. The parser accepts the timestamp structure rather than arbitrary message text. It rejects decimal seconds and undocumented style letters instead of guessing.

This is different from a Discord snowflake ID. Snowflakes encode creation time plus worker, process, and increment bits; paste a decimal message, channel, or user ID into the snowflake decoder below to convert its creation metadata.

To get a message ID, enable Developer Mode in Discord’s settings, then use the message context menu’s copy-ID action. If your Discord app instead offers Copy Message Link, the final numeric segment of that message link is the message ID. Paste the decimal ID into the decoder.

Paste a decimal ID such as 1199835124667021433 into the decoder. LiveParse shifts the ID right by 22 bits, adds Discord’s epoch of 1420070400000 milliseconds, and shows 2024-01-24 21:56:25.579 UTC. Use Use creation time to load the equivalent whole second, 1706133385, into the timestamp generator.

The result also separates worker, process, and increment fields. This helps when correlating logs, reviewing bot output, or checking whether a supposedly old ID was really created at the stated time. The decoder runs in your browser and accepts only decimal IDs within Discord’s unsigned 64-bit range. Discord’s Snowflakes reference documents the same 42-bit timestamp and epoch used here.