Discord Timestamps: How to Add Them

Discord timestamps let you display dates and times in any timezone, automatically converting for each viewer. This guide shows you how to generate the correct code and paste it into your messages, channel topics, or posts.

What You’ll Need

A Discord account (web, desktop, or mobile app)
A Unix timestamp for the date/time you want to display
Permission to send messages in the channel where you’ll paste the code

Step-by-Step

Get a Unix timestamp for your target date and time. A Unix timestamp is the number of seconds since January 1, 1970, UTC. You can generate one using an online converter or by running date +%s in a terminal (Linux/macOS) or Get-Date -UFormat %s in PowerShell (Windows). For example, the timestamp for January 1, 2025, 12:00 UTC is 1735689600.
Decide which format style you want. Discord supports several display styles, each with a different letter code:
Construct the timestamp code. The format is always: <t:UNIX_TIMESTAMP:STYLE>. Replace UNIX_TIMESTAMP with your number and STYLE with one of the letters below. For example, to show a short date and time, use <t:1735689600:f>.
Paste the code into your Discord message. Type or paste the full code (including the angle brackets and colon) into the message box. It will appear as plain text until you send it.
Send the message. Once sent, Discord converts the code into a clickable, timezone-aware timestamp. Hovering over it shows the exact date and time in your local timezone.

Style Codes:

t – Short time (e.g., 3:45 PM)
T – Long time (e.g., 3:45:30 PM)
d – Short date (e.g., 01/01/2025)
D – Long date (e.g., January 1, 2025)
f – Short date and time (e.g., January 1, 2025 3:45 PM) – default if no style is given
F – Long date and time (e.g., Wednesday, January 1, 2025 3:45 PM)
R – Relative time (e.g., 2 months ago, in 3 days)

Example codes:

Relative: <t:1735689600:R> → “in 2 months”
Long date: <t:1735689600:D> → “January 1, 2025”
Short time: <t:1735689600:t> → “12:00 PM”

Common Mistakes

Using milliseconds instead of seconds. Unix timestamps from many programming languages (like JavaScript’s Date.now()) are in milliseconds. Discord expects seconds. Divide by 1000 if your source gives milliseconds.
Forgetting the angle brackets. The code must include the < and > characters. Without them, Discord treats it as literal text.
Using the wrong case for the style letter. Styles are case-sensitive: t and T are different, as are d and D. Double-check which one you want.
Including spaces or extra characters. The code must be exactly <t:number:letter> with no spaces, quotes, or other punctuation inside.
Using a timestamp in the past when you meant the future. Triple-check your Unix timestamp corresponds to the correct year and timezone (UTC).

Tips

Use relative timestamps for deadlines. The R style automatically updates (e.g., “in 3 days” becomes “in 2 days”), which is great for event reminders.
Test with a known date. Before relying on a timestamp for an important announcement, send it in a private channel or to yourself to verify it displays correctly.
Combine multiple timestamps. You can put several timestamp codes in one message, useful for showing both a start and end time.
Use them in channel topics and embed descriptions. Timestamps work in most text fields, not just regular messages.
Bookmark a timestamp generator. Many free websites let you pick a date/time and instantly copy the Discord code, saving you the math.

Troubleshooting

The timestamp shows as plain text like <t:1735689600:f> instead of a formatted date. This usually means you have a typo. Check that you used the correct angle brackets, the number is a valid Unix timestamp (10 digits, not 13), and the style letter is one of the allowed options. Also ensure you didn’t accidentally add a space before or after the code.

The date is off by one day or several hours. Your Unix timestamp is probably in UTC but you expected local time, or you used milliseconds. Convert your local date/time to UTC before generating the timestamp, and divide millisecond values by 1000.

The timestamp displays but in the wrong format. You likely used the wrong style letter. Refer to the style list above and replace the letter in your code.

It works in one channel but not another. Some bots or server settings may strip certain characters. Try pasting the code in a different channel to rule out a server-side filter.

Hovering shows “Invalid Date.” Your timestamp number is outside the valid range (before 1970 or far in the future). Generate a new timestamp for your intended date.

Frequently Asked Questions

Can I use Discord timestamps on mobile? Yes, the codes work identically on iOS and Android apps. Paste the code into the message box and send.

Do timestamps work in server names or nicknames? No, they only render in message content, channel topics, and embed fields – not in server or channel names.

Can I make a timestamp that updates automatically? The R (relative) style updates continuously, showing “in 5 minutes” then “in 4 minutes,” etc. Other styles are fixed to the moment you set them.

What happens if I use no style letter? The default format is the short date and time (f style). For example, <t:1735689600> displays the same as <t:1735689600:f>.

Can I use timestamps in direct messages? Yes, they work in DMs, group DMs, and server channels alike.

Is there a limit to how many timestamps I can put in one message? No specific limit, but Discord’s general message length limit (2000 characters) applies, so keep the rest of your message short if you include several.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →