Epoch Time Converter Discord: How to Use It

An epoch time converter for Discord is a tool or bot that translates Unix timestamps (seconds since January 1, 1970 UTC) into readable dates and times, or formats them into Discord’s special timestamp syntax so they display dynamically in chat. You can use it by pasting a raw epoch number into a converter website, or by typing a slash command from a bot inside Discord to get a formatted timestamp you can copy into a message.

Formula

The calculator converts a Unix epoch timestamp (whole seconds) into a calendar date and time. The core formula treats the epoch as a number of days since 1970-01-01, then adds that to Excel’s day-zero (1899-12-30) to get a serial date that spreadsheet programs recognize. The expressions are:

• UTC date/time serial = t / 86400 + 25569, where t is the epoch seconds, 86400 is seconds per day, and 25569 is the day count from 1899-12-30 to 1970-01-01.
• Local date/time serial = t / 86400 + 25569 + offset / 24, where offset is your time zone’s difference from UTC in hours (e.g., -5 for US Eastern Standard Time, +1 for Central European Time).

The result is a decimal number where the integer part is the day and the fractional part is the time of day. For example, 0.5 represents 12:00 noon. To read it as a date, you format the serial as a date/time in a spreadsheet or use a converter that displays the text directly.

Worked Example

Using the default value of t = 1,700,000,000 seconds and offset = 0 (UTC):

1. Divide by 86400: 1,700,000,000 ÷ 86,400 = 19,675.9259259…
2. Add 25569: 19,675.9259 + 25,569 = 45,244.9259 (this is the Excel serial for UTC).
3. The integer 45,244 corresponds to November 14, 2023 (Excel serial 1 = 1900-01-01, so 45244 = 2023-11-14).
4. The fractional part 0.9259 × 24 = 22.22 hours, which is 22:13 (approximately 10:13 PM). So 1,700,000,000 epoch = 2023-11-14 22:13:20 UTC.
5. With offset = 0, the local result is the same as UTC. If you set offset to -5, the serial becomes 45,244.7176, which is 17:13 (5:13 PM) on the same date.

The calculator’s output shows the raw serial numbers; you would format them as dates in a spreadsheet or use the displayed date string from a full converter.

Why Discord Uses Epoch Time

Discord stores every message, user join, and interaction as a Unix timestamp in its database. When you see a date like “Jan 1, 2024� in Discord, the app has already converted the raw number for you. However, if you export Discord data or use its API, you get the raw epoch seconds. That’s why a converter is handy: it lets you read those numbers as human dates, or produce a timestamp that Discord will render correctly in any time zone.

Discord also has a built-in timestamp feature that lets you display a date in chat using a special syntax. You write <t:1700000000> and Discord replaces it with a readable date. You can add a letter after the number to change the format: f for full date and time, d for date only, t for time only, and R for a relative time like “2 hours ago�. An epoch converter helps you generate that syntax correctly.

How to Convert Epoch Time for Discord

There are three main ways to get a Discord-friendly timestamp from an epoch number:

• Use a website converter – Many free online tools let you paste an epoch number and instantly see the UTC date and your local date. Some also output the Discord <t:...> syntax directly.
• Use a Discord bot – Some bots (like “Timestamp� or “Epoch Converter�) have a slash command such as /timestamp 1700000000 that returns the formatted code you can copy into a message.
• Do the math yourself – Divide the epoch by 86,400 to get days, then add that to the Unix epoch date (1970-01-01) using a spreadsheet or programming language. This is the most flexible but least convenient.

For most users, a website converter is the fastest. Just search “epoch converter� and you’ll find several that show both UTC and local time. If you need the Discord syntax, look for a field that says “Discord Timestamp� or “Format for Discord�.

Common Mistakes and Misconceptions

One frequent error is confusing seconds with milliseconds. Discord’s API uses seconds (10 digits), but many other systems (like JavaScript’s Date.now()) use milliseconds (13 digits). If you paste a 13-digit number into a seconds-based converter, the date will be off by about 47 years. Always check the digit count: seconds = 10 digits, milliseconds = 13.

Another mistake is ignoring time zones. An epoch timestamp is absolute – it represents the same instant everywhere. But when you convert it, the date and time you get depend on your local offset. If you see a date that looks wrong, check whether the converter is showing UTC or your local time. Discord automatically displays timestamps in each user’s local time zone, so a message sent at 10 PM UTC will show as 5 PM in New York and 11 PM in Berlin.

Also, note that the Unix epoch starts at 1970-01-01 00:00:00 UTC. Dates before that are represented as negative numbers. Some converters handle negatives fine, but others may show an error. If you need pre-1970 dates, use a converter that explicitly supports negative timestamps.

Limits of the Formula

The conversion formula above works for any epoch in seconds, but it relies on the Gregorian calendar and ignores leap seconds. Unix time is defined as the number of seconds since 1970, ignoring leap seconds, so it is always a continuous count. The formula also assumes a 24-hour day, which is true for Unix time. However, if you use the Excel serial method, be aware that Excel has a bug that treats 1900 as a leap year, so serial numbers for dates after February 28, 1900 are correct, but before that they are off by one day. For Discord-related dates (all after 2015), this is irrelevant.

Another limit: the formula gives a serial number, not a formatted date string. To get “Nov 14, 2023 22:13:20� you need to convert the serial to a date using a spreadsheet’s formatting or a programming language’s date functions. The calculator above shows the serial so you can verify the math, but for everyday use you’ll want a converter that displays the full text.

Frequently Asked Questions

How do I get a Discord timestamp from an epoch number?

Take the epoch in seconds and wrap it in <t:...>. For example, <t:1700000000> shows the date. Add a suffix like <t:1700000000:f> for full date and time, <t:1700000000:R> for relative time. Many converters have a button that copies this syntax for you.

Why does my epoch converter show a different date than Discord?

Most likely you’re comparing UTC to your local time. Discord shows the timestamp in each viewer’s local time zone, so if you convert to UTC and it’s 10 PM, in New York it will display as 6 PM. Check the converter’s time zone setting.

Can I convert a Discord timestamp back to epoch?

Yes. If you see a date in Discord, you can’t directly see the epoch, but you can use a converter that has a “date to epoch� feature. Enter the date and time (with time zone) and it will give you the epoch seconds. Note that Discord’s timestamps are always in seconds, not milliseconds.

What is the difference between Unix time and epoch time?

They are the same thing. “Unix time� and “epoch time� both refer to the number of seconds since 1970-01-01 00:00:00 UTC. The term “epoch� is just the name for that starting point.

Why do some epoch numbers have 13 digits?

Those are milliseconds, not seconds. JavaScript’s Date.now() and many APIs return milliseconds. To convert to seconds, divide by 1000. If you accidentally use a 13-digit number in a seconds converter, the date will be in the far future (around 5138).

Is there a way to make a timestamp that updates automatically?

Yes, use the R suffix in Discord’s timestamp syntax. For example, <t:1700000000:R> displays as “2 hours ago� and updates live. The underlying epoch does not change, but Discord recalculates the relative time every time you view it.

Related

• Pin Code Distance Calculator: How It Works
• PSV Brake Code Calculator & How It Works
• QR Code Calculator: Decode Data Payloads

in t | Epoch time (seconds) | - | 1700000000 | 0
out dt | Date and time (UTC) | - | t / 86400 + 25569 | 0
in offset | Your UTC offset (hours) | - | 0 | -12
out local | Date and time (your zone) | - | t / 86400 + 25569 + offset / 24 | 0