A Discord timestamp is a short tag, <t:UNIX:FORMAT>, that Discord converts into a live clock reading each reader sees in their own local time. Type it into a message, and Discord swaps it for a date or countdown that never gets confused by time zones.
Anyone who has scheduled a raid across three countries knows the pain of writing “9 PM EST” and watching half the server show up at the wrong hour. This tag fixes that, and it works in messages, embeds, and slash commands alike.
Here is the syntax, the format codes, and the fastest way to get the Unix number the tag needs.
What the Discord Timestamp Tag Looks Like
The full syntax is <t:1735689600:F>. The number after the first colon is a Unix timestamp, a count of seconds since January 1, 1970, at midnight UTC. The letter after the second colon sets the display format.
Type that string into any message box and send it. Discord renders a readable date, converted to each reader’s own device clock and time zone. No bot required, this is plain Discord markdown.
How to Get the Unix Timestamp You Need
Open your browser’s developer console (F12 on most browsers), click the Console tab, and type Math.floor(Date.now()/1000), then press Enter. That returns the timestamp for right now.
For a future date, type Math.floor(new Date('2026-08-01T20:00:00').getTime()/1000), swapping in your date and time in your local zone. Wrap the number in the tag with the format letter you want.
Every Discord Timestamp Format Code, Explained
The letter you pick changes how the date renders for every viewer. Using a sample date of January 20, 2027 at 4:20 PM:
t shows a short time, 4:20 PM. T adds seconds. d shows a short numeric date, 2027-01-20. D spells it out, January 20, 2027.
f combines a short date with time. F adds the day of the week. R is the relative format, the most popular of the seven, showing “in 3 months” or “2 hours ago” that keeps updating on its own.
Why the Same Timestamp Shows a Different Time to Every Reader
Discord never stores or displays a time zone name because it does not need to. The Unix number inside the tag is one absolute point in time, and the app converts it locally on each reader’s device before rendering it.
A player in Vancouver and a friend in London read the same tag and each get the correct local hour, no manual conversion needed. Worth ruling out a connection issue too; our guide on how to fix Discord not connecting to voice channels covers the usual causes.
Where Discord Timestamps Are Most Useful
Event posts benefit most: drop an R tag into a tournament announcement and it counts down for every reader with zero refreshing. Rules channels use D or F tags to mark when a policy last changed.
Bot developers should know Discord’s own snowflake IDs, the same numeric strings covered in our Discord ID lookup guide, already encode a creation timestamp, a handy trick for figuring out roughly when an account was made. If a PS5 connection to Discord keeps dropping before the scheduled time arrives, sort that out first so your countdown actually matters.
Frequently Asked Questions
Do I need a bot to use Discord timestamps?
No. The <t:UNIX:FORMAT> tag is native Discord markdown and works in any regular message, embed, or slash command without installing anything.
Why does my timestamp show the wrong date after I send it?
The Unix number was likely calculated from the wrong local time before conversion. Check the date and time you fed into the console, since the tag only stores the resulting number, not your intent.
Which format code works best for scheduling an event?
Use R for a live countdown that updates on its own, or pair it right after an F tag so readers see both the exact date and how far away it is.
Tricia Nelson writes about technology, science, and how-to guides for 3Zebras. She has a knack for turning dense, technical topics into clear explanations, covering everything from iPhone and Android troubleshooting to the science stories behind the headlines.