The field guide

Discord timestamp not working? Try these fixes

Fix literal timestamp code, dates near 1970, incorrect hours, unsupported styles, and countdowns that look different from your preview.

✓ Free. Instant. No account.

Start by identifying the symptom. Literal code usually points to formatting. A readable but wrong date usually points to the number or timezone. Paste the original code into the converter before changing it; that makes the stored moment visible.

You see <t:…> instead of a date

The code must have angle brackets, a lowercase t, colons, whole Unix seconds, and an optional supported style. A valid example is <t:1791635400:F>. Send it as ordinary text, without surrounding backticks or a code block.

Check for copied spaces, curly punctuation, or a missing closing bracket. The letters are case-sensitive. Uppercase R is relative time; lowercase r is unsupported. See the format reference for all nine choices.

The date is far in the future or near 1970

Discord expects seconds. JavaScript’s Date.now() returns milliseconds, so a developer must use Math.floor(Date.now() / 1000) when building a timestamp. Do not paste a 13-digit millisecond number directly into Discord markup.

The converter accepts raw milliseconds and produces seconds. Auto mode assumes raw numbers with 13 or more digits are milliseconds; choose Seconds or Milliseconds explicitly when the intended unit is unusual. Inside Discord markup, the number is always interpreted as seconds.

The event is an hour off

Check the source timezone for the event date. A fixed offset such as UTC−05:00 does not follow New York’s summer clock. Use America/New_York when that is the organizer’s location.

Also check whether the organizer gave you their time or an already converted local time. Entering a converted time while selecting the organizer’s timezone converts it twice. For repeated times when daylight saving ends, choose the correct occurrence.

Someone else sees a different date

That may be correct. Discord displays the moment in each viewer’s timezone, and events near midnight can fall on different calendar days. Compare the UTC time in the converter or use the generator’s Preview as control. Different language and clock settings can also change the appearance without changing the moment.

The countdown does not show seconds

The R style is relative wording, such as “in 2 hours.” Discord chooses the wording and refresh timing. A days/hours/minutes/seconds preview on this website is a separate browser clock. It does not control Discord’s display.

If the event has passed, relative wording changes to “ago.” The original timestamp stays fixed. Generate a new timestamp for the next event; changing the letter does not reschedule it.

The Copy button cannot access the clipboard

Some browser or permission settings block clipboard access. Use the manual-copy text box that opens, select the entire code, and copy it using your browser’s normal action. On mobile, press and hold the selected text if needed.

If the syntax is correct but Discord still behaves unexpectedly, try a normal message in a current Discord client and compare the code with Discord’s timestamp reference. A timestamp is a display feature, not a reminder bot or scheduled-message command.

Copy your code

Your browser could not access the clipboard. Select the text and copy it manually (Ctrl+C or ⌘C).