Discord Timestamp Generator
Create Discord timestamps and countdowns that every reader sees in their own time zone.
Create Discord timestamps and countdowns that every reader sees in their own time zone.
"Saturday at 8 PM" means one moment to the person who wrote it and a different one to everyone in another time zone. A Discord timestamp fixes that: the code <t:1790878500:F> holds one moment, and Discord shows it to each reader in their own time zone and language. One player in New York reads 2:15 PM, a teammate in London reads 19:15, and both are right.
Pick the date and the time, check the time zone (it starts on yours) and the list under it fills with every Discord timestamp code for that moment, each next to a preview of how it looks to you. Tap a row to copy its code, then paste it into any message. The buttons under the time zone add an hour, a day or a week, or move the same time to tomorrow. The last row is the bare unix timestamp, for bots and spreadsheets.
A code is <t: plus the unix time in seconds, a colon, one style letter and >. Discord has nine styles. Here is how each one reads for a reader in New York with Discord in US English, for October 1, 2026 at 2:15 PM:
| Code | Style | What the reader sees |
|---|---|---|
<t:1790878500:t> | Short time | 2:15 PM |
<t:1790878500:T> | Medium time | 2:15:00 PM |
<t:1790878500:d> | Short date | 10/1/26 |
<t:1790878500:D> | Long date | October 1, 2026 |
<t:1790878500:f> | Long date, short time | October 1, 2026 at 2:15 PM |
<t:1790878500:F> | Full date, short time | Thursday, October 1, 2026 at 2:15 PM |
<t:1790878500:s> | Short date, short time | 10/1/26, 2:15 PM |
<t:1790878500:S> | Short date, medium time | 10/1/26, 2:15:00 PM |
<t:1790878500:R> | Relative | in 3 hours (read at 11:15 AM) |
A reader with Discord in British English sees 01/10/2026 for the short date and 14:15 for the time; a German reader sees 1. Oktober 2026 um 14:15. A code with no letter, <t:1790878500>, shows like f. Discord also has its own 12 or 24-hour clock setting, so the same code can read 2:15 PM for one person and 14:15 for another. The previews here use your browser's language and time zone, the way Discord uses the language you picked in its settings.
The R style is the countdown: "in 3 hours" before the moment, "3 hours ago" after it. Its preview on this page counts live. Discord rounds to the nearest unit and changes unit at fixed points: seconds up to 59, then "a minute", minutes up to 59, then "an hour", hours up to 21, then "a day" from 22 hours, days up to 25, then months, and years from 11 months. So an event 23 hours away reads "in a day", and one 47 minutes away reads "in 47 minutes".
For an event announcement, the usual pattern is both styles side by side: <t:1790878500:F> (<t:1790878500:R>) reads "Thursday, October 1, 2026 at 2:15 PM (in 3 hours)", the exact time plus how long is left.
The box under the buttons works the other way round: paste something and the date and time come back in the time zone you picked, with every code made again for that moment. It says what it read the paste as:
A Discord ID carries its own creation time: the top bits count milliseconds since the first second of 2015, so (id >> 22) + 1420070400000 is the moment it was made. Discord's own example, 175928847299117063, comes out as 2016-04-30 11:18:25.796 UTC. Paste a user ID to see when the account was created, or a message link to see when the message was sent. To see that user's profile picture, the same ID works in the Discord PFP Viewer.
The time zone box is the zone the date and time are meant in. Search it by city, country, abbreviation (EST, CET, IST) or offset (+5:30). Half-hour and 45-minute zones such as India and Nepal work like any other, and each zone's offset is shown for the date you picked, so summer time is already in it.
Daylight saving makes two times awkward, and the page says which way it went. When the clocks jump forward, a time in the skipped hour does not exist: 2:30 AM on March 8, 2026 in New York becomes 3:30 AM, moved forward by the gap. When the clocks go back, an hour happens twice: 1:30 AM on November 1, 2026 in New York is taken as the first one, still on summer time.
Open In other zones to see the moment the way a reader in up to four other cities sees the default style. Your list of zones is remembered in this browser.
Crop a picture to Discord's circle with the Discord PFP Cropper, turn your display name into fancy fonts with the Discord Name Converter, and copy ready-made rules for your server from Discord Rules.
Everything here runs in your browser: the date maths, the formats and the decoding of IDs. Nothing you type or paste is sent anywhere, and an ID is read from its own digits, not looked up, so a pasted user ID or message link never leaves your device. The only thing kept is your list of other time zones, in this browser's own storage.
Pick the date and time of the event, tap the R row to copy its code and paste it into your message. Discord shows it as "in 3 hours", "in 2 days" and so on, for every reader, and as "3 hours ago" once the moment has passed.
That is the point of it. The code holds one moment and Discord shows it in each reader's own time zone, so a friend in another zone sees their local time for the same moment. Check the In other zones list to see what they see.
Seconds. A code with a 13-digit millisecond value is read as seconds and lands tens of thousands of years in the future. Paste the millisecond number into the converter and it gives the codes in seconds.
Copy the user's ID in Discord (Developer Mode in Advanced settings, then Copy User ID) and paste it into the converter. The time it was created is in the ID itself, to the millisecond.
The code has to be exact: angle brackets around t, a colon, the time in whole seconds and an optional colon with a style letter, and no spaces anywhere. A decimal point or a style letter Discord does not use leaves it as plain text. Paste the code into the converter and it says what it found.
Yes. Pick the zone the time is meant in, for example the event's local time in Tokyo, and the codes are made for that moment. Every reader still sees it in their own time zone.