Skip to content

Unix Timestamp Converter

Convert Unix timestamps to human dates and back, in UTC and local time.

Updated · Examples checked by automated tests

LOCAL WORKSPACENO UPLOAD REQUIRED

Current Unix time

—

Timestamp → date

Date → timestamp

About Unix Timestamp Converter

A Unix timestamp counts the seconds elapsed since midnight UTC on 1 January 1970. It is unambiguous and easy to compare, which is why it appears throughout logs, databases and API payloads - and why it is unreadable at a glance.

This converter translates in both directions, accepts seconds or milliseconds, and displays the result as an ISO 8601 string, a UTC date and a local date, alongside a live clock of the current epoch value.

How Unix Timestamp Converter works in your browser

Unix time counts seconds since 1 January 1970 UTC. The converter accepts seconds and milliseconds, distinguishing them by magnitude: a ten-digit value is seconds, a thirteen-digit value is milliseconds. Getting that wrong is the single most common timestamp bug, and it presents as a date in 1970 or one roughly fifty thousand years away.

Each timestamp is shown in UTC and in your device’s local time zone simultaneously, with the offset stated, because most timestamp confusion is really time zone confusion.

Two limits are worth knowing. Values above 2,147,483,647 — 19 January 2038 — overflow a signed 32-bit integer, which still matters in older systems and in some database columns. And JavaScript dates are precise to the millisecond, so nanosecond timestamps from tracing systems lose their tail here.

When to use it

  • Turning a timestamp from a log line into a readable date while debugging.
  • Checking whether a token or cache entry’s expiry is in the past.
  • Producing a Unix timestamp for a specific date to use in a query or a fixture.
  • Working out whether a discrepancy between two systems is a real gap or a time zone offset.

Worked examples

Convert a Unix timestamp in seconds to a date

Settings: Unit: Auto

Input

1767225600

Expected output

ISO 8601 (UTC): 2026-01-01T00:00:00.000Z
Interpreted as: seconds

A ten-digit value is read as seconds since 1 January 1970 UTC. The tool also shows the same moment in your local time zone and relative to now.

Convert a JavaScript millisecond timestamp

Settings: Unit: Auto

Input

1767225600000

Expected output

ISO 8601 (UTC): 2026-01-01T00:00:00.000Z
Interpreted as: milliseconds

Values with more than eleven digits are read as milliseconds, which is what Date.now() and most JavaScript logs produce. Reading the same number as seconds would give a date tens of thousands of years ahead.

Limits and checks before you use the result

  • Only whole numbers are accepted. Decimal seconds and microsecond or nanosecond timestamps must be truncated to seconds or milliseconds first.
  • Local time uses your device’s time zone and daylight-saving rules. Compare the UTC row when matching logs from servers in other regions.
  • Choose Seconds or Milliseconds explicitly for very old or very distant dates, where digit-count detection can guess the wrong unit.

Frequently asked questions

How do I convert a Unix timestamp to a date?

Paste the number. Ten digits are read as seconds and thirteen as milliseconds, which is the most common cause of a date landing in 1970 or far in the future.

How do I convert a date to a Unix timestamp?

Pick a date and time in the Date → timestamp section. It is read in your local time zone and shown as Unix seconds, Unix milliseconds, ISO 8601 and UTC.

Seconds or milliseconds?

Both. The converter detects the magnitude of the number and tells you which unit it assumed, and you can override the choice.

What timezone is used?

Results are shown in UTC and in your local timezone at the same time, so there is no ambiguity.

What is the year 2038 problem?

Systems storing time in a signed 32-bit integer overflow in January 2038. Modern platforms use 64-bit values and are unaffected.

Guides

Related tools