Convert milliseconds to human-readable date and time formats instantly with our free Milliseconds to Date Converter. This tool transforms UNIX timestamps (milliseconds since 1 January 1970) into both UTC and local date/time formats. Perfect for developers, data analysts, and anyone working with timestamps in applications, databases, or APIs.
JavaScript and most modern systems count time in milliseconds since the UNIX epoch, so a value like 1690000000000 is a precise moment that this converter renders in your local timezone and in UTC. To go the other way — turn a chosen date into a timestamp — use the Date to Milliseconds tool, or see the live clock on the Current Date and Time page.
Get the current date and time instantly with our free live online clock. See the exact time in your local timezone and in UTC, the day of the week, and the real-time UNIX timestamp in milliseconds — all updating every second. Perfect for developers, system administrators, and anyone who needs an accurate, always-current world clock with no setup required.
A UNIX timestamp (also called epoch or POSIX time) counts the number of seconds — or milliseconds — that have elapsed since midnight on 1 January 1970 UTC, the so-called UNIX epoch. Because it is a single monotonic number with no timezone attached, it is the most reliable way to store and compare moments in time across systems, databases, and APIs. JavaScript's Date object works in milliseconds since the epoch, which is why this clock displays the value in milliseconds.
The same instant reads differently depending on where you are. UTC (Coordinated Universal Time) is the global baseline — it never observes daylight saving — while your local time applies your region's offset and DST rules. A timestamp of 1690000000000 ms is one exact moment, but it may show as 14:26 UTC and 19:56 in Kolkata on the clock at the same instant. Always store and transmit timestamps in UTC or as epoch milliseconds, and convert to local time only for display.
Two classic pitfalls catch developers out. First, the seconds-vs-milliseconds confusion: many APIs return seconds (10 digits), while JavaScript uses milliseconds (13 digits) — multiply or divide by 1000 to convert. Second, the Year 2038 problem: older 32-bit systems store seconds as a signed 32-bit integer that overflows in January 2038; 64-bit and millisecond-based systems are unaffected. To convert a specific moment, use the Date to Milliseconds tool, or reverse the process with Milliseconds to Date.
A 13-digit millisecond timestamp maps to one exact instant. The UTC reading is fixed; the local reading depends on your timezone:
1690000000000 (milliseconds)UTC: 2023-07-22 08:26:40
Local: depends on your timezone A UNIX timestamp counts time elapsed since the epoch — midnight UTC on 1 January 1970. JavaScript's Date works in milliseconds (13 digits today), while many APIs and Unix shells report seconds (10 digits). Mixing the two is the single most common timestamp bug: a seconds value fed where milliseconds are expected lands decades in the past. This converter expects milliseconds, so multiply a seconds value by 1000 first.
The same instant reads differently across timezones. UTC is the fixed global baseline with no daylight saving; your local time applies your offset. The converter shows both so you can confirm a timestamp regardless of where a user or server sits. Timestamps before the epoch are negative numbers; far-future values may hit limits on 32-bit systems (the Year 2038 problem), but millisecond-based 64-bit JavaScript is unaffected until the year 275760. To convert a date into a timestamp, use the Date to Milliseconds tool.