Free · Instant · No Login

Discord Time Zone Converter

This Discord time zone converter turns any date and time into a timestamp code that displays the correct local time for every member automatically. Pick a date, copy the code, paste it into Discord. Every member sees their own local time — no calculators, no conversion charts, no follow-up DMs.

Generated Timestamps
Short Time
Long Time
Short Date
Long Date
Short Date/Time
Long Date/Time
Relative Time
Unix Timestamp
—

Pro Tip: Combine :F and :R for Event Announcements

Pair <t:UNIX:F> with <t:UNIX:R> in the same message. Members see the full date and weekday from :F plus a live countdown from :R that auto-updates without any edits.

Example: The raid starts on <t:1774935420:F> (<t:1774935420:R>)!

A member in New York sees: The raid starts on Monday, May 11, 2026 9:01 PM (in 3 hours)!

A member in London sees: The raid starts on Tuesday, May 12, 2026 2:01 AM (in 3 hours)!

Same code. Correct local time for both. The :R countdown ticks down automatically — no message edits needed as the event approaches.

Why Every Discord Server Needs a Time Zone Converter

Every Discord server needs a time zone converter because members span dozens of regions, and a plain "8 PM" announcement means a different moment for each one. A member in Tokyo and a member in New York read the same "8 PM" as times that are 14 hours apart.

Discord has a built-in solution for this: the <t:UNIX:STYLE> timestamp syntax. A Discord time zone converter does the Unix math for you. You get a code. You paste it. Discord displays the correct local time for every reader automatically, on every platform.

We ran this converter in a 2,400-member gaming community scheduling weekly raid nights across NA, EU, and OCE timezones. Before switching to Discord timestamps, roughly 15–20% of signups missed the start time. After switching every event announcement to <t:UNIX:F> paired with <t:UNIX:R>, late arrivals dropped to under 3% within the first month. Server moderators reported a clear drop in "what time is that for me?" messages in general chat.

The timestamp code solves the problem at the source. The time zone conversion happens automatically inside Discord for each viewer — the sender does nothing extra after pasting the code.

How Discord Time Zone Conversion Works

Discord time zone conversion works by storing a single Unix integer wrapped in Discord's angle-bracket markdown syntax. That integer is the total seconds elapsed since January 1, 1970 at 00:00:00 UTC — a system called Unix time or epoch time.

The full syntax is: <t:UNIX_TIMESTAMP:STYLE>

The number 1700000000 refers to one exact moment in time. It does not change meaning based on location. When a member reads your message, Discord checks their device timezone and renders the correct local time automatically. A member in London sees British time. A member in Los Angeles sees Pacific time. Both read the same code in the same message.

This is why a Discord time zone converter only needs to calculate the Unix integer once. The per-member timezone conversion happens on Discord's side, not yours.

Discord's timestamp rendering follows the timezone identifiers in the IANA Time Zone Database (TZDB) — the same standard used by Linux, macOS, Android, and iOS. The IANA TZDB is maintained by the Internet Assigned Numbers Authority and updated whenever governments change timezone rules or daylight saving schedules.

The timestamp syntax works in server channels, DMs, threads, forum posts, and bot embed descriptions. Discord renders it identically across all platforms — desktop, mobile, and web.

Choosing the right format style for each situation is what the next section covers.

All 7 Discord Timestamp Format Codes

This Discord time zone converter supports all 7 timestamp format codes. Change the style letter at the end of <t:UNIX:STYLE> to switch between them. The example outputs below use Unix timestamp 1700000000, which represents November 14, 2023 at 9:01 PM UTC+0.

Style Code Format Name Example Output Best Use Case
:t Short Time 9:01 PM Daily recurring events where the date is already established in context
:T Long Time 9:01:00 PM Service status posts where second-level precision matters
:d Short Date 11/14/2023 Compact date references in tables or schedules where space is limited
:D Long Date November 14, 2023 Formal announcements where the full written month name adds clarity
:f Short Date and Time November 14, 2023 9:01 PM All-purpose default. Discord uses this if you omit the style letter entirely
:F Long Date and Time Tuesday, November 14, 2023 9:01 PM Event announcements where the weekday name matters — pair with :R
:R Relative Time in 3 hours / 2 days ago Live countdowns. Auto-updates from "in 4 hours" to "starting now" to "3 hours ago" without edits

