A community manager scheduling a game night at 8pm Eastern needs every member to see the correct local time. Instead of posting "8pm EST" and forcing people in London, Tokyo, and Sydney to do the math, they paste a Discord timestamp code. Each reader sees the event time adjusted to their own timezone automatically.
Esports tournament organizers use Discord timestamps in channel pins and announcements. A tournament starting at 18:00 UTC shows as 1pm in New York, 7pm in Berlin, and 3am in Tokyo for each viewer without any manual conversion.
Discord bot developers test timestamp formatting before deploying commands. Instead of running a bot locally to check output, they paste a date into this generator, copy the code, and drop it into a test channel to verify the rendering.
Streamers and content creators share stream schedules across global audiences. A YouTube premiere at 3pm Pacific becomes a clickable, timezone-aware timestamp in Discord that shows "in 4 hours" for one viewer and "tomorrow at 11am" for another.
Discord supports a special markdown syntax for timestamps: <t:UNIX_TIMESTAMP:STYLE>. The Unix timestamp is the number of seconds since January 1, 1970 at 00:00:00 UTC. When Discord's client encounters this code in a message, it converts the timestamp into a localized date or time string based on the viewer's timezone and language settings.
There are seven format styles, each controlled by a single letter after the colon. The style determines whether the output shows just the time, just the date, both, or a relative phrase like "in 3 hours." The relative style (R) updates live as time passes, so a message saying "starts in 2 hours" will eventually say "started 30 minutes ago" without anyone editing the message.
The Unix timestamp is always in UTC. Discord handles the offset calculation for each viewer. This means you only need to generate one code, and every reader sees the correct local time. If you have a 13-digit millisecond timestamp (common in JavaScript), divide by 1000 to get the 10-digit seconds value Discord expects.
Input
March 6, 2026 at 12:00 PM UTC
Output
<t:1772956800:F> renders as "Friday, March 6, 2026 12:00 PM" for a US Eastern viewer
Long date/time format (F) includes the weekday
Input
December 31, 2026 at 11:59 PM UTC
Output
<t:1798195140:R> renders as "in 5 months" and updates automatically
Relative format (R) is live-updating and works well for countdowns
Input
July 4, 2026 at 9:00 AM Pacific (UTC-7)
Output
<t:1751648400:t> renders as "9:00 AM" for a Pacific viewer, "12:00 PM" for an Eastern viewer
Short time format (t) shows only the time portion
Pitfalls to avoid
Discord timestamp format reference
What is a Discord timestamp?
A Discord timestamp is a special code in the format <t:UNIX_SECONDS:STYLE> that Discord automatically converts into a localized date or time string for each viewer. Everyone sees the time in their own timezone without any manual conversion.
Do Discord timestamps work in bot messages?
Yes. Discord timestamps work in regular messages, channel topics, role descriptions, bot embeds, and webhook payloads. No special API call is needed. The code is just text that Discord's client parses and renders.
How do I get a Unix timestamp for Discord?
Use the datetime picker on this page. It converts your selected date and time into a Unix timestamp in seconds. If you have a timestamp in milliseconds (13 digits), divide by 1000 to get the 10-digit seconds value Discord expects.
Why does my timestamp show the wrong time?
The most common cause is using milliseconds instead of seconds. Discord expects a 10-digit Unix timestamp in seconds. If your number has 13 digits, divide by 1000. Another cause is entering the wrong timezone for your event.
Can I use multiple timestamps in one message?
Yes. You can include as many timestamp codes as you want in a single message. For example, you could write "The sale starts <t:1717243200:F> and ends <t:1717502400:F>" to show both the start and end times.
Does the relative timestamp format update automatically?
Yes. The R style format updates live as time passes. A message saying "in 2 hours" will eventually say "starting now" and then "30 minutes ago" without anyone editing the message. This makes it useful for countdowns and event announcements.
What happens if I omit the format style?
If you write <t:1700000000> without a trailing colon and style letter, Discord defaults to the short date/time format (f), which shows something like "November 14, 2023 10:13 PM." This is the same as explicitly using <t:1700000000:f>.
Do Discord timestamps respect the viewer's language?
Yes. The exact wording depends on the viewer's Discord locale setting. A viewer with French locale will see "lundi 11 mai 2026 21:01" for the same F-format code that an English viewer sees as "Monday, May 11, 2026 9:01 PM."
This generator converts your selected date, time, and timezone into a Unix timestamp using the IANA Time Zone Database. Discord handles the final rendering based on each viewer's locale and timezone settings. The generated codes are plain text and require no API calls or bot permissions to function.