ToolNest logoToolNest.

Free Discord Timestamp Generator

Last updated: October 30, 2026

Quick answer: Discord has a built-in trick most servers never use: paste a tag like <t:1735689600:F> into any message and every reader sees that moment rendered in their own timezone, in their own date format — no bot, no plugin, no timezone math in the chat. This free Discord timestamp generator builds those tags for you: pick a date, time, and timezone, and it returns all seven official Discord timestamp formats (short time, long time, short date, long date, short date-time, long date-time, and the live-updating relative format) with one-click copy for each. It also runs in reverse: paste a tag or a raw Unix timestamp you found in a message and it tells you the exact moment it means. Everything runs in your browser; nothing is posted to Discord until you paste it yourself.

StyleCode to pasteRenders as (example)

How it works: Discord renders <t:UNIX:STYLE> tags itself, so the tag is just a Unix timestamp (seconds since 1 January 1970, UTC) plus one style letter: t short time, T long time, d short date, D long date, f short date and time (the default when the style is left off), F long date and time, R relative time that counts up or down live. The timezone you pick here only affects how your chosen wall-clock time is converted to Unix seconds — readers always see the moment in their own timezone. Tags work in regular messages, embeds, and webhook payloads; they do not need a bot or any permission.

🔒 100% Private: Data never leaves your device.

✓ Free forever  ·  ✓ No signup  ·  ✓ Tool inputs stay in your browser — never sent to our servers.

Try next: Unix Timestamp Converter · Days Between Dates · Morse Code Translator

How to Use the Discord Timestamp Generator

  1. Pick the date and time of the moment you want to announce — an event start, a deadline, a raid time, a giveaway draw. The date and time pickers default to today at noon so you can edit rather than start from scratch.
  2. Set the timezone to the timezone that date and time are written in — your own, or the event's local timezone. This is the step most generators skip, and it is the one that matters: 9pm in Los Angeles and 9pm in London are 8 hours apart, and the tag must carry the right Unix seconds.
  3. Read the table: all seven Discord timestamp formats for your moment, each with its copy button. Use F (long date and time) for announcements, R (relative) for countdowns — 'starts in 2 hours' — because R keeps counting live without you editing the message.
  4. Press the Copy button on the row you want, paste the tag into any Discord message, and send it. Every reader sees the moment in their own timezone and format; you do not need to add 'PT/ET' conversions to the message.
  5. For a quick moment, use the presets: Use right now fills in the current time, In 1 hour jumps ahead an hour, Tomorrow, same time moves the date one day forward. The table updates live as you change any field.
  6. To read a tag someone else posted, paste it — or just its Unix number — into the Decode box and press Decode it. The tool shows the exact moment in your timezone, in UTC, and as a relative time, so you can answer 'when is that for me' without doing the math.

Why Use Our Discord Timestamp Generator?

Common Use Cases

Discord Timestamp Generator vs Alternatives

Most timestamp generators build you one code and leave the timezone question to you — which is where the mistakes happen. This page converts through your timezone, shows all seven styles at once, previews the live relative rendering, and reads tags back. For an announcement that has to be right in every reader's timezone, that is the whole job in one page.

Frequently Asked Questions

