Convert epoch time to anything readable.

When Unix was being developed at Bell Labs in the late 1960s, the engineers needed a simple, compact way to represent time. They picked 1970-01-01 00:00:00 UTC as a convenient round date near Unix's creation. The 32-bit signed integer gave them ~136 years of range from that point, which felt comfortable at the time. The convention stuck and became standard across every major operating system and programming language.

Count the digits. A 10-digit number is almost certainly seconds (year ~2001–2286). A 13-digit number is almost certainly milliseconds. 16 digits is microseconds. This converter auto-detects based on digit count.

A signed 32-bit integer maxes out at 2,147,483,647, which corresponds to 2038-01-19 03:14:07 UTC. After that second, systems still using 32-bit time overflow to a negative value, jumping back to 1901. Modern systems use 64-bit timestamps, which won't overflow for billions of years. Read more →

JavaScript: Math.floor(Date.now() / 1000)
Python: int(time.time())
Bash: date +%s
Go: time.Now().Unix()
PHP: time()
Rust: SystemTime::now().duration_since(UNIX_EPOCH).unwrap().as_secs()

No. All conversion happens in your browser using native JavaScript and the Intl API. Nothing is logged, transmitted, or stored. Refresh the page and your input is gone (unless it's in the URL, which is by your choice).

Timezones like America/New_York account for daylight saving time changes automatically. A fixed offset like UTC-5 doesn't — it's wrong for half the year in regions that observe DST. Use IANA names whenever you can.