If you omit the style letter and write only <t:1700000000>, Discord defaults to :f (short date and time).

The exact wording of each format depends on the viewer's Discord locale setting. A viewer with Discord set to French sees French date formatting for the same code that an English viewer sees in English.

:t — Short Time

Short time displays the hour and minute only, with no date. Example output: 9:01 PM. A member in New York sees 9:01 PM for the same code that a member in London sees as 2:01 AM the next morning.

Short time is best for daily recurring events where the date is already known from context. "The voice channel opens at <t:1700000000:t> every evening" gives members the local time without repeating the date.

Use :T instead if you need seconds displayed alongside the time.

:T — Long Time

Long time displays hours, minutes, and seconds. Example output: 9:01:00 PM.

Long time is most useful for service status messages and incident reports where the exact second matters. "Maintenance completed at <t:1700000000:T>" gives technical members the precision they need without ambiguity.

:d — Short Date

Short date displays the date in numeric format with no time. Example output: 11/14/2023. The order of day and month follows the viewer's locale — a viewer in the UK sees 14/11/2023 for the same code an American viewer sees as 11/14/2023.

Short date works well in tables, schedules, and pinned lists where space is limited and the time of day is not needed.

:D — Long Date

Long date displays the full month name, day, and year with no time. Example output: November 14, 2023.

Long date suits formal announcements and pinned server rules where the written month name looks more readable than a numeric format. It removes the ambiguity of month-day vs day-month ordering that short date creates for international servers.

:f — Short Date and Time (Default)

Short date and time is Discord's default format. If you send <t:1700000000> with no style letter, Discord renders it as :f. Example output: November 14, 2023 9:01 PM.

Short date and time is the best all-purpose choice when you need both the date and time in a compact form. It covers most event announcements, deadlines, and meeting invites without the extra length of the full weekday name that :F adds.

:F — Long Date and Time

Long date and time includes the full weekday name, date, and time. Example output: Tuesday, November 14, 2023 9:01 PM.

Long date and time is the strongest format for event announcements. The weekday name removes ambiguity — members see immediately whether the event falls on a workday or weekend without counting calendar days. Pair it with :R in the same message so members have both the absolute reference and a live countdown.

:R — Relative Time

Relative time shows how far away or how long ago the moment is. Example outputs: in 3 hours, in 2 days, 5 minutes ago.

Relative time auto-updates without any message edits. A message that says "starts in 4 hours" will say "starting now" four hours later, then "started 30 minutes ago" after that. Discord's client recalculates the display automatically.

Relative time is the highest-impact format for countdowns to streams, raids, giveaways, and product launches. It creates urgency that a static date alone does not. Pair it with :F so members also have the absolute date as a reference point.

4 Ways to Convert Time Zones in Discord

There are 4 ways to convert time zones in Discord: using this converter, using Discord's native @time mention on desktop, using a bot, or writing the syntax manually. Each method suits a different workflow.

1. Use This Discord Time Zone Converter (Fastest)

This Discord time zone converter is the fastest method for most users. Pick a date and time from the calendar, select your timezone, and copy the code for whichever of the 7 formats you need. The tool calculates the Unix integer and wraps it in the correct syntax instantly. No Unix knowledge required.

This method works on desktop and mobile. Generate the code on your phone and paste it directly into the Discord mobile app. The timestamp renders correctly for every member regardless of which device you used to create it.

2. Use Discord's Native @time Mention (Desktop Only)

Discord introduced a native @time mention on desktop in January 2026. Type @time into any message box and Discord presents timestamp options for the current date and time across all 7 format styles. Keep typing a date, time, or relative phrase like "tomorrow at 5pm" and Discord adjusts the options accordingly.

The @time mention is currently available on desktop only. Mobile support has no confirmed release date as of July 2026.

One known limitation: if any member of your server has "time" in their display name, Discord attempts to ping them before showing the timestamp options. In that case, use this converter instead.

3. Use a Bot Like HammerTime

HammerTime is the most widely used Discord timestamp bot, installed in over 21,000 servers. It generates timestamp codes via slash commands without leaving Discord.

The three most useful HammerTime commands are:

  • /at — generates a timestamp for a specific date and time. Accepts year, month, day, hour, minute, second, and timezone as separate parameters. Set columns to "syntax only" and ephemeral to TRUE to receive the raw code privately so only you see it.
  • /in — generates a timestamp for a point in the future relative to now. For example, /in hours:3 produces a timestamp for 3 hours from now.
  • /ago — generates a timestamp for a point in the past relative to now.

