Epoch Milliseconds Converter
Convert a value in epoch milliseconds to a readable date in UTC, local time and ISO 8601.
Epoch milliseconds
Epoch milliseconds is the same Unix epoch (1 January 1970, 00:00:00 UTC) counted in thousandths of a second instead of whole seconds. It is the unit JavaScript's Date.now() and many JSON APIs return, and it has 13 digits today, for example 1790000000123.
When to use this instead of Milliseconds to Date
This tool and Milliseconds to Date use the same conversion; both exist because people search for “epoch” and “milliseconds” as different terms for the same idea. Use whichever page you found first, or the Unix Timestamp Converter if you are not sure which unit you have.
Want the background? Read our comprehensive guide: Seconds vs Milliseconds Timestamps.
How to use this tool
- Enter the value in epoch milliseconds.
- Select Convert.
- Read the date in UTC, local time and ISO 8601.
- Copy the value you need.
Examples
The millisecond fraction is kept in the result.
A value from Date.now()
1790000000123 (milliseconds)
- UTC
- 2026-09-21 14:13:20.123 UTC
- ISO 8601
- 2026-09-21T14:13:20.123Z
The Unix epoch itself
0 (milliseconds)
- UTC
- 1970-01-01 00:00:00 UTC
A 10-digit value read as milliseconds
1700000000 (milliseconds)
- UTC
- 1970-01-20 16:13:20 UTC
Only 20 days after the epoch: this is a seconds value read as milliseconds by mistake.
Frequently Asked Questions
How many digits does epoch milliseconds have today?
How do I get the current time in epoch milliseconds?
What if my value has 10 digits?
Are microseconds or nanoseconds supported?
Related tools
- Milliseconds to DateConvert Unix milliseconds, such as Date.now() values, to a date.
- Unix Timestamp ConverterTurn a Unix timestamp into UTC, local time and ISO 8601.
- Current Unix TimestampLive Unix time in seconds and milliseconds. Copy, pause or refresh.
- Unix Timestamp ValidatorCheck whether a value is a valid Unix timestamp, with a clear reason if not.