Epoch to Date Converter
A Unix epoch timestamp counts the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970. It is the standard way computers store points in time, but it is unreadable to humans until you convert it back to a calendar date.
Paste an epoch value (in seconds) below to see both the UTC date and your local date update instantly. The current epoch is shown live for reference, and all conversion happens in your browser.
Current epoch: 1782284433 s · 1782284433270 ms
2021-01-01 00:00:00 UTC1/1/2021, 12:00:00 AM| Epoch (seconds) | UTC date |
|---|---|
0 | 1970-01-01 00:00:00 |
1000000000 | 2001-09-09 01:46:40 |
1609459200 | 2021-01-01 00:00:00 |
1700000000 | 2023-11-14 22:13:20 |
2000000000 | 2033-05-18 03:33:20 |
1609459200→2021-01-01 00:00:00 UTC1,609,459,200 seconds after the epoch is midnight on New Year's Day 2021.
Frequently asked questions
What is the Unix epoch?
It is the reference point 00:00:00 UTC on 1 January 1970. Unix time counts seconds elapsed since that instant, ignoring leap seconds, which makes it a simple integer representation of any moment.
Are epoch timestamps in seconds or milliseconds?
Classic Unix timestamps are in seconds. JavaScript and many APIs use milliseconds, which are 1000× larger. If your value has 13 digits it is probably milliseconds — use the milliseconds tool instead.
Why does the local date differ from UTC?
The same instant looks different depending on your time zone offset. This tool shows both the universal UTC date and the date in your browser's local zone so you can compare them.
What is the year 2038 problem?
Systems that store Unix time in a signed 32-bit integer overflow on 19 January 2038. Modern 64-bit timestamps avoid this entirely, but legacy code may still be affected.