Unix Timestamp Converter
Convert a Unix timestamp to a readable date and time, or a date to a Unix timestamp. Seconds and milliseconds are detected automatically, and results can be shown in any time zone.
How to use the Unix Timestamp Converter
- Choose timestamp → date or date → timestamp.
- Enter the timestamp, or the date and time.
- Pick a time zone to view or interpret the time.
How it works
Unix time (also called epoch time or POSIX time) counts the seconds elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is used by databases, APIs, logs and programming languages because it is a single number that is the same everywhere in the world.
JavaScript and many APIs use milliseconds instead of seconds; a 13-digit number is almost always milliseconds. Systems that store Unix time as a signed 32-bit integer will overflow on 19 January 2038 — the “Year 2038 problem”.
Notable Unix timestamps
| Timestamp | Date (UTC) |
|---|---|
| 0 | Thursday, 1 January 1970 — the Unix epoch |
| 1000000000 | Sunday, 9 September 2001, 01:46:40 |
| 1234567890 | Friday, 13 February 2009, 23:31:30 |
| 1767225600 | Thursday, 1 January 2026, 00:00:00 |
| 2147483647 | Tuesday, 19 January 2038, 03:14:07 — 32-bit limit |
Frequently asked questions
What is a Unix timestamp?
The number of seconds since midnight UTC on 1 January 1970. For example, 1767225600 is 1 January 2026 at 00:00 UTC.
Is my timestamp in seconds or milliseconds?
Current timestamps in seconds have 10 digits; in milliseconds they have 13. The converter detects this automatically.
Do Unix timestamps have time zones?
No. A timestamp is always UTC-based; only its display depends on a time zone.
What is the Year 2038 problem?
Signed 32-bit timestamps can only count to 2,147,483,647, which is reached on 19 January 2038. Modern systems use 64-bit time to avoid it.