- How do Discord timestamps work?
- A Discord timestamp is a tag like <t:1798201800:F>. The number is a UNIX time: the seconds since midnight UTC on January 1, 1970. It names one exact moment, with no timezone attached. When Discord shows the message, each reader's app turns that moment into their own local time and language. So one code reads as 6:00 PM on Friday, December 25, 2026 in Mumbai, 7:30 AM in New York, and 12:30 PM in London. Nobody has to do timezone math.
- What do the seven style letters mean?
- The letter after the second colon picks the format. t is short time (6:00 PM), T is long time with seconds (6:00:00 PM), d is short date (12/25/2026), D is long date (December 25, 2026), f is short date and time (December 25, 2026 at 6:00 PM), F adds the weekday (Friday, December 25, 2026 at 6:00 PM), and R is relative (in 3 months). With no letter at all, <t:1798201800> shows the f style. Each reader's language settings decide the exact wording and date order, so a reader in Germany sees 25.12.2026.
- Which style should I use for an event announcement?
- Long date/time (F) is the safest. It includes the weekday, and that catches the most common mistake: an event late on Friday in one country is Saturday morning in another. Many mods post two codes side by side, like <t:1798201800:F> (<t:1798201800:R>), so readers see both the exact time and a countdown. The relative style updates by itself: it says "in 2 hours," then "in 5 minutes," then "10 minutes ago."
- What happens on the days clocks change for daylight saving?
- Two local times need care. In spring, clocks jump forward, so 2:30 AM on March 8, 2026 never happens in New York. Most tools quietly give you a code for the wrong hour. This one moves the time forward to 3:30 AM EDT and tells you. In autumn, clocks go back, so 1:30 AM on November 1, 2026 happens twice. This tool uses the first one (1:30 AM EDT, UNIX 1793511000) and says so. If you meant the second one, an hour later, the code is <t:1793514600:F>.
- Why does the preview show a different time than I typed?
- The previews show the code the way Discord shows it to you, in your own timezone. If you live in London and set 8:00 PM in America/New_York, the preview reads 1:00 AM the next day, because that's when the event happens for you. Your New York friends see 8:00 PM. The UTC line under the UNIX number is a neutral check: 8:00 PM EDT on July 4, 2026 is 2026-07-05 00:00 UTC.
- Can I make a timestamp for a date before 1970 or after 2038?
- Yes. Before 1970 the UNIX number is negative, so midnight UTC on December 31, 1969 is <t:-86400:F>. After 2038 nothing breaks either. Some old systems store time as a 32-bit number that runs out at 03:14:07 UTC on January 19, 2038, but that limit doesn't apply here or in Discord. 03:15 UTC that day is 2147483700, and dates run all the way to December 31, 9999.
- Do I need a bot or special permissions to use timestamps?
- No. The timestamp tag is part of Discord's normal message formatting, the same as bold or spoilers. Anyone who can type in a channel can use one, in servers, DMs, threads, and event descriptions, on desktop and mobile. You don't need to invite a scheduling bot, give it permissions, or learn slash commands. Copy the code from this page and paste it. Nothing you enter here is sent anywhere; the math runs in your browser.
- Why is my code showing as plain text instead of a time?
- Check three things. The tag has to be exact: a less-than sign, t, colon, the number, an optional colon and style letter, then a greater-than sign, with no spaces. It can't be inside a code block or backticks, because Discord shows code blocks as raw text. And a few places outside normal messages, like usernames and some parts of bot embeds, show the raw tag instead of a time. Copying from the buttons here avoids typos.
