Unix Timestamp Converter

Convert between Unix epoch values and dates with explicit units, UTC/local interpretation and multiple output formats.

Browser-based · No signup · Transparent assumptions

Open converter Free to use · No signup

01Enter your values
02Adjust your settings
03Review your results

All 23 utilities

Live · current Unix timestamp

0 ms

UTC —

Mode

Unix timestamp

Enter timestamp e.g., 1736947200

Unit

Negative values count back from 1970. 10-digit values are usually seconds; 13-digit values are usually milliseconds.

Quick set

Export

⏱

Enter a timestamp or date

Your converted value, 9 output formats, and component breakdown will appear here.

Date input interpretation

Microseconds truncate sub-millisecond precision. Choose the source unit explicitly.

Calculations run in this browser. Shared URLs can contain input values. Review links before sharing financial, dietary or birth-date information.

When to use this calculator

Inspect an epoch value from a log or API response and compare its UTC and local date representations. Choose seconds, milliseconds or microseconds explicitly so a unit mismatch does not produce the wrong date.

Review the worked example and assumptions below, then use the supported report or copy controls to keep the result with its inputs. Calculations run in this browser; a shared URL can include the values you entered.

How to use Unix Timestamp Converter

Choose timestamp-to-date or date-to-timestamp mode.
Select the epoch unit or date interpretation zone; avoid relying on automatic magnitude detection for early dates.
Review UTC and local outputs, copy formats or export the result.

Epoch units and date interpretation

Unix epoch counts from 1970-01-01T00:00:00Z. Seconds multiply by 1000 to reach JavaScript milliseconds. Milliseconds are unchanged; microseconds divide by 1000 and are truncated toward zero to the browser's millisecond resolution. Negative values represent instants before the epoch.

Worked example

0 seconds = 1970-01-01T00:00:00.000Z
1700000000 seconds = 2023-11-14T22:13:20.000Z
1700000000000 milliseconds represents the same instant

Assumptions and limits

Date uses millisecond precision; sub-millisecond microseconds are truncated. Only integer epoch inputs within safe numeric precision and the JavaScript Date range are accepted. Local datetime input depends on the browser zone and can be ambiguous during daylight-saving overlap; use UTC or the Time Zone Converter for explicit disambiguation. Unix time does not represent leap seconds.

Reference: MDN: Date time values and range. Model/source review: 19 October 2026. See the tool-specific scope and precision limits above.

Frequently asked questions

Should I use seconds or milliseconds?

Select the unit specified by the data source. Magnitude detection is a convenience and is ambiguous for small or historical values.

Can I convert negative timestamps?

Yes, within the supported Date range. They represent dates before January 1970.

Are microseconds preserved?

No. Browser Date output has millisecond resolution; remaining microseconds are truncated toward zero.

Translate a date value for an everyday workflow

Choose the known epoch unit or calendar input, then inspect the UTC and local displays. Keep the unit and zone context when sharing the result.

Scope of this workflow

This single-value utility is distinct from the developer batch converter. Submillisecond detail is not retained and local datetime input can be ambiguous.

Time Zone Converter: Cities, DST & Meeting Times · All utilities · Privacy policy · Contact PixelOkay