Discord Timestamp Generator
Generate Discord timestamp codes that show in everyone's local timezone — all 7 formats with live preview.
Written by Anil Gautam · Updated
How is the Unix time in the code worked out?
The date and time box uses your device's time zone. When you pick a moment, the tool converts it to Unix time, the number of seconds since 00:00 UTC on 1 January 1970, and shows that number next to the box. The box opens one hour ahead of the current time and has no seconds field, so every code lands on a whole minute and the long time format always ends in :00.
Say your computer is set to New York time and you pick 8:00 PM on Saturday 14 November 2026. That moment is 01:00 UTC on Sunday 15 November, so every code uses 1794704400, for example <t:1794704400:F>. A member in Los Angeles sees 5:00 PM on Saturday, one in London sees 1:00 AM on Sunday and one in Tokyo sees 10:00 AM on Sunday. If the event is fixed in another city's time, convert it first with the Time Zone Converter, or the code will be off by the gap between the two zones.
Why can the preview differ from what Discord shows?
Your browser formats the preview in its own language, and Discord formats the same code with each reader's app language and time zone. Expect small differences in word order, month names or 12-hour and 24-hour clocks, while the moment itself stays the same for everyone.
The Relative line is an approximation the tool calculates itself. It counts a month as 30 days and a year as 365 days and rounds to the nearest whole unit, so an event 45 days away previews as "in 2 months" and one 360 days away as "in 12 months". The preview refreshes every 30 seconds, while Discord keeps its own relative text live in the message and may word it differently.
What mistakes stop a Discord timestamp from working?
Discord expects seconds. A 13-digit value copied from JavaScript's Date.now() is in milliseconds and points to a date tens of thousands of years away, so drop the last three digits. Codes typed inside backticks or a code block stay as raw text, so keep them outside any code formatting.
A code stores one fixed moment. If the event moves, edit the message and paste a fresh code, since the old one keeps pointing at the original time. For announcements, two codes side by side work well, such as <t:1794704400:F> (<t:1794704400:R>) for the full date followed by a countdown. A bare <t:1794704400> with no letter displays in the f style, and the Unix Timestamp Converter turns any of these numbers back into a readable date.