How to Set a Time on a Discord Message

Setting a time on a Discord message sounds simple until you actually try it. I learned this the hard way planning a gaming session with friends across three countries — I said "9 pm" and three people showed up at completely different hours. After that I started using Discord timestamps, and the confusion stopped completely. Every reader sees the correct local time on their screen automatically — no math, no timezone conversion, no follow-up questions.

This guide covers every method available in 2026 — from the brand new @time mention Discord added in January 2026 to manual Unix time code creation, scheduled messages, and bot automation for recurring schedule message workflows.

What Is a Discord Timestamp and Why Use It?

A Discord timestamp is a code you embed directly inside a message box. When someone reads it, Discord automatically renders it in their own local time zone — so if you write an event for 5 PM Eastern Standard Time, a friend in the UK sees 10 PM automatically. No mental math, no timezone setting friction, no missed events.

Behind the scenes Discord uses Unix time — a number counting every seconds elapsed since January 1 1970 at 00:00:00 UTC, known as the Unix epoch. That number is what you embed inside the message. Discord reads it, converts it using each reader's device timezone setting, and displays the correct local time for everyone simultaneously. This is fundamentally different from typing "Friday 9 pm" — a typed time never adapts to anyone's local time zone.

Method 1 — The @time Mention (Fastest in 2026)

In January 2026 Discord introduced the @time mention — now the fastest way to set a time on a Discord message without any external tool or Unix time calculation.

Type @time into any Discord message box and a popup appears instantly showing timestamp options for the current date and time in multiple format styles — long date time, short date, relative time like "in 2 months". Keep typing a specific date and time after @time and Discord adjusts its options automatically.

Select any option and Discord inserts the correct Unix time code automatically. No converter tool needed, no UTC offset math, no angle brackets to type manually. For quick scheduling and announcements this is the fastest path to a working timestamp in a message.

Method 2 — Discord Timestamp Generator (Recommended for Specific Dates)

For specific future dates, precise event scheduling, or when you need all 7 format codes simultaneously, use our free Discord Timestamp Generator — the fastest tool for creating any Discord message timestamp.

Step 1 — Convert your date and time. Open the Discord Timestamp Generator and use the date picker to select your date and time. The tool auto-detects your timezone setting on load — confirm it matches where your event is based. The tool automatically converts your input to the correct Unix time number handling daylight savings time and UTC offset without any manual math.

Step 2 — Choose your format flag. All 7 format codes appear simultaneously:

Step 3 — Copy and paste into Discord. Click the copy button next to your chosen format code — or use Copy All Formats to grab every code at once. Paste as plain text into your Discord message box. Never wrap in backticks or a code block — this disables Discord's rendering and shows raw code instead of the formatted timestamp.

Method 3 — Manual Unix Time Code Creation

If you know your UTC offset and want full control over formatting — for example inside bot embeds, webhook payloads, or Zapier workflow automation — you can create manually using Discord's Unix time syntax directly.

The format string is: <t:UNIXTIME:FLAG>

Where UNIXTIME is the Unix epoch number in seconds and FLAG is your chosen single-letter style code. For example <t:1762491060:F> displays as "Sunday, November 7, 2026 9:00 PM" for every reader in their own local timezone.

To get the Unix time number manually: count the seconds since January 1 1970 00:00:00 UTC for your target date and time, adjusted for your UTC offset. In practice, most people use our Unix Timestamp Converter to do this instantly rather than calculating by hand — manual calculation is slow and prone to daylight savings time errors if you get the UTC offset wrong for the time of year.

Important: always use seconds not milliseconds. A Unix time value in milliseconds is 13 digits and produces a timestamp showing a date far in the future. Discord requires seconds — a 10-digit number.

Method 4 — Scheduled Messages (Send Later)

A Discord timestamp shows a time inside a message but does not schedule the message itself to send automatically. These are two different features.

If you want send later — Discord's built-in scheduled messages feature — here is how:

On mobile: Press and hold the Send button → select Schedule Message → pick your date and time → confirm. Discord queues the message and sends it automatically at the specified time in your local time zone.

On desktop: Click the small arrow next to the send button → select Schedule Message → set your date and time → confirm.

Discord currently allows up to 15 scheduled messages per channel at one time. Scheduled messages appear in a separate queue you can view and cancel before they send.

Note: Discord scheduled messages send at the time you set in YOUR timezone — not the reader's. If you want the message to reference a time that automatically converts for every reader, combine both features: schedule the message to send automatically AND include a Discord timestamp code inside it.

Method 5 — Bot and Automation Workflows

For recurring schedule message workflows — weekly event announcements, automated raid scheduling, regular community updates — a discord bot for scheduled messages or a Zapier workflow handles this without manual effort every time.

Using a Discord bot: The most popular bot for scheduled messages is MEE6 which has a built-in scheduled messages feature. Add it to your server and configure recurring posts with Discord timestamp codes embedded in the message template. The bot fires the message at the configured interval automatically.

Using Zapier: Connect a Google Calendar trigger to a Discord action step. Add a Formatter step that converts the calendar event start time to Unix time using the X format string option — this outputs the raw Unix epoch number in seconds. Then build your Discord message template wrapping that output in angle brackets: <t:ZAPIER_OUTPUT:F>. The workflow fires automatically whenever a Google Calendar event matches your trigger conditions.

Using the @time mention with bots: Bot for scheduled messages like Carl-bot also support timestamp codes in message templates — use the same <t:UNIX:F> format string inside the bot's message box template and it renders correctly for every reader.

Common Mistakes When Setting a Time on Discord Messages

Pasting inside backticks: Shows the raw code instead of rendered timestamp. Always paste as plain text — never inside backticks or code blocks.

Using milliseconds instead of seconds: JavaScript's Date.now() returns milliseconds — a 13-digit number. Discord needs seconds — 10 digits. Divide by 1000 first.

Wrong UTC offset: If your timestamp shows a time one hour off, you selected the wrong UTC offset or ignored daylight savings time. Use named timezones like America/New_York instead of abbreviations like EST — named timezones automatically apply the correct daylight savings time offset.

Trying to edit after sending: A timestamp code points to a fixed moment — you cannot change it after sending. Delete the message and send a corrected one.

Related Guides

• How to Do a Timestamp on Discord
• How to Use Discord Timestamps
• Discord Time Zone Converter
• Discord Timestamp Generator