Epoch Converter
Convert between Unix timestamps and human-readable dates. Auto-detects seconds vs milliseconds. Everything runs in your browser.
Epoch → Human Date
Human Date → Epoch
Batch Convert
Paste multiple timestamps (one per line). Auto-detects seconds vs milliseconds.
Reference Timestamps
| Name | Epoch (seconds) | Date (UTC) |
|---|---|---|
| Unix Epoch | January 1, 1970 00:00:00 UTC | |
| Y2K | January 1, 2000 00:00:00 UTC | |
| 32-bit Overflow (Y2K38) | January 19, 2038 03:14:07 UTC | |
| GPS Epoch | January 6, 1980 00:00:00 UTC | |
| Max 32-bit unsigned | February 7, 2106 06:28:15 UTC |
What is Unix Epoch Time?
Unix epoch time (also called Unix time, POSIX time, or Unix timestamp) is a system for tracking time as a running count of seconds since the Unix Epoch — January 1, 1970, 00:00:00 UTC. It's the most widely used time representation in computing.
For example, the timestamp 1700000000 represents November 14, 2023 22:13:20 UTC. Timestamps before the epoch are negative numbers.
Seconds vs Milliseconds
Some systems use seconds (10 digits, e.g. 1700000000) while others use milliseconds (13 digits, e.g. 1700000000000). This tool auto-detects which format you're using.
- Seconds: Unix/Linux, Python
time.time(), MySQLUNIX_TIMESTAMP(), PHPtime() - Milliseconds: JavaScript
Date.now(), JavaSystem.currentTimeMillis(), Elasticsearch
The Year 2038 Problem (Y2K38)
Systems storing Unix time as a signed 32-bit integer will overflow on January 19, 2038 at 03:14:07 UTC (timestamp 2,147,483,647). After this point, the time wraps to a negative number, interpreted as December 13, 1901. Most modern systems use 64-bit integers, which won't overflow for ~292 billion years.
Common Commands
# Current epoch (seconds) date +%s # Convert epoch to date date -d @1700000000 # Linux date -r 1700000000 # macOS # Convert date to epoch date -d "2023-11-14 22:13:20 UTC" +%s # Linux # Python python3 -c "import time; print(int(time.time()))" # JavaScript console.log(Math.floor(Date.now() / 1000))