Unix Time Converter

Convert between Unix timestamps and human-readable dates.

Paste a Unix timestamp (seconds or milliseconds) and see the corresponding ISO 8601, UTC, and local-time representations, plus useful metadata like the day of week, day of year, and whether it falls in a leap year. Works the other way too — type a date and get the timestamp.

Common use cases: reading timestamps out of log files, debugging an "off by 24 hours" bug, planning expiry windows, converting JavaScript Date.now() output into something a human can read, and double-checking that your local clock is what you think it is.

Unix Timestamp

Format Guide

Milliseconds
13-digit timestamp (e.g., 1699024800000)
Seconds
10-digit timestamp (e.g., 1699024800)
ISO 8601
2024-11-03T12:00:00Z
Epoch
January 1, 1970 UTC

Frequently asked questions

What is a Unix timestamp?
The number of seconds (or milliseconds, in JavaScript) that have elapsed since the Unix epoch: 00:00:00 UTC on 1 January 1970. A single integer that uniquely identifies an instant in time — and the format almost every operating system, database, and programming language uses internally.
How do I tell seconds from milliseconds at a glance?
By the magnitude. A 10-digit number is seconds (around 2001–2286 in human time). A 13-digit number is milliseconds. If you see 1700000000, that's seconds (≈Nov 2023); 1700000000000 is the same moment in milliseconds.
What's the Year 2038 problem?
Systems that store Unix timestamps in a signed 32-bit integer overflow on 2038-01-19 03:14:07 UTC. Most modern systems use 64-bit timestamps and are unaffected, but legacy embedded systems, some databases, and old file formats still need attention before then.
Why does my converted time look an hour off?
Almost always a UTC-vs-local-time confusion. Unix timestamps are always in UTC. If you're displaying them in your local timezone, expect them to shift by your offset (plus DST when applicable).