Epoch Time Converter
Convert between Unix/Epoch timestamps and human-readable date and time — instantly.
Frequently Asked Questions
About this calculator
Convert a Unix/Epoch timestamp to a readable date and a date back to a timestamp. The current epoch time is shown on top.
Developers meet timestamps in logs, databases, JWTs and APIs. This tool translates them into dates people can read, in your time zone and UTC.
How to use it
- Enter a timestamp and press Convert, or pick a date.
- Read the UTC and local times.
- Copy what you need.
How epoch time works
Unix time counts seconds since 00:00:00 UTC on 1 January 1970 (the epoch), ignoring leap seconds. To convert, divide by 86,400 for days. JavaScript and many APIs use milliseconds, which is 1,000 times larger. Time zones affect only how the date is displayed, never the timestamp. 32-bit signed timestamps overflow on 19 January 2038 at 03:14:07 UTC (2,147,483,647).
Worked example
Landmark timestamps (UTC)
| 0 | 1 Jan 1970 00:00:00 |
| 1,000,000,000 | 9 Sep 2001 01:46:40 |
| 1,700,000,000 | 14 Nov 2023 22:13:20 |
| 2,000,000,000 | 18 May 2033 03:33:20 |
| 2,147,483,647 | 19 Jan 2038 03:14:07 (32-bit limit) |
Tips and common mistakes
- 10 digits is seconds; 13 digits is milliseconds.
- Always store timestamps in UTC and convert for display.
- Beware the 2038 problem with 32-bit systems.
- Dividing by 86,400 gives days since the epoch.
- Use ISO 8601 for human-readable interchange.
Frequently asked questions
What is a Unix timestamp?
The number of seconds since 1 January 1970 UTC.
How do I tell seconds from milliseconds?
Seconds have 10 digits, milliseconds 13.
What is the year 2038 problem?
32-bit signed time overflows on 19 January 2038.
Does a timestamp have a time zone?
No, it is always UTC.
How do I get the current timestamp?
The tool shows it live.
Does it handle leap seconds?
No, Unix time ignores them.