Convert Unix epoch timestamps to human-readable dates and back. Live current timestamp, timezone selection, and common reference timestamps (Unix epoch, Y2K, Y2K38). Supports milliseconds and seconds.
Free, no sign-up — one of the SaaSQuickStart Developer tools.
Unix time counts the number of seconds (or milliseconds) elapsed since the Unix epoch: January 1, 1970, 00:00:00 UTC. This tool auto-detects whether your input is in seconds or milliseconds by checking whether the value exceeds 10 billion — if so it treats it as milliseconds. Conversion is handled entirely by the browser's native Date API with no external dependencies.
A Unix timestamp is the number of seconds elapsed since January 1, 1970, 00:00:00 Coordinated Universal Time (UTC), not counting leap seconds. It is the most common way to represent a point in time in programming because it is timezone-independent.
As of 2024, a seconds timestamp is a 10-digit number (~1.7 billion). A milliseconds timestamp is a 13-digit number (~1.7 trillion). If your number has 13 or more digits, it is almost certainly milliseconds. This tool auto-detects it for you.
Many older systems store Unix timestamps as a signed 32-bit integer. The maximum 32-bit signed value is 2,147,483,647, which corresponds to January 19, 2038, at 03:14:07 UTC. After that point the counter overflows to a large negative number, causing date calculations to fail. Modern systems use 64-bit integers, which won't overflow for hundreds of billions of years.
JavaScript: Math.floor(Date.now() / 1000) for seconds, or Date.now() for milliseconds. Go: time.Now().Unix(). Python: import time; int(time.time()). Bash: date +%s.
Yes. "Unix time" and "Linux time" refer to the same thing — the count of seconds since January 1, 1970 UTC. The name comes from the original Unix operating system; Linux (and macOS, and virtually every other Unix-like system) inherited the same epoch and the same convention, so "Linux timestamp" and "Unix timestamp" are interchangeable terms for the same number.