Time, Date & Work

Unix Timestamp Converter

Updated Aug 24, 2026 Reviewed Aug 24, 2026
Convert Unix timestamps and zoned date-times in seconds, milliseconds, microseconds, or nanoseconds without losing integer precision.

Unix / POSIX epoch time

Convert machine time and civil time

Enter a signed whole integer. Explicit precision is safest for historic and far-future values.

For timestamp input this changes display only; for date input it defines the exact instant.

Exact integer arithmetic
All four epoch values remain integer strings, so microseconds and nanoseconds are not rounded through JavaScript floating-point numbers.

Result

Calculation summary

Enter values to see the result

Your result, breakdown, assumptions, and warnings will appear here.

Epoch conversion preview

One instant, multiple precisions

Live preview
One instant, multiple precisionsSeconds: 1787902134. UTC calendar date: 2026-08-28.01110101 0110111001101001 01111000Seconds1787902134UTC calendar date2026-08-28Resolved precisionSeconds
The preview shows exact whole epoch units; submit to see UTC and selected-zone representations.

How to use this calculator

  1. 1Choose timestamp-to-date or date-to-timestamp.
  2. 2Select explicit precision or let digit length detect an entered timestamp.
  3. 3Choose a display/input IANA zone and convert.

Formula

Unix timestamp = elapsed SI-style units since 1970-01-01T00:00:00Z

BigInt arithmetic preserves whole seconds, milliseconds, microseconds, and nanoseconds before the exact instant is displayed in UTC and a selected zone.

Calculation steps

  • Validate the integer timestamp or local date-time.
  • Resolve or detect the timestamp precision.
  • Scale with integer nanosecond arithmetic.
  • Create one exact instant.
  • Render UTC, selected-zone, and all four epoch precisions.

Worked example

1,000 Unix seconds is 1970-01-01T00:16:40Z; the equivalent millisecond timestamp is 1,000,000.

Assumptions

  • The Unix epoch is 1970-01-01T00:00:00Z.
  • Input timestamps are whole integers.
  • Automatic detection uses digit length and should be overridden for unusual historic or far-future values.
  • POSIX/Unix time does not count leap seconds separately.
  • Integer strings are retained to avoid JavaScript Number precision loss.

Sources

Frequently asked questions

Is my timestamp in seconds or milliseconds?

Current timestamps usually have 10 digits in seconds and 13 in milliseconds. Auto uses digit length; choose an explicit unit when known.

Why are large values displayed as text?

Nanosecond and some microsecond values exceed safe floating-point integers, so exact integer strings prevent rounding.

What is the year 2038 warning?

Signed 32-bit systems cannot represent seconds after 2038-01-19T03:14:07Z, though modern systems may use wider values.

Are leap seconds included?

No. POSIX-style timestamps map civil time without counting leap seconds as extra timestamp seconds.

Does time zone change the timestamp?

No. A timestamp is an exact instant; the selected zone changes only its human-readable representation. For date-to-timestamp, the zone defines which instant the wall time means.

Time Zone Converter
Convert one local date-time to up to four IANA time zones with daylight-saving offsets, date changes, and ambiguity controls.
Countdown Calculator
Create a live, shareable countdown to an exact date-time in any IANA time zone, with stop-at-zero or count-up behavior.
Date Add & Subtract Calculator
Add or subtract calendar years, months, weeks, and days from a date with explicit month-end handling and a localized result date.