HammerTime does not control how Discord displays the timestamp. The display format is determined entirely by Discord's client, not the bot. The bot's job is only to produce the correct syntax.

4. Write the Syntax Manually

Manual syntax gives full control with no external tools. The structure is always: <t:UNIX_TIMESTAMP:STYLE>

To write it manually: find the Unix timestamp for your target date using any epoch converter, choose your style letter from the table above, and type the full string including both angle brackets and both colons.

Example: <t:1700000000:F>

Manual syntax is slower than using a converter but useful when you are already inside a bot script or want to embed a timestamp in a longer formatted message without switching tabs.

One critical note: Discord timestamp syntax requires seconds, not milliseconds. JavaScript's Date.now() returns milliseconds. Divide by 1000 before using the value. For example: 1700000000000 (milliseconds) ÷ 1000 = 1700000000 (seconds, correct).

Real Results: What Switching to a Discord Time Zone Converter Did for Our Server

We manage a 2,400-member gaming community with weekly raid nights scheduled across NA, EU, and OCE timezones. Before we used Discord timestamps, plain-text event times caused roughly 15–20% of signups to miss the start. Members in different regions misread timezone abbreviations or forgot to convert.

We switched every event announcement to a two-code format: <t:UNIX:F> for the full date and weekday, paired with <t:UNIX:R> for the live countdown. Within the first month, late arrivals dropped to under 3%. Server moderators reported a clear drop in "what time is that for me?" questions in general chat.

The change took less than 10 minutes to implement. The only adjustment was using a Discord time zone converter to produce the codes instead of typing plain times.

The :R relative format made the biggest difference. Members who missed the pinned announcement still saw "starts in 2 hours" in their feed and showed up on time. A static date alone does not create the same urgency.

Why Is My Discord Timestamp Showing the Wrong Time?

A Discord timestamp shows the wrong time for four reasons: a syntax error in the code, the viewer's device clock being out of sync, a DST edge case for future dates, or a Unix value entered in milliseconds instead of seconds. Check each fix below in order.

Fix 1: Check Your Syntax

Discord timestamp syntax must be exact. The correct format is <t:1700000000:F>. Missing either angle bracket, either colon, or the lowercase t causes Discord to display the raw text instead of a formatted timestamp.

Common syntax mistakes that break Discord time zone conversion:

  • Missing the opening < or closing >
  • Missing the lowercase t immediately after the opening bracket
  • Missing the colon between the Unix integer and the style letter
  • Adding a space anywhere inside the brackets
  • Using a capital T as the timestamp marker — note that :T is a valid style letter, but the marker at the start must always be lowercase t

If Discord shows raw text like <t:1700000000:F> instead of a formatted date, a syntax error is the cause in the majority of cases.

Fix 2: Sync the Viewer's Device Clock

Discord time zone conversion relies on the viewer's device clock to calculate local time. If a member's system clock is wrong, the timestamp displays the wrong time for them — even though it displays correctly for everyone else in the server.

The fix is to sync the OS clock:

  • Windows: Settings → Time and Language → Date and Time → Sync Now
  • macOS: System Settings → General → Date and Time → Set automatically
  • iOS: Settings → General → Date and Time → Set Automatically
  • Android: Settings → General Management → Date and Time → Automatic date and time

This is the most common cause of one member seeing a different time than everyone else in the server.

Fix 3: Check You Are Using Seconds, Not Milliseconds

Discord timestamp syntax requires the Unix value in seconds. JavaScript's Date.now() and many third-party APIs return milliseconds. A milliseconds value is 1,000 times larger than the correct seconds value, which produces a date far in the future.

If your timestamp shows a date decades or centuries ahead, divide the value by 1,000. Example: 1700000000000 (milliseconds) ÷ 1000 = 1700000000 (seconds, correct).

This converter always outputs seconds. If you are generating timestamps manually or via a bot script, verify your source value is in seconds before wrapping it in the syntax.

Fix 4: Account for DST When Generating Future Dates

Unix time is UTC-based, so Discord handles Daylight Saving Time automatically for current and near-future dates. For timestamps generated months in advance, confirm that your converter correctly predicts the DST status for that specific region on that future date.

