Milliseconds to Date Converter
Convert a 13-digit Unix timestamp in milliseconds into a readable date and time. This page is built for debugging API payloads, frontend logs, JavaScript Date.now() values, and database fields stored in epoch milliseconds.
Epoch to Date Converter
Use this converter for searches like epoch converter, epoch to date, epoch time to date, epoch time converter, and unix epoch converter. It also matches narrower searches like epoch timestamp converter and epoch timestamp to date. Paste the raw Unix value exactly as you copied it and this tool turns it into a readable date, time, ISO string, and timezone-aware answer.
These examples match the broad homepage queries people use when they are not sure whether their timestamp came from seconds, milliseconds, or decimal SQL output. Decimal SQL values and negative timestamps work too.
Readable answer
1708560000000 converts to Thursday, February 22, 2024 at 00:00:00 UTC. If this looks shifted by hours, keep the same epoch value and change the timezone instead of editing the number.
UTC answer for epoch search results
In UTC, 1708560000000 is Thursday, February 22, 2024 at 00:00:00 UTC. Use this baseline for searches like epoch to date, epoch date, and epoch timestamp converter before comparing local timezone output.
Thursday, February 22, 2024
00:00:00 UTC
Thursday, February 22, 2024
00:00:00
Thursday
2024-02-22T00:00:00.000Z
UTC
What is a milliseconds timestamp?
A Unix milliseconds timestamp is the number of milliseconds that have elapsed since January 1, 1970 at 00:00:00 UTC. These values are typically 13 digits long and are common in browser JavaScript, mobile apps, analytics events, and log streams. If a timestamp has 13 digits, treat it as milliseconds; if it has 10 digits, treat it as seconds. Mixing those two formats is the most common reason dates look wrong.
Milliseconds to date conversion tips
Start by pasting the raw number into the converter above. It will auto-detect milliseconds, render the exact instant, and show ISO 8601 so you can compare results across systems. If your backend expects seconds, divide by 1,000 before sending the value. If your backend returns seconds but your frontend expects milliseconds, multiply by 1,000 before creating a Date.
UTC vs local timezone
The timestamp itself is timezone-agnostic and always represents a UTC instant. Timezone only affects display formatting. That is why the same milliseconds value can appear as different local clock times across cities but still represent one exact moment. Use the timezone selector above when validating incidents between teams in different regions.
Related pages
Need full bidirectional conversion? Open the main epoch converter.
Frequently Asked Questions
What does a 13-digit timestamp mean?
It represents milliseconds since the Unix epoch (January 1, 1970 UTC). A 10-digit value is usually seconds.
How can I convert milliseconds to seconds?
Divide by 1,000. For example, 1708560000000 milliseconds equals 1708560000 seconds.
Why is my converted result off by hours?
The timestamp is likely correct, but you are viewing it in a different timezone. Compare using UTC and then switch to local display.
Can Unix milliseconds include timezone information?
No. Unix timestamps do not store timezone data. Timezone is only applied when formatting the value for display.