Time Tools
Convert Unix timestamps to human-readable dates and vice versa. Live-updating clock, auto-detect seconds/milliseconds, and multiple output formats.
Now to load it into the converter, or Copy to grab it directly.Enter Unix timestamp (seconds or milliseconds)... box, then press Convert (or hit Enter).Converted Formats panel: Unix (seconds), UTC, Local, ISO 8601, RFC 2822, and Relative.Copy on any format row to copy just that value to your clipboard.Select a date to convert to timestamp field — the seconds and milliseconds appear instantly, with Copy to grab them.Server logs often print raw epoch values. Convert them to UTC or your local time to see exactly when an event happened.
Stripe, GitHub, JWTs, and many databases return time as seconds or milliseconds. Paste a value to read it as a real date.
Automatic seconds-vs-milliseconds detection keeps a 13-digit value from being misread as a 1970 date — and vice versa.
Generate ISO 8601 and RFC 2822 output for HTTP headers, feeds, and JSON payloads without hand-formatting.
The Relative row turns any timestamp into "3 days ago" or "in 2 hours" — handy for notifications and audits.
Everything runs in your browser. Your timestamps never leave the page or touch a server.
A Unix timestamp is the number of seconds since the Unix epoch — 1970-01-01 00:00:00 UTC. It's a timezone-free way to represent a single moment in time.
By digit count. A value with 13 or more digits is treated as milliseconds; a shorter value is treated as seconds. The detected unit is shown under the input.
Small values are interpreted as seconds since 1970. For example, 100 means 100 seconds after the epoch, not the year 100. Use a 13-digit millisecond value if you meant a more recent time.
Timestamps themselves are UTC. The UTC, ISO 8601, and RFC 2822 rows are shown in UTC, while the Local row uses your device's timezone.
Both are standard date formats. ISO 8601 (e.g. 2026-08-13T20:56:00.000Z) is common in JSON and APIs; RFC 2822 (e.g. Thu, 13 Aug 2026 20:56:00 +0000) is used in email and HTTP headers.
Systems storing time in a signed 32-bit integer overflow at 2147483647 seconds — 2038-01-19 03:14:07 UTC. This tool runs in JavaScript, which handles dates well beyond that range.
No. All conversion happens locally in JavaScript, and the live clock reads your device's time. Nothing is uploaded, stored, or logged.