Unix Timestamp Converter

Convert between Unix epoch timestamps and readable dates in both directions. The converter auto-detects whether a number is seconds, milliseconds, microseconds, or nanoseconds, and shows the result in UTC, your local timezone, ISO 8601, and relative time.

Common uses

• Decode timestamps found in logs, databases, or JWT claims
• Get the current epoch time for a script or test fixture
• Convert a deadline into a timestamp for an API call

Example

1700000000

Tue, 14 Nov 2023 22:13:20 UTC

How does the converter know if my timestamp is seconds or milliseconds?

It looks at the magnitude: values under 100 billion are treated as seconds (about 10 digits today), then 13-digit values as milliseconds, 16 as microseconds, and 19 as nanoseconds. If a value falls on the wrong side of a boundary, pick the unit explicitly from the Unit dropdown.

Is the timestamp I paste sent to a server?

No. Conversion runs entirely in your browser with JavaScript, so timestamps from private logs or tokens never leave your device.

Why is a Unix timestamp the same in every timezone?

A Unix timestamp counts seconds elapsed since January 1, 1970 00:00:00 UTC, so it identifies a single instant regardless of location. Timezones only matter when you format that instant as a date, which is why this tool shows both UTC and your local time.

Can I convert a negative Unix timestamp?

Yes. Negative timestamps represent moments before January 1, 1970 — for example -86400 is December 31, 1969 UTC. The supported range matches the JavaScript Date limit of ±8,640,000,000,000,000 milliseconds, roughly the years 271821 BCE to 275760 CE.

What is the year 2038 problem?

Systems that store Unix time in a signed 32-bit integer overflow at 03:14:07 UTC on January 19, 2038, wrapping to a date in 1901. This converter is not affected — it uses 64-bit numbers — but timestamps read from old 32-bit systems can be.