🕐 Unix Timestamp Converter
Convert between epoch time and human-readable dates, in local time and UTC.
What is a Unix timestamp?
A Unix timestamp (also called epoch time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It's the standard way computers store time because it's a single, timezone-independent number — which also makes it hard for humans to read at a glance. This converter translates in both directions.
Seconds vs. milliseconds
Unix time is usually measured in seconds (a 10-digit number today), but JavaScript and many APIs use milliseconds (13 digits). This tool auto-detects which you've pasted based on length, so both work.
Where you'll see epoch time
- Log files and timestamps in Linux (
date +%sprints the current epoch). - API responses, JWT token expiry, and database records.
- Cron jobs and scheduling.
Working in the terminal a lot? See our basic Linux commands guide.
Frequently asked questions
How do I get the current Unix timestamp?
On Linux or macOS, run date +%s in the terminal. In JavaScript, use Math.floor(Date.now() / 1000) for seconds, or Date.now() for milliseconds. In Python, import time; time.time().
Seconds or milliseconds — which is it?
A 10-digit number is seconds; a 13-digit number is milliseconds. This converter detects the length automatically, so you can paste either. If you ever get a date in 1970 or wildly in the future, you've almost certainly mixed up the two units.
What timezone does the result use?
Unix time itself is always UTC — it has no timezone. When converting to a human-readable date, this tool shows it in a clear, unambiguous format so you can line it up against your local time or UTC as needed.
What is the Year 2038 problem?
Systems that store Unix time in a signed 32-bit integer will overflow on 19 January 2038, wrapping around to a negative number. Modern 64-bit systems store time in a much larger integer and aren't affected for billions of years.