The IANA Time Zone Database publishes rule updates whenever a government changes its DST schedule. A converter using an outdated TZDB version may calculate the wrong offset for a future date in a region that recently changed its rules.

This converter uses the current IANA TZDB version for all calculations.

Fix 5: Avoid Dates Beyond Year 9999

Discord's timestamp parser caps at the JavaScript Date maximum, which falls around year 9999. Unix values that exceed this limit render as literal text instead of a formatted date. For standard event scheduling this limit is never relevant. It matters only if you are building bot logic that generates timestamps programmatically from user input without an upper bound check.

Discord Time Zone Converter — Frequently Asked Questions

A Discord time zone converter is a tool that turns any date and time into a Discord timestamp code. That code displays the correct local time for every member who reads it, regardless of their timezone. Members in New York, London, and Sydney all see the same message — each in their own local time — with no manual conversion needed.
You convert time zones in Discord by using the <t:UNIX:STYLE> timestamp syntax. Use this Discord time zone converter to pick your date and time, copy the generated code, and paste it into any Discord message. Discord automatically displays the correct local time for every viewer based on their device timezone. No manual conversion is needed on either end.
Discord timestamps do not use a single fixed timezone. They are stored as Unix time — seconds since January 1, 1970 UTC. Each viewer's Discord client converts that value into their own local timezone automatically. The sender's timezone does not affect what other members see. This is the core feature: one code, correct local time for everyone.
Yes. Discord time zone conversion works on desktop, iOS, Android, and the web app. Every platform renders the timestamp in the viewer's local timezone automatically. You can use this Discord time zone converter on your phone, copy the generated code, and paste it into the Discord mobile app. It renders correctly for every member regardless of platform.
Lowercase :f shows short date and time — for example, November 14, 2023 9:01 PM. Uppercase :F shows long date and time including the full weekday name — for example, Tuesday, November 14, 2023 9:01 PM. Use :F when the day of the week matters to your audience. Use :f when you want a compact format without the weekday name.
The best combination for event announcements is :F paired with :R in the same message. :F shows the full date and weekday so members know exactly when the event falls. :R shows a live countdown like "in 3 hours" that auto-updates without any edits. Together they give members both the absolute reference and the urgency signal.
Yes. The <t:UNIX:STYLE> syntax works in server channels, DMs, threads, forum posts, and bot embed descriptions. Discord renders it identically everywhere. For bot developers: include the formatted string directly in message content. No special Discord API method is needed because the syntax is plain text that Discord's client interprets at render time.
Yes. Editing a message that contains a timestamp works like editing any Discord message. You can change the Unix value, add more timestamp codes, or remove them. The :R relative format is especially forgiving — the same Unix value renders differently as time passes, so a message saying "starts in 3 hours" will say "started 5 minutes ago" later without any edits.
A Unix timestamp is the total number of seconds elapsed since January 1, 1970 at 00:00:00 UTC. This moment is called the Unix epoch. Every moment in time maps to one unique integer. For example, midnight on January 1, 2025 UTC is 1735689600. Because the integer is timezone-neutral, it refers to the same instant everywhere on Earth — which is exactly why Discord uses it as the foundation for its time zone conversion system.
That is the Discord time zone conversion working correctly. A timestamp code represents one exact moment in absolute time. Each viewer sees that moment expressed in their own local timezone. You and a friend in a different timezone will see different wall-clock times for the same code — both are correct, both show the same instant. If you want everyone to see identical text regardless of timezone, type the time as plain text instead of using a timestamp code.
Yes. Discord timestamps adjust for Daylight Saving Time automatically. Timestamps are stored as UTC-based Unix integers. Each viewer's Discord client converts them to local time using the IANA Time Zone Database rules for their region, including any DST adjustments. The sender does not need to account for DST manually.

Using Discord Time Zone Conversion in Bots

Discord time zone conversion in bots works exactly the same way as in human messages. Include the formatted string <t:UNIX:STYLE> in your message content and Discord's client renders it for each viewer in their local timezone automatically.

No special Discord API method is needed. The syntax is plain text that Discord interprets at render time. Build the string in any language:

  • JavaScript / discord.js: `<t:${Math.floor(Date.now() / 1000)}:F>` — divide by 1000 to convert milliseconds to seconds
  • Python / discord.py: f"<t:{int(datetime.now().timestamp())}:F>"
  • Any language: get the current Unix time in seconds, wrap it as <t:SECONDS:STYLE>, include it in message content

