ToolNestFree Discord Timestamp Generator
Last updated: October 25, 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.
| Style | Code to paste | Renders 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.
✓ Free forever · ✓ No signup · ✓ Tool inputs stay in your browser — never sent to our servers.
How to Use the Discord Timestamp Generator
- 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.
- 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.
- 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.
- 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.
- 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.
- 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?
- All 7 official styles in one table — t, T, d, D, f, F, and R, each with its rendered example and a one-click copy button, instead of a single-format generator that makes you re-pick for every style.
- Timezone-aware conversion — a full timezone picker (UTC offsets from UTC−12 to UTC+14, including half-hour zones like India and Nepal) converts your wall-clock time to the correct Unix seconds, so an event announced in one timezone lands at the right moment everywhere.
- Reverse decoder included — paste a <t:...> tag or a raw 10-digit (or 13-digit millisecond) Unix value and get the moment back in your local time, in UTC, and as a relative time. Most generators only build tags; this one also reads them.
- Live relative preview — the R format's 'in 3 days' or '2 hours ago' rendering updates as you change the date, so you can sanity-check a countdown before you post it.
- Quick presets — right now, in 1 hour, and tomorrow at the same time cover the three moments people generate most, without calendar-picking.
- No bot, no permissions, no signup — Discord renders these tags natively, so the generated code works in any server, channel, embed, or webhook payload the moment you paste it.
Common Use Cases
- Announcing a global game night: Your server spans Los Angeles, London, and Sydney, and 'Friday 8pm' means three different moments. Generate the F tag for Friday 8pm Los Angeles time and post it once: every member sees Friday 8pm in their own timezone, and the R tag next to it counts down live until the event starts. No follow-up questions about timezones in the chat.
- Posting a deadline that counts itself down: A submission deadline posted as 'closes
- Reading a timestamp someone else posted: A mod posts a tag and you want to know when that is for you: paste it into the decoder and get the moment in your local time, in UTC, and as a relative time. Faster than opening a timezone converter and retyping the date.
- Scheduling recurring announcements via webhook: A webhook that posts weekly reminders can embed a pre-generated tag for each week's event time. Because the tag is just text, it survives scheduling, templating, and reposting — the rendering happens on Discord's side at read time, so the same payload stays correct for every reader.
Discord Timestamp Generator vs Alternatives
- Single-format timestamp generators (the current top results): Most of the small tools ranking today generate one style at a time or a fixed set without a timezone picker, so the common failure — right wall-clock time, wrong timezone — is built in. This page shows all seven styles at once, converts through your chosen timezone, and decodes tags back, which covers both directions of the job.
- HammerTime and sesh.fyi-style generators: The well-known community generators are solid single-purpose pages with good format previews; sesh.fyi in particular is widely linked from guides. What they do not do in one place is decode a pasted tag back to a moment or offer the quick presets — this page adds both without losing the one-click copy flow.
- Discord bots with time commands: Bots like MEE6 or Carl-bot can post timestamps through slash commands, which is convenient if the bot is already in your server. The trade-off is bot permissions, setup, and a dependency on the bot staying online; a generated tag needs none of that and works in DMs, where bots cannot post.
- Timezone converter sites: A general timezone converter answers 'what time is 9pm PT in London' but gives you a sentence, not a paste-ready tag — you still have to build the <t:...> syntax and compute the Unix seconds yourself. This generator skips the middle step: pick the moment, copy the tag.
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.