Developer Tool
Live Updates
Timestamp
Converter
Convert Unix epoch timestamps to human-readable datetime formats. Instantly parse seconds or milliseconds, and generate timestamps from dates. Runs entirely in your browser.
// Total Uses
201
and counting
// Updates
Live
Real-time clock
Current Epoch Time
(Seconds)
1700000000
↓ Epoch to Human Date
GMT / UTC
-
Your Timezone
-
Relative
-
↑ Human Date to Epoch
Seconds
Milliseconds
§ Docs
What is Unix Epoch Time?
The Epoch
Unix time (also known as Epoch time or POSIX time) measures time as the number of elapsed seconds since 00:00:00 UTC on January 1, 1970 (excluding leap seconds). It provides a standardized, timezone-independent timestamp widely used across operating systems, databases, and APIs.
Seconds vs Milliseconds
Standard Unix timestamps are in seconds (10 digits) (e.g. PHP's
time() or Python's time.time()). Modern JavaScript APIs, MongoDB ObjectIDs, and Java use milliseconds (13 digits). Our auto-detect automatically recognizes 10-digit vs 13-digit values.
⊞ Reference
Epoch Time Conversion Reference Table
| Human Duration | Seconds | Milliseconds | Typical Use Case |
|---|---|---|---|
| 1 Minute | 60 | 60,000 | Rate limiting, short OTP tokens |
| 1 Hour | 3,600 | 3,600,000 | API access token expiration (JWT) |
| 1 Day | 86,400 | 86,400,000 | Daily cron jobs, cache TTL |
| 1 Week | 604,800 | 604,800,000 | Session cookies, refresh tokens |
| 1 Month (30.44 days) | ~2,629,743 | ~2,629,743,000 | Billing cycles, monthly subscriptions |
| 1 Year (365.24 days) | ~31,556,926 | ~31,556,926,000 | SSL/TLS certificates, domain registrations |
| Year 2038 Problem | 2,147,483,647 | 2,147,483,647,000 | Max signed 32-bit integer overflow (Jan 19, 2038) |
</> Code
How to Get & Convert Timestamps in Code
⚡ JavaScript / TypeScript
// Current timestamp in seconds
const sec = Math.floor(Date.now() / 1000);
// Seconds to Date
const date = new Date(sec * 1000);
console.log(date.toISOString());
🐍 Python 3
import time
from datetime import datetime, timezone
# Current epoch in seconds
now_epoch = int(time.time())
# Epoch to human datetime (UTC)
dt = datetime.fromtimestamp(now_epoch, tz=timezone.utc)
🐘 PHP
// Current timestamp
$now = time();
// Convert to ISO 8601 / Human format
$human = gmdate('Y-m-d H:i:s \U\T\C', $now);
// Human to timestamp
$timestamp = strtotime('2026-09-03 12:00:00');
🗄️ MySQL / PostgreSQL
-- MySQL
SELECT UNIX_TIMESTAMP(NOW());
SELECT FROM_UNIXTIME(1700000000);
-- PostgreSQL
SELECT EXTRACT(EPOCH FROM NOW());
? FAQ
Frequently Asked Questions
On 19 January 2038 at 03:14:07 UTC, 32-bit signed integers will exceed their maximum value (2,147,483,647 seconds) and wrap around to negative numbers (-2,147,483,648), resetting system clocks to 13 December 1901. Modern operating systems, databases, and programming languages prevent this by upgrading timestamp counters to 64-bit integers, which won't overflow for another 292 billion years.
Unix time strictly treats every day as having exactly 86,400 seconds. When UTC adds a positive leap second (e.g. 23:59:60), Unix time repeats second 86,400 or applies leap smear algorithms (used by Google, AWS, and Cloudflare) to ensure time stays continuous without crashing databases.
A 10-digit number (e.g.
1700000000) represents seconds since the epoch. A 13-digit number (e.g. 1700000000000) represents milliseconds. JavaScript's Date.now() produces 13-digit millisecond timestamps by default.
Absolutely. All time conversions run 100% locally in your browser using JavaScript's
Intl.DateTimeFormat API. No data is ever sent to a server.