Convert Unix timestamps (epoch time) to human-readable dates and vice versa. Support for seconds, milliseconds, timezones, and batch conversion.
YYYY=Year, MM=Month, DD=Day, HH=Hour, mm=Minute, ss=Second
Unix timestamp (Epoch time) is the number of seconds elapsed since January 1, 1970 00:00:00 UTC.
• Seconds format: Standard Unix timestamp (10 digits for dates until 2286)
• Milliseconds format: JavaScript and many modern systems use milliseconds (13 digits)
• Time zones: Unix timestamps are always UTC; conversion to local time happens on display
Our Unix Timestamp Converter is the most comprehensive tool for converting between Unix timestamps (epoch time) and human-readable dates. Whether you're debugging logs, working with APIs, or managing databases, our converter handles seconds, milliseconds, multiple timezones, and batch conversions with ease.
10-digit number representing seconds since Jan 1, 1970 UTC. Example: 1710498600
13-digit number used by JavaScript and modern systems. Example: 1710498600000
International standard: 2024-03-15T10:30:00.000Z
Database format: 2024-03-15 10:30:00
// JavaScript Math.floor(Date.now() / 1000) // Seconds Date.now() // Milliseconds # Python import time int(time.time()) # Seconds // PHP time() // Seconds microtime(true) // With microseconds // Java System.currentTimeMillis() / 1000 // Seconds // C++ #include <chrono> auto now = std::chrono::system_clock::now(); auto epoch = now.time_since_epoch(); auto seconds = std::chrono::duration_cast<std::chrono::seconds>(epoch); # Ruby Time.now.to_i # Seconds // Go time.Now().Unix() // Seconds # Bash date +%s # Seconds
| Event | Date | Unix Timestamp |
|---|---|---|
| Unix Epoch Start | Jan 1, 1970 00:00:00 UTC | 0 |
| 1 Billion Seconds | Sep 9, 2001 01:46:40 UTC | 1000000000 |
| 32-bit Overflow | Jan 19, 2038 03:14:07 UTC | 2147483647 |
| 2 Billion Seconds | May 18, 2033 03:33:20 UTC | 2000000000 |
January 1, 1970 00:00:00 UTC was chosen as the Unix epoch because it was a convenient date for the early Unix engineers at Bell Labs. It was recent enough to be relevant but far enough in the past to handle historical dates.
Negative Unix timestamps represent dates before January 1, 1970. For example, -86400 represents December 31, 1969. Most modern systems handle negative timestamps correctly.
Unix time does not account for leap seconds. It assumes all days are exactly 86,400 seconds long. This can cause a one-second discrepancy with UTC during leap second events.
Note: All conversions are performed locally in your browser. No data is sent to our servers, ensuring complete privacy and instant results.