A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have elapsed since January 1, 1970 at 00:00:00 UTC. This moment is called the Unix epoch. Unix timestamps are widely used in programming, databases, APIs, log files, and web development because they provide an unambiguous, timezone-independent way to represent a point in time as a single number. For example, the timestamp 1700000000 represents November 14, 2023 at 22:13:20 UTC.
The converter divides the timestamp by the appropriate factors to extract years, months, days, hours, minutes, and seconds, accounting for leap years and varying month lengths. Millisecond timestamps (13 digits) are automatically detected and handled. The reverse conversion takes a date and time, converts it to seconds since epoch, accounting for timezone offset.
Enter a Unix timestamp to convert it to a human-readable date, or enter a date to convert it to a Unix timestamp. The converter supports both seconds and milliseconds format. Select your timezone to see the local time equivalent. The current Unix timestamp is also displayed for reference.
32-bit systems store Unix time as a signed 32-bit integer, which will overflow on January 19, 2038. Modern 64-bit systems use 64-bit timestamps, pushing this limit billions of years into the future.
A seconds timestamp has 10 digits (like 1700000000). A milliseconds timestamp has 13 digits (like 1700000000000). JavaScript and Java commonly use milliseconds while Python and PHP use seconds.
Yes. Negative timestamps represent dates before January 1, 1970. For example, -86400 represents December 31, 1969.