Quick Answer
Pick the date and time, choose your time zone, and press Make timestamp codes. Copy the code for the style you want and paste it into your chat message. You can also paste a Unix timestamp to get all the codes for it.
Embed this calculator
Adjust the size if needed, then copy the code below into your page or blog. The calculator will load in an iframe and stay updated automatically.
Table of Contents
- Chat Timestamp Generator
- Quick Answer
- Related Calculators
- How This Chat Timestamp Generator Works
- How to Use the Chat Timestamp Generator
- How the Code Is Built
- Key Terms
- Worked Example
- Real-Life Examples
- Timestamp Code vs Typing the Time
- Timestamp Styles
- Tips for Using Timestamp Codes
- Common Mistakes to Avoid
- Frequently Asked Questions
- References & Sources
How This Chat Timestamp Generator Works
Some chat apps let you write a time inside a message as a short code, such as <t:1618935630:f>. Instead of showing the code, the app turns it into a readable date and time, and it shows each reader the time in their own time zone. This is useful for events, because “8 PM” means something different to everyone.
This tool turns a date, a time and a time zone into that code. It makes one code for each style so you can copy the one you like. You can also paste a Unix timestamp to get the codes for it.
Features:
- All styles at once: short and long times, short and long dates, full dates and relative time.
- Time zone picker: your device zone, UTC and 22 major cities.
- Preview: see what each style looks like next to its code.
- Unix input: paste a number of seconds, or milliseconds, and get the codes back.
How to Use the Chat Timestamp Generator
- Pick the date and time of your event.
- Choose the time zone the event uses.
- Press Make timestamp codes.
- Copy the code for the style you want from the table.
- Paste it into your chat message.
How the Code Is Built
- Code format: <t:TIMESTAMP:STYLE>. The style letter is optional; leaving it out uses the default style, f.
- Timestamp: a Unix timestamp in whole seconds, not milliseconds. It counts the seconds since 1 January 1970 at 00:00:00 UTC.
- Local time to Unix time: the tool finds the UTC offset of your chosen zone on that date, including daylight saving time, and subtracts it from the date and time.
- Milliseconds: if you paste a number of 12 digits or more, the tool treats it as milliseconds and divides it by 1,000.
- Relative style (R): the reader’s app works out the gap to the current time, such as “4 years ago” or “in 2 hours”.
Key Terms
- Unix timestamp: the number of seconds since 1 January 1970 at 00:00:00 UTC.
- UTC: Coordinated Universal Time, the base time that other zones are offset from.
- Time zone: a region with one set of clock rules, including daylight saving changes.
- Relative time: a time shown as a gap from now, such as 3 hours ago.
Worked Example
- Date and time: 20 April 2021, 16:20:30 in UTC.
- Days from 1 January 1970 to 20 April 2021: 18,737. That is 18,737 × 86,400 = 1,618,876,800 seconds.
- Add the time of day: 16 × 3,600 + 20 × 60 + 30 = 57,600 + 1,200 + 30 = 58,830 seconds.
- Unix timestamp: 1,618,876,800 + 58,830 = 1,618,935,630.
- Code for the long date with short time: <t:1618935630:f>.
Real-Life Examples
- Event announcements: everyone sees the start time in their own zone.
- Deadlines: post a relative code so readers see how long is left.
- Game nights and streams: schedule across countries without a time zone chart.
- Meetings: share one code instead of listing times for each office.
Timestamp Code vs Typing the Time
- Timestamp code: one value that each reader sees in their own zone, so nobody has to convert it.
- Typed time: “8 PM EST” forces readers to convert it, and daylight saving makes EST and EDT easy to mix up.
- Where codes work: only in chat apps that support the tag format; elsewhere the raw code shows as text.
Timestamp Styles
These examples come from the format’s own documentation. The look of each style can change with the reader’s language and settings.
| Style | Name | Example output |
|---|---|---|
| t | Short time | 16:20 |
| T | Medium time | 16:20:30 |
| d | Short date | 20/04/2021 |
| D | Long date | April 20, 2021 |
| f | Long date with short time (default) | April 20, 2021 at 16:20 |
| F | Full date with short time | Tuesday, April 20, 2021 at 16:20 |
| s | Short date with short time | 20/04/2021, 16:20 |
| S | Short date with medium time | 20/04/2021, 16:20:30 |
| R | Relative time | 4 years ago |
Tips for Using Timestamp Codes
- Pick the zone the event happens in. If the event is at 8 PM New York time, choose New York, not your own zone.
- Use R for countdowns. “in 3 days” is clear for a deadline or an event start.
- Use F for announcements. The weekday avoids date mix-ups.
- Check daylight saving dates. Times near a clock change depend on the zone’s rules, which this tool applies for you.
- Test the code. Paste it into a message and check that it shows the time you expect.
Common Mistakes to Avoid
- Using milliseconds. The code needs seconds, so a 13 digit number gives a wrong date.
- Picking the wrong zone. The same clock time is a different moment in each zone.
- Leaving out the angle brackets. The code must start with < and end with >.
- Adding spaces inside the code. Spaces break it, so it shows as plain text.
- Using it where it is not supported. Other apps show the raw code, so test first.
Frequently Asked Questions
A short tag like
Yes, with no sign-up and no download.
It shows relative time, such as 4 years ago or in 2 hours.
If you leave the style out, the code uses f, a long date with a short time.
Seconds. If you paste a longer number, the tool treats it as milliseconds and divides by 1,000.
Everyone sees the same moment, shown in their own time zone and language settings.
Yes. The tool uses the zone’s rules for the date you pick.
The app may not support the tag format, or a space or bracket is missing.
Yes. Dates from 1970 to 9999 work in this tool.
Pick today’s date and the current time, or use a Unix timestamp converter.
Short date with short time, and short date with medium time.
It is only a guide. Each reader sees their own language and format.
No. Everything runs in your browser.
Leave Your device time zone selected, or pick a city from the list.
References & Sources
| Source | Used For | Link |
|---|---|---|
| Developer documentation of the chat app that defines this tag format, Timestamp Styles | Tag syntax |
https://docs.discord.com/developers/reference |
| MDN, Intl.DateTimeFormat | How the browser formats dates and times for a chosen time zone. | https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat |