Pick a date and time below and this converter builds the Discord timestamp code for that moment in all seven display styles. Copy a code, paste it into a Discord message, and every reader sees the time converted into their own local timezone automatically.
Unix timestamp: seconds
| Style | Preview (your timezone) | Code to copy |
|---|
What Is a Discord Timestamp?
A Discord timestamp is a short piece of markdown that tells Discord: show this exact moment, formatted for whoever is reading. It looks like this: <t:1735689600:F>. The long number in the middle is a Unix timestamp — the count of seconds between 1 January 1970 and the moment you mean. The letter at the end chooses how the moment is displayed.
When you send a message containing that code, Discord does not show the raw text. It replaces it with a friendly date or time, worked out on the reader’s own device. A member in Los Angeles, another in London and a third in Karachi can read the same announcement and each sees the start time in their own timezone, in their own 12-hour or 24-hour format, with their own date order. Nobody has to convert anything by hand, and the classic mistake of writing a bare time like 8 PM and forgetting the timezone disappears.
If you leave the style letter off, Discord uses the date-and-time style by default, so <t:1735689600> still works. The converter above always includes the letter, because picking the style deliberately gives a much clearer announcement.
The 7 Discord Timestamp Styles
All seven styles describe the same instant; only the presentation changes. This table uses one fixed moment — 1 January 2025 at midnight UTC, Unix time 1735689600 — and shows how each style renders for a reader whose device is set to UTC with US formatting. Your own readers will see the same moment shifted into their own timezone and language.
| Style | Code | Renders as (UTC example) | Best for |
|---|---|---|---|
| Short time (:t) | <t:1735689600:t> |
12:00 AM | A time on a day everyone already knows |
| Long time (:T) | <t:1735689600:T> |
12:00:00 AM | Countdowns and precise start times with seconds |
| Short date (:d) | <t:1735689600:d> |
1/1/2025 | Compact date references |
| Long date (:D) | <t:1735689600:D> |
January 1, 2025 | Readable dates without a time |
| Date and time (:f) | <t:1735689600:f> |
January 1, 2025 12:00 AM | Most announcements; also the default style |
| Full date and time (:F) | <t:1735689600:F> |
Wednesday, January 1, 2025 12:00 AM | Events, where the weekday matters |
| Relative time (:R) | <t:1735689600:R> |
in 2 months, or 3 days ago | Countdown-style reminders that update live |
The relative style is the only one that keeps moving: it counts up or down as time passes, so a message posted last week still reads sensibly today. Pairing the full style with the relative style — the date for the calendar, the countdown for urgency — is the pattern most event announcements use.
How to Use This Discord Time Converter
First, enter the date and time of your event in the picker. Enter it exactly as it appears on your own clock: the converter treats what you type as your local time, which is what you want, because the schedule you are copying from was almost certainly written for your timezone. Second, glance at the Unix timestamp line if you need the raw number for a bot or a script. Third, find the style you like in the table and press its Copy button. Fourth, paste the code into your Discord message as ordinary text and send it. That is the whole process; there is nothing to install and no bot to invite.
The previews in the table are rendered in your timezone, so they show exactly what the code will look like to you. Everyone else sees their own equivalent.
Worked Example: Announcing a Community Game Night
Imagine your server is running a game night on Saturday, 14 March 2026 at 7:30 PM UTC. That moment is Unix time 1773516600. The converter produces these seven codes:
| Style | Code | A UTC reader sees |
|---|---|---|
| :t | <t:1773516600:t> |
7:30 PM |
| :T | <t:1773516600:T> |
7:30:00 PM |
| :d | <t:1773516600:d> |
3/14/2026 |
| 😀 | <t:1773516600:D> |
March 14, 2026 |
| :f | <t:1773516600:f> |
March 14, 2026 7:30 PM |
| :F | <t:1773516600:F> |
Saturday, March 14, 2026 7:30 PM |
| :R | <t:1773516600:R> |
Relative wording that updates as time passes |
A ready-to-post announcement might read: Game night starts <t:1773516600:F> — that is <t:1773516600:R>. A member in New York reads 3:30 PM on Saturday afternoon, because New York is on Eastern Daylight Time (UTC−4) that day. A member in Karachi reads 12:30 AM on Sunday, because Karachi is UTC+5. Same message, same code, three correct local times.
Why the Same Code Shows a Different Time to Everyone
It helps to separate the moment from its display. The Unix number inside the code names one single instant, the same way a point on a globe is one place regardless of what language you name it in. That instant never changes. What changes is the label each reader’s Discord client sticks on it, and the client takes the label rules — timezone, hour format, date order, language — from the reader’s own device settings.
Two practical consequences follow. First, your timezone as the sender does not travel with the message: once the code is made, nobody can tell or needs to know where you were. Second, the only moment where timezone mistakes can happen is right here, at creation. If the event is advertised as 7:30 PM London time and you are sitting in New York, either set the picker while thinking in London time or convert before you generate the code. After that, Discord handles everything.
Common Discord Timestamp Mistakes
Using milliseconds instead of seconds. Many programming tools produce 13-digit millisecond timestamps. Discord expects 10-digit seconds. A millisecond value pasted into a code lands thousands of years in the future, which is the giveaway if a date ever looks absurd.
Wrapping the code in backticks. Inside backticks or a code block, Discord shows the literal characters instead of rendering the time. Paste the code as plain message text.
Typing the time as plain text. Writing starts at 8 PM EST invites trouble: half the server will convert from the wrong offset, especially around daylight saving changes. A timestamp code has no such ambiguity.
Confusing the f and F styles. The lowercase f omits the weekday; the capital F includes it. Forgetting which is which is harmless but worth checking in the preview before you copy.
Editing part of the code. The opening bracket, the t, both colons, the full number and the closing bracket all have to survive the paste. If a code shows as raw text, one of those pieces is usually missing.
Where Timestamps Work, and Making Them Look Good
Timestamps render in normal messages, in embed descriptions and fields, and in messages sent by bots and webhooks, so the same codes work for hand-written announcements and automated reminders alike. For announcements, the full style plus the relative style in brackets is the most readable combination. If the text around the timestamp needs styling too — bold headers, small caps, fancy lettering for a server event post — our Discord font generator creates copy-and-paste text styles that sit happily next to timestamp codes. And if your community plans in real-world units as well as in-game ones, the converter family this tool belongs to includes a weight converter, a temperature converter and a length converter for everything outside Discord.
Frequently Asked Questions
What is a Discord timestamp?
A Discord timestamp is a short code in the form <t:UNIX:STYLE> that you paste into a message. Discord replaces it with a date or time formatted for each reader, using the Unix time stored in the code — the number of seconds since 1 January 1970, UTC.
How do I paste a timestamp into Discord?
Copy a code from the table above and paste it into any message as plain text, then send it. Do not wrap it in backticks or a code block, because Discord then displays the raw code instead of the formatted time.
What timezone does a Discord timestamp use?
It uses each reader’s own timezone, taken from their device settings. The code stores one universal moment as Unix time, and every Discord client converts that moment locally, so the sender’s timezone does not affect what anyone else sees.
What is the difference between the f and F styles?
The f style shows the date and time without the weekday, such as March 14, 2026 7:30 PM. The F style adds the full weekday name, such as Saturday, March 14, 2026 7:30 PM. Use F for events when the day of the week matters to your readers.
Do Discord timestamps work on mobile?
Yes. Timestamps render in Discord on iOS, Android, desktop and the web app, always in the timezone of the device viewing them. You can generate a code with this tool on your phone and paste it straight into the Discord mobile app.
Why does my timestamp show the wrong time?
The usual cause is the moment that was picked: this converter reads the date and time you enter as your local time, so enter the time as it appears on your own clock and in your own timezone. The other common cause is pasting milliseconds (a 13-digit number) instead of seconds (10 digits), which pushes the date far into the future.