Unix Timestamp Converter
Convert epoch time to a readable date and back — seconds, milliseconds or microseconds, in UTC or your time zone.
Current Unix timestamp:
Timestamp → date
Date → timestamp
How to convert a Unix timestamp
- Paste a timestamp — seconds, milliseconds or microseconds are detected automatically.
- Read the date in UTC, your local time zone, ISO 8601 and relative time.
- To go the other way, pick a date and time; tick “Interpret as UTC” if it isn't local time.
What is Unix time?
Unix time counts the seconds elapsed since 1 January 1970 00:00:00 UTC (the “epoch”), ignoring leap seconds. JavaScript and many APIs use milliseconds instead, so 13-digit values are milliseconds. Systems that store Unix time in a signed 32-bit integer overflow on 19 January 2038 at 03:14:07 UTC (timestamp 2147483647).
| Timestamp | Date (UTC) |
|---|---|
| 0 | 1 Jan 1970 00:00:00 |
| 1000000000 | 9 Sep 2001 01:46:40 |
| 1700000000 | 14 Nov 2023 22:13:20 |
| 2000000000 | 18 May 2033 03:33:20 |
| 2147483647 | 19 Jan 2038 03:14:07 |
Frequently asked questions
How do I know if a timestamp is in seconds or milliseconds?
Current dates have 10 digits in seconds and 13 digits in milliseconds. The converter detects this automatically and shows the unit it used.
Does Unix time include time zones?
No. A timestamp is always UTC; only the displayed date depends on the time zone.
How do I get the current timestamp in code?
JavaScript: Math.floor(Date.now() / 1000). Python: int(time.time()). PHP: time(). Bash: date +%s.
What is the year 2038 problem?
Signed 32-bit integers can't store timestamps after 2147483647 (19 January 2038, 03:14:07 UTC). Modern systems use 64-bit time.