Epoch ↔ Human-readable date · Seconds & Milliseconds · Any timezone
Instantly convert any Unix timestamp to a readable date, or pick a date and get the corresponding epoch time. Supports seconds and milliseconds, any IANA timezone, and multiple output formats — all computed locally in your browser.
10-digit vs 13-digit timestamps are automatically recognised as seconds or milliseconds.
All IANA timezones available. Pick Europe/Paris, America/New_York or UTC — output updates instantly.
ISO 8601, RFC 2822, UTC string, locale, relative time, week number — all at once.
Convert dozens of timestamps in one click. Paste a list, choose the output format, copy results.
A Unix timestamp counts the number of seconds elapsed since the Unix epoch: January 1, 1970 at 00:00:00 UTC. It is an integer, always positive for dates after 1970, timezone-neutral, and used universally across operating systems, databases and APIs.
A 10-digit number (e.g. 1 735 689 600) is in seconds. A 13-digit number (e.g. 1 735 689 600 000) is in milliseconds. JavaScript's Date.now() returns milliseconds; most Unix system clocks and SQL databases use seconds. The "Auto" unit option detects this automatically.
No. A Unix timestamp represents a single, absolute moment in time. The displayed date and time changes when you switch timezone, but the integer itself is always UTC-based and timezone-agnostic.
On 32-bit systems, the maximum is 2 147 483 647, which corresponds to January 19, 2038 at 03:14:07 UTC — the famous Year 2038 problem. On 64-bit systems the limit is effectively unlimited for any practical date.
JavaScript: Math.floor(Date.now() / 1000) for seconds, Date.now() for ms. Python: import time; int(time.time()). PHP: time(). SQL (PostgreSQL): EXTRACT(EPOCH FROM NOW()).