Convert Unix epoch time to human-readable dates — and back. Supports seconds & milliseconds, all timezones, live clock, relative time, and code snippets in JavaScript, Python, SQL, Bash & Go. Free, instant, no signup.
Convert epoch time to readable dates. Instant, free, no login needed.
// Timestamp → Date const ts = 1700000000; const date = new Date(ts * 1000); console.log(date.toLocaleString()); // "Nov 14, 2023, 10:13:20 PM" // Date → Timestamp const now = Math.floor(Date.now() / 1000); // Current timestamp (milliseconds) const ms = Date.now(); // 13 digits
from datetime import datetime, timezone # Timestamp → Date (UTC) ts = 1700000000 dt = datetime.fromtimestamp(ts, tz=timezone.utc) print(dt) # 2023-11-14 22:13:20+00:00 # Date → Timestamp now = datetime.now(timezone.utc) ts = int(now.timestamp())
-- MySQL / MariaDB SELECT FROM_UNIXTIME(1700000000); SELECT UNIX_TIMESTAMP('2023-11-14 22:13:20'); -- PostgreSQL SELECT TO_TIMESTAMP(1700000000); SELECT EXTRACT(EPOCH FROM NOW())::BIGINT; -- SQLite SELECT datetime(1700000000, 'unixepoch');
# Current Unix timestamp date +%s # Timestamp → Human (Linux) date -d @1700000000 # Timestamp → Human (macOS) date -r 1700000000 # Date → Timestamp (Linux) date -d "2023-11-14 22:13:20" +%s
import "time" // Timestamp → Time ts := int64(1700000000) t := time.Unix(ts, 0).UTC() fmt.Println(t) // 2023-11-14 22:13:20 +0000 UTC // Current Timestamp now := time.Now().Unix()
| Event | Timestamp | Date (UTC) |
|---|
↑ Click any timestamp to load it in the converter
A Unix timestamp — also called epoch time, POSIX time, or Unix time — is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC. This reference point is known as the Unix epoch.
For example, the Unix timestamp 1700000000 equals November 14, 2023 at 22:13:20 UTC. Because it counts absolute seconds (not local time), it is timezone-independent — the same integer means the same moment everywhere on Earth.
Timestamps are stored as a 10-digit integer in seconds (standard Unix) or a 13-digit integer in milliseconds (used by JavaScript's Date.now()). This converter auto-detects both formats.
Common use cases: database storage, REST API responses, JWT token expiry (exp claim), AWS Lambda scheduling, Firebase Firestore timestamps, log file timestamps, MongoDB BSON dates, and distributed system clocks.
The most common source of confusion with Unix timestamps is whether a value is in seconds or milliseconds. The rule of thumb is simple:
1700000000 = Nov 14, 2023. Standard Unix, used by most backend systems, Linux, Python, Go, Rust, and Ruby.1700000000000 = same moment. Used by JavaScript (Date.now()), Java (System.currentTimeMillis()), and many front-end APIs.If a timestamp converts to a date far in the future (a 13-digit value interpreted as seconds would give year 56000+), you likely have milliseconds — divide by 1000. This tool auto-detects the format based on digit count.
Storing time as a Unix integer — rather than a formatted string — is best practice for backend development because it is timezone-safe, language-agnostic, and fast to index and sort.
exp, iat, and nbf fields in JWT tokens are Unix seconds. Use the JWT Decoder to inspect them as human-readable dates.Date.now().Math.floor(Date.now() / 1000)int(time.time())time.Now().Unix()date +%sUNIX_TIMESTAMP() (MySQL)
-86400 is December 31, 1969 at 00:00:00 UTC. Most modern systems and languages support negative timestamps for historical dates.| Tool | What you'll find |
|---|---|
| Cron Expression Generator | Build, validate and explain cron expressions in plain English |
| Cron Expression Tester | Test cron syntax and see next 10 scheduled run times |
| AWS EventBridge Cron | 6-field AWS cron format with examples |
| Cron Examples | 50+ ready-to-use cron expressions with descriptions |
| Linux Crontab Examples | Real crontab commands for common tasks |