Convert timestamps, dates, and durations — all in your browser
Supports seconds (10 digits), milliseconds (13), microseconds (16), and nanoseconds (19). Also accepts date strings.
Accepts RFC 2822, ISO 8601, D-M-Y, M/D/Y, Y-M-D, etc.
The Unix epoch is a fixed reference point in time — 00:00:00 UTC on 1 January 1970. A Unix timestamp is simply the number of seconds (or milliseconds) elapsed since that moment. Because it is a single integer with no timezone ambiguity, epoch time is the universal standard for storing and comparing timestamps in databases, APIs, log files, and JWT tokens.
Unix timestamps traditionally use seconds (10-digit integer as of 2025). JavaScript's Date.now() returns milliseconds (13 digits). Many APIs — Stripe, Twilio, AWS — use seconds; browser APIs use milliseconds. Always verify the unit before passing a timestamp to an external service.
On 19 January 2038 at 03:14:07 UTC, a signed 32-bit integer storing a Unix timestamp will overflow to a large negative number. Systems that store timestamps as 32-bit signed integers will misinterpret future dates as 1901. Modern 64-bit systems are not affected — a 64-bit timestamp will not overflow for approximately 292 billion years.