Unix Timestamp Converter

A Unix timestamp counts the number of seconds elapsed since the Unix epoch: January 1, 1970 at 00:00:00 UTC (midnight Greenwich Mean Time). Negative values represent dates before 1970. The epoch was chosen arbitrarily by early Unix developers and became the de facto standard across programming languages, databases, and APIs. Timestamps are time-zone-agnostic — they represent an absolute instant.

Convert timestamp 1,700,000,000 to a date. Divide into manageable chunks: 1,700,000,000 seconds from epoch. Years ≈ 1,700,000,000 ÷ 31,557,600 (seconds per average year) ≈ 53.9 years from 1970 → around 2023–2024. Precisely: 1,700,000,000 = November 14, 2023 at 22:13:20 UTC. In Eastern Time (UTC−5): November 14, 2023 at 5:13:20 PM EST.

Milliseconds multiply by 1,000. JavaScript's Date.now() returns milliseconds: 1,700,000,000,000 ms = same moment as 1,700,000,000 seconds. A common bug passes milliseconds where seconds are expected, producing a date tens of thousands of years in the future. Check whether your system uses 10-digit (seconds) or 13-digit (milliseconds) values.

Reverse conversion: encode November 14, 2023 22:13:20 UTC as a timestamp. Compute seconds from epoch to that instant. Most languages provide built-in functions (Python: datetime.timestamp(), JavaScript: Date.getTime()/1000). Manual calculation requires summing seconds across years including leap years — tedious without software.

Enter a Unix timestamp to see the human-readable date and time in your chosen zone, or enter a date and time to get the corresponding timestamp. Supports both seconds and milliseconds. Indispensable for reading server logs, debugging API responses, and converting database epoch columns.