Milliseconds to Date Converter
Paste a 13-digit epoch value and read it as a date in UTC and your time zone. For seconds, microseconds or nanoseconds, use the epoch converter.
JavaScript needed for live conversion. The results below show a static example for 1735689600000.
Unit: milliseconds
Accepts ISO 8601 (2025-01-01T00:00:00Z), RFC 2822, “YYYY-MM-DD HH:mm:ss” in the selected zone, or “now”.
- UTC
- 2025-01-01T00:00:00Z
- Local time (UTC)
- Wednesday, January 1, 2025 at 12:00:00 AM UTC
- ISO 8601
- 2025-01-01T00:00:00Z
- RFC 2822
- Wed, 01 Jan 2025 00:00:00 +0000
- Relative
- 2 years ago
- Day of year · ISO week
- Day 1 of 365 · 2025-W01-3
- Seconds / ms / µs / ns
- 1735689600 s 1735689600000 ms 1735689600000000 µs 1735689600000000000 ns
- Julian Day
- JD 2460676.50000 · MJD 60676.00000
Runs in your browser. Nothing is sent.
How to use it:
- Paste a millisecond timestamp, such as
1735689600000. The unit is fixed to milliseconds. - Pick a time zone, or keep the one your browser reports.
- Copy the date you need, or copy the JavaScript or Java line that reproduces it.
Convert Epoch Milliseconds to a Date
To convert epoch milliseconds to date and time, divide by 1,000 to get Unix seconds, then read those seconds as a UTC date. The converter above does both steps in one go. For example, 1735689600000 is 1 January 2025 at 00:00:00 UTC, and 1735689600123 is 123 milliseconds later.
This ms timestamp converter keeps the millisecond part in every result, so .123 stays visible in the ISO 8601 row instead of being rounded away. If the value has 16 or 19 digits, the tool warns you that it looks like micro- or nanoseconds and offers the auto-detecting converter.
| Milliseconds | ISO 8601 (UTC) |
|---|---|
0 | 1970-01-01T00:00:00Z |
1000000000000 | 2001-09-09T01:46:40Z |
1735689600000 | 2025-01-01T00:00:00Z |
1735689600123 | 2025-01-01T00:00:00.123Z |
-1500 | 1969-12-31T23:59:58.500Z |
Why JavaScript and Java Use Millisecond Timestamps
JavaScript's Date object stores time as milliseconds since the epoch, and Date.now() returns that number directly. Java made the same choice with System.currentTimeMillis(). Anything built on those platforms, from browser analytics to Android apps and many REST APIs, tends to hand you a 13 digit timestamp.
const d = new Date(1735689600000);
console.log(d.toISOString()); 2025-01-01T00:00:00.000Z import java.time.Instant;
System.out.println(Instant.ofEpochMilli(1735689600000L)); 2025-01-01T00:00:00Z Milliseconds are a practical middle ground. They resolve user actions and network events finely enough for most apps, and the value still fits easily in a 64-bit integer or a JavaScript number. The JavaScript timestamp guide and the Java epoch time guide cover both languages in depth.
Milliseconds, Microseconds and Nanoseconds Compared
Each step down in unit adds three digits. The count of digits is the quickest way to tell them apart.
| Unit | Per second | Digits today | Example |
|---|---|---|---|
| Seconds | 1 | 10 | 1735689600 |
| Milliseconds | 1,000 | 13 | 1735689600000 |
| Microseconds | 1,000,000 | 16 | 1735689600000000 |
| Nanoseconds | 1,000,000,000 | 19 | 1735689600000000000 |
Be careful with nanoseconds in JavaScript. A regular number only holds integers exactly up to 253, which is 16 digits, so a 19-digit value loses its last digits. Use BigInt for them, as this site does. The full breakdown is in seconds vs milliseconds timestamps.
Convert a Date to Milliseconds Since the Epoch
For date to milliseconds, open the Date → Timestamp tab in the converter. Type or pick a date and the milliseconds value appears in the units row. A date without an offset is read in the time zone you selected.
In code, every date API that returns seconds can be multiplied by 1,000, and the JavaScript and Java APIs return milliseconds already:
console.log(Date.parse("2025-01-01T00:00:00Z"));
console.log(new Date(Date.UTC(2025, 0, 1)).getTime()); 1735689600000
1735689600000 Watch the month in Date.UTC: it counts from 0, so January is 0. To work with whole dates and weekdays rather than milliseconds, try the timestamp to date converter.
Milliseconds to Date FAQ
How do I convert milliseconds to a date?
Paste the 13-digit value into the converter above and read the UTC, local and ISO 8601 rows. In code, pass it straight to a date API that expects milliseconds: new Date(1735689600000) in JavaScript or Instant.ofEpochMilli(1735689600000L) in Java. In a language that expects seconds, such as Python or PHP, divide by 1,000 first.
What does a 13-digit timestamp mean?
A 13-digit timestamp is almost always Unix time in milliseconds. Every moment from September 2001 to November 2286 has exactly 13 digits in milliseconds. JavaScript, Java, many REST APIs and analytics exports use this format. Divide by 1,000 to get the familiar 10-digit value in seconds.
Why does my date show the year 57,000?
A millisecond timestamp was read as seconds. The value 1735689600000 treated as seconds lands around the year 57,000, far past the year 9999 where many date libraries stop working. Divide the value by 1,000 before passing it to a function that expects seconds, such as Python's datetime.fromtimestamp() or PHP's date().
How do I get the current time in milliseconds?
Use Date.now() in JavaScript, System.currentTimeMillis() in Java, time.time_ns() // 1_000_000 in Python, or date +%s%3N with GNU date in Bash. Each returns a 13-digit number today. If you only need to copy the current value, the live clock on the current epoch time page has a milliseconds toggle.