Unix Timestamp Converter

Convert epoch values across seconds, milliseconds, microseconds, and nanoseconds with explicit UTC and local-time output.

Local processingYour input stays in this browser tab.

Timestamp to date

Enter one Unix value and choose its precision.

Unix timestampTimestamp precision

Automatic detection uses digit length. Choose a unit when precision must be explicit.

Converted date

UTC, local time, and every Unix precisionResults appear after conversion.

Date to Unix timestamp

This field is interpreted in your browser's local time zone.

Local date and time

Seconds, milliseconds, microseconds, or nanoseconds?

Unix time counts from 00:00:00 UTC on January 1, 1970. Many systems store whole seconds, while JavaScript commonly uses milliseconds. Logs and databases may retain microseconds or nanoseconds.

A current timestamp is usually 10 digits in seconds, 13 in milliseconds, 16 in microseconds, and 19 in nanoseconds. Automatic detection uses this pattern, but an explicit unit is safer for historical or unusually short values.

Why a timestamp can show the wrong date

A seconds value interpreted as milliseconds lands near January 1970.
A milliseconds value interpreted as seconds is usually outside the supported date range.
UTC and local output represent the same instant but use different clock values.
A date without a time-zone offset is ambiguous; the date input above intentionally uses the browser's local zone.

Exact precision, local output

PayloadHarbor normalizes timestamps with bigint so microsecond and nanosecond digits are not rounded away. JavaScript Date is used only for the human-readable date and supports millisecond resolution, while the original precision remains available in the Unix outputs.