Epoch / Unix Timestamp Converter

Convert Unix timestamps to human-readable dates and vice versa.

The current Unix epoch time is

1779565004

Timestamp to Date

Date to Timestamp

Also accepts YYYY/MM/DD and other standard formats if typed manually (type="text").

About Unix epoch time

Unix epoch time (also called POSIX time or "epoch seconds") counts the number of seconds that have elapsed since 1970-01-01 00:00:00 UTC, ignoring leap seconds. It is the most common way to represent timestamps in databases, log files, file systems, network protocols, and APIs because it is timezone-free, sortable, and easy to compare.

This converter handles seconds, milliseconds, microseconds and nanoseconds so you can decode timestamps from any source — Postgres, Linux stat, JavaScript Date.now(), Kafka message timestamps, and the exp/iatclaims in a JWT — into a human-readable date and time, in either UTC or your local timezone.

How to use

  1. Paste an integer timestamp into the input. The tool auto-detects whether it is seconds, milliseconds, microseconds or nanoseconds based on the magnitude.
  2. Read the human-readable result in both UTC and your local timezone.
  3. Use the reverse direction to convert a date-time back to epoch in any of the supported precisions.
  4. Copy the value you need with one click.

Common use cases

  • Reading timestamps in raw log files or audit trails.
  • Building time-bounded queries against a Postgres table that stores Unix timestamps.
  • Debugging cache expirations and JWT exp claims.
  • Cross-referencing events across services that use different time units.

Frequently asked questions

What time zone is epoch time in?

None. Epoch time is by definition the number of seconds since 1970-01-01 00:00:00 UTC and is unaffected by time zones. The conversion to a wall-clock time happens during display.

Why is JavaScript timestamps so much larger than the ones in my database?

JavaScript Date.now() returns milliseconds, not seconds. Multiply a Postgres EXTRACT(EPOCH FROM now()) value by 1000 to get the equivalent JS timestamp.

What about the Year 2038 problem?

Systems that store Unix time as a signed 32-bit integer overflow on 2038-01-19. Any modern 64-bit system, including all current operating systems and databases, is safe well past the year 292,277,026,596.

Does this account for leap seconds?

No, and neither does Unix time. Leap seconds are smeared or skipped depending on the operating system; for almost every application this is the right behaviour.

Advertisement