Why use a Discord timestamp tag instead of just typing the date?

Discord timestamp tags render in each viewer's local time zone automatically. If you type 'Stream starts at 8 PM EST' a viewer in Europe has to do mental math to figure out when that is for them. If you type the equivalent timestamp tag, Discord shows it as '2:00 AM CET' to the European viewer and '5:00 PM PST' to the West Coast viewer — same moment, no math. The relative format also auto-updates: 'starts in 2 hours' becomes 'started 30 minutes ago' without anyone editing the message.

Will the timestamp work for everyone in my server?

Yes, for anyone using Discord — desktop, web, mobile, all platforms support timestamp rendering. The viewer's Discord client looks at their device's local time zone and formats the timestamp accordingly. The only requirement is that the viewer is using a Discord client from roughly 2021 or later, which covers essentially everyone.

Can I use Discord timestamps in a bot's messages?

Absolutely — bots can produce timestamp tags the same way as humans. Just include the formatted string ' ' in the message content your bot sends. Many bot developers store event times as Unix timestamps internally and let Discord do the locale formatting client-side, which avoids the eternal headache of figuring out each user's time zone preference.

Can I edit a Discord timestamp message?

Yes. Editing a message that contains a timestamp tag works like editing any message — you can change the timestamp, add more, or remove them. The relative format (:R) is particularly useful precisely because the same Unix value renders differently as time passes, so you often don't need to edit at all: a message saying 'starts in 3 hours' will eventually say 'started 5 minutes ago' on its own.

What time zone does Discord use to display the timestamp?

The viewer's local time zone, as determined by their device — not the server's, not yours, not Discord's. This is the whole point of using a timestamp tag: each person sees the time in the zone that's natural for them.

Why don't all my friends see the same time?

That's the feature, not a bug. The timestamp tag represents a single moment in absolute time. Each viewer sees that moment expressed in their own time zone. So if you and a friend are in different time zones, you'll see different wall-clock times for the same tag — they're showing the same instant, just relative to each of you. If you actually want everyone to see the same string, type it as plain text instead of using a timestamp tag.

Discord Timestamp Generator — All 7 Formats, Live

Generate <t:UNIX:F> tags for Discord messages. Each viewer sees the time in their own zone, and the relative format auto-updates as time passes.

What are Discord timestamps?

Discord supports a special syntax for inline timestamps: <t:UNIX_TIMESTAMP:FORMAT>. When a viewer sees a message containing this tag, Discord's client converts it into a localized date or time string in that viewer's time zone. The relative format (:R) auto-updates as time passes, so a message saying "starts in 2 hours" will, two hours later, say "starting now" and then "30 seconds ago" — all without anyone editing the message.

This is useful any time you're communicating about a moment in time across time zones. Server announcements, event schedules, deadlines, "when does the sale end" questions — anything that historically required typing a string like "8 PM EST (1 AM CET) (5 PM PST)" can be replaced with a single timestamp tag that does the conversion automatically for everyone.

The seven format codes

Discord supports seven format codes. The letter at the end of the tag determines how the date is rendered:

Code	Style	Example output (English locale)
t	Short time	9:01 PM
T	Long time	9:01:00 PM
d	Short date	05/11/2026
D	Long date	May 11, 2026
f	Short date/time (default if no code given)	May 11, 2026 9:01 PM
F	Long date/time	Monday, May 11, 2026 9:01 PM
R	Relative time	in 3 hours, 2 days ago

If you omit the format code entirely (just <t:1735689600>), Discord defaults to :f (short date and time). The exact wording for each format depends on the viewer's locale — a viewer with their Discord set to French will see "lundi 11 mai 2026 21:01" for the same :F code that an English viewer sees as "Monday, May 11, 2026 9:01 PM".

Common use cases

Different formats fit different situations:

Event announcements: :F gives the full date and weekday, which is perfect for "the tournament is on Monday, May 11, 2026 9:01 PM your time."
Countdowns to a stream or launch: :R auto-updates, so a single message says "in 4 hours" and later "starting now" without an edit.
Deadline reminders: :f for the wall-clock date plus :R for the urgency. The combination "Due May 15 (in 4 days)" tells the reader both the absolute time and the relative urgency.
Service status posts: :T shows the second-precision time, useful for "Service was restored at 9:01:00 PM."
Daily schedules: :t for time only, when the date is implicit ("the daily standup is at 9:00 AM").

How to use them in messages

The workflow is: pick a date in this generator, copy the tag, paste it into your Discord message. You can mix multiple tags in one message — for example, The sale ends <t:1735776000:R> (<t:1735776000:F>) renders as "The sale ends in 2 days (Sunday, January 4, 2026 12:00 AM)" — relative urgency with the absolute time as a backup.

The tag works inside any text message in any channel where you can post, and it renders the same in DMs as in server messages. There's no need for special formatting markers around it.

For Discord bot developers

If you're building a bot, generate timestamp tags the same way: take a Unix timestamp (seconds, not milliseconds), wrap it as <t:UNIX:FORMAT>, and include the resulting string in your message content. Most Discord libraries (discord.js, discord.py, JDA, serenity) don't have a special API for this because no API is needed — it's just text.

A common pattern: store event times as Unix timestamps in your database, and render them as Discord tags when posting messages. This pushes the locale-specific formatting work onto Discord's clients, which avoids the perpetual headache of "what time zone does this user prefer?" in your bot's settings.

Worth noting: timestamps in embeds (the timestamp field) are different from inline timestamp tags. Embed timestamps render as a footer date in the embed itself, while <t:> tags work inline in any text. Use the embed field for "this embed describes an event at this time," and use inline tags for "this sentence references this moment."

Limitations and edge cases

No timezones in the past or future: Discord uses the viewer's current time zone for all renderings, even for historical dates. If you tag a date that happened during DST in a region that changed its DST rules since, the rendering may not match what was actually displayed locally on that day.
Negative timestamps mostly work: dates before 1970 (Unix epoch 0) generally render correctly across Discord clients, but very old dates can occasionally trigger formatting bugs in older client versions. Modern Discord handles them fine.
Year 9999+ doesn't work: Discord's parser caps timestamps at the JavaScript Date max around year 9999. Very large Unix values render as a literal string instead of a date.
Locale dependency: the exact wording is the viewer's locale, not yours. A French viewer sees French dates, a Japanese viewer sees Japanese dates — usually a feature, occasionally surprising if you're used to English-only servers.
Spoiler tags: wrapping a timestamp in ||spoiler tags|| hides the rendered output but the original tag syntax shows briefly while loading.

Related tools

If you're working with timestamps for things other than Discord, you might also need:

Embed this tool on your site

If you maintain bot documentation, a server guide, or any community resource page, you can embed this timestamp generator directly — it's free to use on any site. Click Embed this tool at the bottom of the generator to copy the iframe snippet, and keep the credit link that ships with it.

Discord Timestamp Generator

Use it in a message