Account

What new tool do you want?

Developer Tools

Unix Timestamp Converter

Convert Unix epoch timestamps (seconds, milliseconds, microseconds) to readable dates in any time zone — and dates back to timestamps.

How to use

  1. 1Enter a Unix timestamp or a date such as 2024-03-15 14:30 UTC.
  2. 2Pick a time zone to see the local date and time there.

How it's calculated

Unix time counts seconds since 1970-01-01 00:00:00 UTC, ignoring leap seconds. Inputs with 12–14 digits are read as milliseconds, 15–17 as microseconds.

Frequently asked questions

What is a Unix timestamp?

The number of seconds since midnight UTC on 1 January 1970 (the Unix epoch). It's the same everywhere, regardless of time zone.

Seconds or milliseconds?

Unix and most APIs use seconds (10 digits today). JavaScript's Date.now() and Java use milliseconds (13 digits). We detect which from the length.

What is the year 2038 problem?

Systems storing Unix time as a signed 32-bit integer overflow on 19 January 2038 at 03:14:07 UTC. 64-bit timestamps don't have this limit.

A worked example of the auto-detection

1700000000 (10 digits) is read as seconds and converts to 2023-11-14T22:13:20.000Z, while 1700000000123 (13 digits) is read as milliseconds and converts to 2023-11-14T22:13:20.123Z — the same instant, just 123ms later, because the tool counts digits to guess the unit: 11 or fewer digits means seconds, 12-14 means milliseconds, 15-17 means microseconds, and anything longer is read as nanoseconds. This digit-counting heuristic works because the ranges genuinely don't overlap in practice today — a millisecond timestamp for a 2024 date is always 13 digits, not 10 — but it's worth knowing it's a heuristic, not something encoded in the number itself.

Why the same moment looks different by time zone, but ISO never does

Converting timestamp 0 with the time zone set to America/New_York gives "Wednesday, December 31, 1969 at 7:00:00 PM EST" — five hours before the Unix epoch's midnight UTC — which is a useful double-check that time zone conversion is working correctly, since epoch 0 famously reads as "late December 31, 1969" in any zone west of UTC. The ISO 8601 and RFC 2822 outputs are deliberately always shown in UTC regardless of the selected zone, because those formats are meant for machine-to-machine use (log files, API payloads) where an unambiguous, zone-independent reference point matters more than local readability.

Why the 2038 problem is still relevant to check for

A signed 32-bit integer can represent at most 2,147,483,647 — which in Unix seconds corresponds to 2038-01-19T03:14:07Z, after which it overflows and wraps to a large negative number, interpreted as a date in December 1901. This isn't a historical curiosity: plenty of embedded systems, older databases, and 32-bit C code still store timestamps this way, and pasting a date past 2038 into a system under test here is a fast way to confirm whether your code handles it correctly before it becomes a production incident.

Seconds drop the fraction, and a bad date stops the page

The timestamp box opens on 1700000000, and the time zone opens on UTC. Zone names that contain underscores are shown with spaces in the date label. Unix seconds are the moment cut down to a whole second, so a millisecond value loses its fraction there. The millisecond line keeps the full value. ISO 8601 stays in UTC no matter which zone I pick for the local line. A value the clock cannot represent stops with "That date is out of range." I use that when a number is so large the date falls apart, instead of reading a blank conversion.

Related tools

More: Developer Tools