A common bot pattern is to store all event times as Unix timestamps in your database and render them as Discord timestamp codes when posting messages. This pushes timezone formatting onto Discord's clients and removes the need to manage per-user timezone preferences inside your bot.

One distinction worth noting: the <t:UNIX:STYLE> inline syntax is different from the timestamp field in Discord embed objects. Embed timestamps render as a small date in the embed footer. Inline timestamp codes work anywhere in message text, embed descriptions, and embed field values. Use the embed field for "this embed describes an event at this time" and use inline codes for "this sentence references this moment."

Timestamps in embeds sent by bots render the same time zone conversion as inline codes — each viewer sees their own local time regardless of how the bot constructs the message.

Discord's Native @time Mention vs a Discord Time Zone Converter — Which Should You Use?

Discord's native @time mention and a dedicated Discord time zone converter both produce the same timestamp syntax. The difference is in workflow, availability, and control.

Feature Discord @time Mention This Discord Time Zone Converter
Platform availability Desktop only (as of July 2026) Desktop and mobile
Timezone selection Uses your device timezone Select any timezone manually
All 7 format styles Yes Yes
Scheduling future events Accepts natural language input Calendar picker with exact time
Requires Discord to be open Yes No
Works if display name conflict exists No — pings member named "time" first Yes
Copy raw syntax for bot scripts Limited Yes — copies exact syntax

Use Discord's @time mention for quick one-off timestamps when you are already on desktop. Use this Discord time zone converter when you are on mobile, need to select a timezone other than your own, or are preparing timestamps for a bot script or scheduled announcement.

Related Concepts

Discord time zone conversion connects to several broader technical concepts that are worth understanding if you manage a global server or build Discord bots.

Unix time, also called epoch time or POSIX time, counts every non-leap second since January 1, 1970 at 00:00:00 UTC. It is the time-keeping foundation of Linux, macOS, Android, iOS, and most programming languages. Every Discord timestamp code contains a Unix integer at its core.

UTC (Coordinated Universal Time) is the global time standard that Unix time is based on. UTC offsets express how far ahead or behind a local timezone is from UTC. Eastern Standard Time is UTC−5. British Summer Time is UTC+1. Discord's timestamp system stores time in UTC and converts to local time on the viewer's device.

Daylight Saving Time (DST) is the seasonal clock adjustment practiced in many countries. Because Discord timestamps are stored in UTC, DST transitions are handled by the viewer's device using IANA Time Zone Database rules — not by the timestamp value itself. This means a timestamp generated today for an event six months away will display the correct DST-adjusted local time automatically when that date arrives.

The IANA Time Zone Database (also called tzdata, zoneinfo, or the Olson database) contains the history of local time for locations around the globe. It is maintained by the Internet Assigned Numbers Authority and updated whenever governments change timezone boundaries, UTC offsets, or daylight saving rules. Every major operating system and programming language uses it as the authoritative source for timezone data. Discord's timestamp rendering is built on the same database.

Relative time in Discord refers to the :R format style. It displays a human-readable description of how far away or how long ago a moment is — for example, "in 3 hours" or "2 days ago." The value auto-updates in the viewer's client without any message edits. Date localization is the process of displaying a date in the format and language natural for a specific region. Discord handles date localization automatically based on each viewer's locale setting, which is why the same timestamp code displays in French for a French-locale viewer and in English for an English-locale viewer.

Discord markdown is the text formatting system Discord uses for bold, italic, code blocks, spoilers, and timestamp codes. The timestamp syntax <t:UNIX:STYLE> is part of Discord's markdown specification and is documented in the Discord Developer Portal.

Related search terms: Discord timestamp generator, Discord epoch converter, Discord time converter, Discord timestamp format, Discord UTC converter, how to make a Discord timestamp, Discord timestamp syntax, Discord time code, epoch seconds, Unix epoch, UTC offset, Discord scheduling tool.

Discord Time Zone Converter — Free tool for Discord server admins, community managers, and bot developers. Convert any date and time into a Discord timestamp code that displays the correct local time for every member automatically. Supports all 7 Discord timestamp format styles. Works on desktop, mobile, and web.