How do I make a Discord timestamp?
Pick a date, time, and timezone in the generator above, then copy one of the seven codes from the table — for example <t:1735689600:F> — and paste it into any Discord message. Discord replaces the code with a formatted date and time when the message sends. No bot or special permission is needed.
What are all 7 Discord timestamp formats?
t is short time (9:41 PM), T is long time with seconds (9:41:30 PM), d is short date (01/01/2025), D is long date (January 1, 2025), f is short date and time (January 1, 2025 9:41 PM, and the default when you leave the style off), F is long date and time with the weekday (Wednesday, January 1, 2025 9:41 PM), and R is relative time (in 2 hours, 3 days ago) that updates live. The table above shows all seven for your moment.
Why does my Discord timestamp show the wrong time?
Almost always because the timezone was wrong when the tag was made: the Unix seconds in the tag encode one absolute moment, and Discord renders that moment in each reader's timezone. If you picked 9pm but left the generator on UTC while you meant Los Angeles time, the tag is 8 hours off for everyone. Rebuild it with the timezone set to the timezone your 9pm was written in — that is exactly what this generator's timezone picker is for.
What is the difference between and ?
Lowercase f is the short date-time: January 1, 2025 9:41 PM. Uppercase F is the long date-time: Wednesday, January 1, 2025 9:41 PM — the same moment with the weekday added. Discord also treats a tag with no style letter at all, <t:1735689600>, as f. Use F for formal announcements where the weekday helps people plan, and f everywhere else.
How does the relative timestamp (R) work?
The R style renders as a live relative time — 'in 2 hours', '3 days ago' — and Discord updates it as time passes, without anyone editing the message. That makes it the right choice for countdowns ('the event starts ') and for 'posted 2 hours ago' markers. It counts from the same Unix seconds as every other style; only the display is relative.
Can I use Discord timestamps in embeds or webhooks?
Yes — the <t:...> syntax is rendered by Discord's message renderer, so it works in regular messages, bot embeds, and webhook payloads alike. If a tag shows up as raw text instead of a date, the message was sent through a client or bridge that does not render Discord markdown — the tag itself is still valid.
What is a Unix timestamp, and why seconds?
A Unix timestamp counts seconds since 1 January 1970, 00:00:00 UTC — so 1735689600 is 1 January 2025, 00:00:00 UTC. Discord uses seconds (10 digits) in its tags; if you paste a 13-digit millisecond value from a developer tool, this generator's decoder divides by 1,000 first. The epoch is why tags from before 1970 or far in the future behave oddly in some clients.
Do Discord timestamps work without a bot?
Yes. Timestamp rendering is built into Discord itself — the feature shipped as part of Discord's message formatting, not as a bot feature. Any user can paste a <t:...> tag into any channel they can write in, and every reader sees it localized. Bots use the same syntax because it is the same renderer, not because bots own it.
Can I make a timestamp for a timezone other than my own?
Yes — that is the main reason the timezone picker exists. Set it to the timezone the event's wall-clock time is written in, not your own timezone. If a tournament starts at 9pm London time and you live in Los Angeles, pick the London offset and enter 9pm: the tag carries the correct Unix seconds, and every reader — including you — sees it rendered in their own timezone. The mistake to avoid is entering 9pm while the picker still sits on your home timezone.
Why does my timestamp show up as raw text instead of a date?
The tag only renders in Discord's own message renderer. It stays as raw text if you wrap it in backticks (which forces a code block), if the message goes through a bot, bridge, or third-party client that does not render Discord markdown, or if an extra character breaks the syntax — a space inside the brackets or a missing closing bracket is enough. Paste the code exactly as copied, without backticks, and test it in a private channel first.
Do Discord timestamps handle daylight saving time automatically?
Discord renders the absolute moment, so once a tag exists, daylight saving changes nothing — every reader sees the right local time whenever they open the message. The catch is at generation time: this generator converts with a fixed UTC offset, so you must pick the offset in effect on the event's date, not today's. Los Angeles is UTC-7 in summer and UTC-8 in winter; using the winter offset for a July event would put the tag an hour out. Check the offset for the event date before you copy.
Which timestamp format should I use for an event announcement?
Use F and R together: F gives the full date, weekday, and time ('Wednesday, January 1, 2025 9:41 PM') so nobody has to guess the day, and R next to it ('in 2 days') gives the live countdown. One format alone is weaker — F alone never says how soon the event is, and R alone never says which day it falls on. For a deadline, the same pair works: F is the exact cutoff, R is the countdown that flips to '3 hours ago' on its own after the deadline passes.
Can I use Discord timestamps in channel names, nicknames, or statuses?
No. Tags render only inside message content — regular messages, embeds, and webhook payloads. Channel names, nicknames, custom statuses, and role names show the raw text, because those fields are not passed through Discord's message renderer. If you need a time in a channel name, write it out as plain text ('event-friday-8pm') and put the live tag in a pinned message in that channel.
Why does a relative timestamp disagree between two people reading the same message?
The R style is computed from each reader's own device clock, so it is only as right as that clock. If your phone's clock runs five minutes fast, 'in 2 hours' reads a few minutes differently for you than for everyone else — while the F style, which shows the absolute moment, matches for all readers. If one member reports a wrong relative time, their device clock is the first thing to check, not the tag.