What this Discord timestamp generator does
This Discord timestamp generator turns a date, a time and a time zone into the short code that makes Discord show one exact moment to every reader in their own local time. You choose when something happens, copy one code and paste it into a message. A member in Karachi sees 6:00 AM, a member in New York sees 8:00 PM the evening before, and nobody has to do time zone arithmetic.
Below the picker you get all seven display styles, a preview of how each one reads for a viewer in any zone and language, countdown shortcuts such as "+1 week", a daylight saving warning, the same moment in eight cities, code for bots in JavaScript and Python, and a snowflake ID decoder that shows when an account, server or message was created. This is an independent tool. It is not affiliated with or endorsed by Discord.
How to use it
- Stay on the Date & time tab. The fields start at the next full hour in your device's time zone.
- Choose the Date and the Time. The time field accepts seconds.
- Set Time zone of this date and time to the place the clock time refers to. This is the field that matters most, because it decides which moment you mean. The hint under it shows the UTC offset that applies on that date.
- For a countdown, press a shortcut (Now, +15 min, +1 hour, +1 day, +1 week) or type a custom amount, pick minutes, hours, days or weeks, and press Set. The date and time fields are filled with the moment that far from now, in the zone you selected.
- Check the Unix timestamp box and the lines under it, which give the moment in your chosen zone and in UTC.
- Under Timestamp codes, press Copy beside the style you want, or Copy all seven codes, then paste it into Discord. The two preview menus show how a viewer in another zone or language will read each style.
The Unix time tab works the other way. Paste seconds, milliseconds (13 digits) or a whole code such as <t:1794704400:R> and the tool shows the moment it stands for. The Snowflake ID tab decodes Discord IDs, explained below. On either tab, Edit in the date picker moves the result back into the first tab.
How Discord timestamps work
A Discord timestamp is ordinary message text in the form <t:UNIX> or <t:UNIX:STYLE>. UNIX is a Unix timestamp, the number of whole seconds since 00:00:00 UTC on 1 January 1970. STYLE is a single letter. The number contains no time zone, because a Unix timestamp names one absolute moment. Each person's Discord app converts that moment to a clock reading using the time zone of their own device. According to community documentation, the viewer's Discord language decides the wording and whether times use AM and PM or a 24-hour clock.
That is why one message can show different clock readings to different people and be right for all of them. It also means the zone in this tool matters only while you type. Once the code exists, the zone is gone and only the moment remains.
The moment 1794704400 is 01:00:00 UTC on November 15, 2026. Here is how this tool previews it for two viewers:
| Style | Name | Viewer in New York, US English | Viewer in London, UK English |
|---|---|---|---|
t | Short time | 8:00 PM | 01:00 |
T | Long time | 8:00:00 PM | 01:00:00 |
d | Short date | 11/14/2026 | 15/11/2026 |
D | Long date | November 14, 2026 | 15 November 2026 |
f | Short date and time | November 14, 2026 8:00 PM | 15 November 2026 01:00 |
F | Long date and time | Saturday, November 14, 2026 8:00 PM | Sunday, 15 November 2026 01:00 |
R | Relative time | depends on the current time | depends on the current time |
These previews come from the browser's Intl formatting, so treat them as close approximations. Discord draws the real text, and its punctuation can differ. A code with no style letter is displayed like f. This page generates the seven long-standing styles. Recent discord.js releases are reported to list two more letters, s (short date with short time) and S (short date with seconds), but how every Discord client draws them is not confirmed here, so they are left out of the copy buttons. If you want to try one, type the letter yourself, as in <t:1794704400:s>, and test it in a private channel first.
A worked example: announcing an event
Say you run a game night on Saturday, November 14, 2026 at 8:00 PM New York time.
- Enter the date 2026-11-14, the time 20:00 and the zone America/New_York. The hint reads UTC-05:00 (EST), because US clocks go back on November 1, and the Unix timestamp is 1794704400. In July the same 8:00 PM would be UTC-04:00 and a different number.
- Copy the codes you need and write the announcement:
Game night: <t:1794704400:F>
Starting <t:1794704400:R>
- Readers see their own clock. The "same moment around the world" list shows the result: 5:00 PM on Saturday in Los Angeles, 10:00 PM in São Paulo, 1:00 AM on Sunday in London, 2:00 AM in Berlin, 6:30 AM in Kolkata, 10:00 AM in Tokyo and 12:00 PM in Sydney.
Countdowns and relative time
The R style shows the distance from now, such as "in 3 hours" or "2 days ago". Discord keeps that wording current without editing the message. Relative text is rounded, so it is never a precise figure. For anything people must be on time for, put the full date with style F next to it.
The countdown shortcuts compute now plus the offset when you press the button, then store a fixed moment. A code made with "+1 day" points at one specific minute, not at "a day after whoever reads it". If a bot should post "starts in 24 hours", it has to calculate that at send time. The live Countdown box in the tool shows the exact days, hours, minutes and seconds left, which Discord's rounded text will not.
Daylight saving: skipped and repeated times
Twice a year, zones that use daylight saving skip a block of clock time or repeat one. The tool checks this with your browser's time zone data and warns you.
- Skipped time. On Sunday, March 8, 2026, clocks in America/New_York jump from 2:00 AM to 3:00 AM, so 2:30 AM never happens. The tool says so and uses 3:30 AM EDT (1772955000), one hour later than you typed.
- Repeated time. On Sunday, November 1, 2026, 1:30 AM happens twice in New York. The first is 1:30 AM EDT (1793511000), the second is 1:30 AM EST (1793514600). A menu lets you choose. London has the same situation on Sunday, October 25, 2026.
Countries also change their clocks on different dates. In 2026 the United Kingdom goes back on October 25 and the United States on November 1, so for that week New York is four hours behind London instead of five. A weekly Saturday 8:00 PM New York event lands at midnight in London on October 31, then at 1:00 AM a week later, which is 169 hours apart instead of 168.
Because a timestamp is one fixed moment, a recurring event needs a fresh code each time, or a bot that recalculates it. In the announcement, also say in words which zone the schedule follows, for example "every Saturday at 8 PM New York time".
Snowflake IDs
Discord identifies users, servers, channels, messages and roles with a 64-bit number called a snowflake. The top bits hold a timestamp, so every ID records when it was created.
| Bits | Field | Meaning |
|---|---|---|
| 63 to 22 | Timestamp | Milliseconds since 1 January 2015 00:00:00 UTC (1420070400000 in Unix milliseconds) |
| 21 to 17 | Worker ID | Five bits identifying the internal worker |
| 16 to 12 | Process ID | Five bits identifying the process |
| 11 to 0 | Increment | A 12-bit counter for IDs made in the same millisecond |
To recover the creation time, shift the ID right by 22 bits and add 1420070400000. IDs exceed the largest integer that ordinary JavaScript numbers hold exactly, which is why the decoder uses BigInt.
Worked example, the ID used in Discord's developer documentation: 175928847299117063 shifted right by 22 gives 41944705796. Adding 1420070400000 gives 1462015105796, which is 2016-04-30 11:18:25.796 UTC. The worker is 1, the process is 0 and the increment is 7.
An ID tells you when that object was created. For a user, that is the account's creation date. It does not say when someone joined a particular server. The decoder warns about values below 4,194,304, where the timestamp part is zero, and about dates in the future, since neither can be a real ID.
Generating timestamps in a bot
Both major bot libraries build the same text. In discord.js, time() with TimestampStyles formats a Date. In discord.py, discord.utils.format_dt() formats a datetime.
import { time, TimestampStyles } from "discord.js";
const unix = Math.floor(Date.now() / 1000) + 3600; // one hour from now
const text = time(new Date(unix * 1000), TimestampStyles.RelativeTime);
The most common bot bug is passing milliseconds. Date.now() returns 13 digits, while Discord expects a 10-digit value in seconds. The Code for a bot section fills in your own moment and style for JavaScript, Python or plain text.
Tips and common mistakes
- Seconds, not milliseconds. A 13-digit number is milliseconds. The Unix time tab converts it and tells you.
- Zone abbreviations. CST and IST each name more than one region, which is why the tool asks for a named zone such as America/New_York or Asia/Kolkata instead of an abbreviation.
- Wrong zone. If the result looks hours off, read the "Selected zone" line under the Unix box. It shows how your input was interpreted.
- Code formatting. Wrapping a code in backticks or a code block makes Discord show it as plain text.
- Embeds. Reports disagree about titles and footers. Descriptions and field values are the usual choice.
- Fallback text. Add a plain-text time where codes will not render, such as exports, logs or other apps.
- Test first. Send the message in a private channel and look at it on desktop and mobile.
Privacy and limitations
The tool remembers your most recent date, time, zone, viewer language and snippet style using sessionStorage, which belongs to this one tab. Reloading keeps those choices and closing the tab discards them. No input is transmitted, and the page never contacts Discord or posts a message on your behalf.
The clock and the device time zone come from your browser. Zone names and daylight saving rules come from the time zone database built into the browser, so an out-of-date browser can be wrong about a recent rule change. The previews are approximate, and the viewer zone and language change only the preview, never the code. Dates run from 1970 through 9999, and Unix timestamps are whole seconds. The tool cannot see how a given server or client version will render a code.
Frequently asked questions
How do I make a timestamp on Discord?
Pick a date, a time and the time zone you mean, then press Copy next to the format you want. You get a short code such as <t:1794704400:R>. Paste it into any Discord message and send it. Discord replaces the code with a time that each reader sees in their own time zone, so you type it once no matter how many countries your community spans.
What do the letters t, T, d, D, f, F and R mean?
They are the seven display styles. Lowercase t is a short time and capital T adds seconds. Lowercase d is a short date and capital D spells out the month. Lowercase f is a date with a short time, and capital F adds the weekday. R is relative time, such as “in 3 hours” or “2 days ago”. A code with no letter is shown like f. Recent discord.js versions also list s and S, which this tool does not generate.
Do Discord timestamps show the right time for people in other time zones?
Yes. A timestamp stores one exact moment as Unix seconds, and each person's Discord app converts it using the time zone of their own device. A friend in Tokyo and a friend in New York see different clock readings for the same moment, and both are correct. The zone you choose in this tool only decides which moment you mean when you type a clock time.
Why is my Discord timestamp showing the wrong time?
The usual cause is the wrong zone when generating it: the date and time you typed were read in a different zone than the one you had in mind. Other causes are pasting milliseconds instead of seconds, a missing angle bracket, and putting the code inside backticks or a code block, where Discord shows it as plain text. Check the zone line under the result first.
How do I make a countdown in Discord?
Use the R style. Press a shortcut such as “+1 hour” or “+1 week”, or enter a custom amount, then copy the relative code. Discord keeps the wording current on its own, so a message that says “in 3 days” later reads “in 2 days”, then “in 5 hours”, without any edit. Relative text is rounded, so add the full date with style F when exactness matters.
Do timestamps work in embeds, on mobile and in bot messages?
Timestamp codes are read wherever Discord renders message text, including messages that bots send. Places other than the main message body are less certain. Community reports disagree about embed titles and footers, while descriptions and field values are the usual safe choice. Always send a test message in a private channel before announcing an event, and check it on both desktop and mobile.
How do I find out when a Discord account, server or message was created?
Turn on Developer Mode in Discord's advanced settings, right-click the user, server, channel or message and choose Copy ID. Paste the number into the Snowflake ID tab. Every ID carries a millisecond timestamp, counted from 1 January 2015 UTC, in its top 42 bits, so the tool can show the exact creation moment plus the worker, process and increment fields packed into the same number.
Can I generate timestamps in a bot with discord.js or discord.py?
Yes. In discord.js, the time() helper with TimestampStyles builds the code from a Date. In discord.py, discord.utils.format_dt() does the same from a datetime. Both simply produce the text <t:UNIX:STYLE>, so a plain string works too. Use Unix seconds, not milliseconds. The Code for a bot section above fills in your moment and chosen style.