Unix Timestamp Converter

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.

• 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.

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.

Use this Unix timestamp converter to translate epoch seconds, milliseconds, microseconds, or nanoseconds into readable local and UTC dates. It also converts human-readable times back into epoch values.

• Inspect API timestamps, database rows, JWT claims, and log events.
• Convert seconds versus milliseconds when debugging date precision issues.
• Copy ISO, UTC, local, and epoch representations for tests or documentation.

Timestamp conversion is pure browser-side date math; no time values are uploaded.

Enter a Unix timestamp or use the reverse converter. The tool detects common precisions and shows multiple readable date formats.

• Ambiguous numeric precision is inferred from value length and magnitude.
• Displayed local time depends on the device time zone and system clock.