Unix Timestamp Converter

Convert Unix timestamps to readable dates and back. It detects seconds, milliseconds, microseconds and nanoseconds, reads dates exactly, and shows the result in UTC, your local time and any time zone you choose.

  • Seconds to nanoseconds
  • Show in any time zone
  • Exact ISO 8601 reading

Current Unix time

—

Epoch to date

Date to epoch

What a Unix timestamp is

A Unix timestamp counts the time since the epoch, 00:00:00 UTC on 1 January 1970. Because it is a single number with no time zone attached, it identifies the same instant everywhere, which is why logs, databases and APIs use it. A time zone only matters when you display it, so the same timestamp reads as different clock times in different places.

Seconds, milliseconds and beyond

Systems disagree about the unit. Many Unix tools and JWT claims use seconds, JavaScript and Java use milliseconds, and databases and tracing systems may use microseconds or nanoseconds. You can usually tell by length: 10 digits is seconds, 13 is milliseconds, 16 is microseconds and 19 is nanoseconds. The tool detects this and tells you what it assumed. If you paste a value that is much too small or large for what you expect, the unit is the first thing to check, and you can set it yourself.

Integers are read exactly, so a 19-digit nanosecond value keeps its full precision instead of being rounded by floating-point arithmetic.

Dates without a time zone

Turning a date into a timestamp needs a time zone, and many tools quietly pick one for you. JavaScript, for instance, reads 2026-01-01 as UTC but 2026-01-01T00:00 as your local time, so two neighbouring formats can differ by hours. Here, ISO 8601 text is read exactly in the zone you choose, local time or UTC, unless the text carries its own offset such as Z or +02:00. Impossible dates, such as 30 February or hour 24, are rejected instead of being rolled forward into the next month.

Text that is not ISO 8601, such as "Jan 1 2026 9:30 AM", is passed to your browser, whose rules vary, and the tool says so. For anything you need to reproduce, use ISO format.

Show it in any time zone

Pick a zone such as America/New_York or Asia/Tokyo to see the same instant as local time there, including daylight saving. That makes it easy to answer "what time was this for the customer?" without doing the arithmetic by hand.

Pitfalls

A few things cause most timestamp bugs:

  • Mixing seconds and milliseconds is the most common bug: a value 1000 times too large puts a date thousands of years in the future.
  • Signed 32-bit seconds overflow on 19 January 2038 at 03:14:07 UTC (2147483647).
  • Unix time ignores leap seconds, so every day is exactly 86,400 seconds.
  • Always store and compare timestamps, and convert to a time zone only for display.

Frequently asked questions

What is a Unix timestamp?

The number of seconds that have passed since 1 January 1970 at 00:00:00 UTC, known as the epoch. It is the same instant everywhere in the world; only the way it is displayed depends on the time zone.

How does it tell seconds from milliseconds?

By the size of the number: about 10 digits is seconds, 13 is milliseconds, 16 is microseconds and 19 is nanoseconds. The tool tells you what it assumed, and you can choose the unit yourself when the guess is wrong, for example for a very early date.

Why does a date without a time zone give different results on different computers?

Without a zone, the text is read in a zone you pick, which is your local time by default, so two people in different zones get different timestamps. Choose UTC, or write a zone in the text, such as 2026-01-01T09:30:00Z or 2026-01-01T09:30:00+02:00, for a result that is the same everywhere.

Why do some tools treat 2026-01-01 and 2026-01-01T00:00 differently?

JavaScript reads a date on its own as UTC, but a date with a time and no zone as local time. This tool reads both the same way, in the zone you choose.

What is the year 2038 problem?

Systems that store the timestamp as a signed 32-bit number of seconds run out at 03:14:07 UTC on 19 January 2038, which is the value 2147483647. Newer systems use 64 bits.

Does Unix time include leap seconds?

No. Unix time counts every day as exactly 86,400 seconds, so leap seconds are not represented.

Is anything sent to a server?

No. Conversions happen in your browser, using your device clock and time zone data.

More tools like this

All tools →