Discord Time Converter & Timestamp Generator

A Discord timestamp is a special markdown format (<t:UNIX:FORMAT>) that renders as a clickable, timezone-aware time/date in chat. Discord automatically converts it to each viewer's local timezone — so a timestamp posted by someone in NYC shows up correctly for someone in Tokyo. Useful for scheduling events, posting deadlines, and building bots that announce times.

Yes — it's a Discord time converter both ways. Enter any date and time in your own timezone and it converts it to Discord's <t:UNIX> code, which Discord then shows every viewer in their local time. You can also paste an existing <t:> code to read what time it represents.

:R is "Relative" (in 2 hours / 3 days ago — auto-updates as time passes). :F is "Long Date/Time" (Sunday, May 3, 2026 at 9:41 PM). :t is "Short Time" (9:41 PM). :T is "Medium Time" (9:41:30 PM). :d is "Short Date" (05/03/2026). :D is "Long Date" (May 3, 2026). :f is "Short Date/Time" (May 3, 2026 at 9:41 PM) — also the default if you omit the format suffix entirely. Discord also supports :s (05/03/2026, 9:41 PM) and :S (05/03/2026, 9:41:30 PM), which most older format guides still leave out. Every example here is how it renders on a US locale; the exact punctuation and order change with each viewer’s own locale.

Yes. Discord stores the timestamp as a Unix epoch (seconds since 1970 UTC) and renders it in each viewer's configured timezone client-side. Post a timestamp at 3pm UTC and a viewer in Los Angeles sees it as 8am, while a viewer in Sydney sees it as 1am the next day. No manual timezone conversion needed.

Calculate the Unix timestamp in your bot code (Math.floor(Date.now() / 1000) for "now", or new Date('2026-05-03').getTime() / 1000 for a specific date) and embed it as `<t:${unix}:R>`. With VibeBot, you can build commands like /remindme that automatically post relative timestamps when triggered — no code, just describe the behavior.

Almost always daylight saving, and it matters which end it happened at. If the code is wrong for everyone, it was generated against a fixed abbreviation like EST while the region was actually observing EDT, which bakes an hour of error into the Unix number — generate against a named zone such as America/New_York instead, which resolves DST correctly year-round. That is why the timezone selector above lists named zones rather than abbreviations. If the timestamp looks wrong to only one person, the problem is on their machine: Discord renders timestamps using the viewer’s own device clock and timezone, so switching that device to set date, time and timezone automatically fixes it.

Not in the way most people mean. A <t:> code is one fixed moment in time, so even where the syntax renders it shows a single frozen date rather than your current local time — and the relative format counts away from that instant instead of ticking like a clock. There is also no legitimate way to automate it: Discord’s API gives bots no access to read or write a user’s About Me, so anything advertising an auto-updating bio clock is driving your account with a selfbot, which violates Discord’s Terms of Service and risks a ban. The practical options are a static line naming your zone, such as "UTC-5 (America/Toronto)", or a single timestamp code pinned to a representative hour that viewers read in their own local time.

No. The syntax encodes one specific Unix second, so there is no recurring form — a timestamp for last Monday stays pointed at last Monday forever. For a genuinely repeating event you have two routes. A bot can post a freshly generated timestamp on a schedule, or you can use Discord’s built-in Scheduled Events, which support weekly, monthly and custom recurrence — the Repeats dropdown offers Daily, Weekly, Monthly and Custom, so every other week needs Custom rather than a preset — and they already show every member the time in their own timezone. Scheduled Events are the no-code answer for "every Monday at 8pm". Note that a recurring event runs until you delete it; Discord does not support an end date or an occurrence count on one.

Only through a bot that renames the channel, and it will never look live. Timestamp markdown does not render in channel names, and Discord applies a much stricter rate limit to a channel’s name and topic than to normal API calls — developers have measured it from the rate-limit responses at roughly two changes every ten minutes. That is why countdown bots display a coarse "about 2 hours left" rather than ticking seconds. The limit is not in Discord’s published rate-limit documentation, so treat the exact figure as something that can change rather than something to hard-code.

Discord added a native @time feature in its 4 February 2026 update. Type @time in the message box and Discord offers a picker for the timestamp formats, so for the simple case you no longer need an external generator at all. The limit worth knowing is that it is desktop only — the patch notes say "On Desktop", and no mobile rollout has been announced since — so phone and tablet users still need a generator, which is what this page is. The selector above also lets you enter a time in a zone you are not currently in.

Further out than you are likely to need. The format is plain seconds since 1970, and Discord's clients handle dates well past 2038 — the classic 32-bit Unix cutoff does not apply to them. Past dates work too, back through 1970 and before.

Yes — embed fields, descriptions, and even titles all support the <t:> syntax. Useful for event announcements, leaderboards with last-update times, and bot status messages with "started X ago" indicators.

Yes. Timestamps are plain text markdown, so paste the copied <t:…> code into the Discord mobile app exactly like on desktop — it renders as local time for every viewer on every platform. This page also works fine from a phone browser, so you can generate the code on mobile too.

Yes — a Discord timestamp is just a Unix timestamp (seconds since 1970) wrapped in <t:…:FORMAT>. If you already have the Unix number, wrap it yourself: <t:1735689600:F>. If you have a date and time instead, use the tool above and it computes the Unix value for you.

Bots can post timestamps, but you don't need one just to convert times — the markdown works from any account, which is what this tool generates. Where a bot earns its place is scheduling around those times: automatic event announcements and reminders. VibeBot's reminder feature does exactly that.