Skip to content
← All tools

[ CHECK / [t=] ]

Unix timestamp converter

Convert Unix seconds, milliseconds, and dates with explicit offsets.

◉ Stays in your browser

01 / Your timestamp

UTC and your browser’s local timezone describe the same instant. A typed numeric offset is used exactly; it is not a city or a daylight-saving rule.

Supports UTC years 0001–9999 and millisecond precision. Dates without offsets, leap seconds, and ambiguous date formats are rejected.

Processed in your browser. Your input is not uploaded or kept in a history.

02 / Your result

Your result will appear here.
Start with your own input or try an example.

What it does

Turn a Unix timestamp into a readable date, or convert an ISO date into Unix seconds and milliseconds. See the same instant in UTC and your browser’s local timezone. Choose units explicitly so a value is never guessed from its length.

Useful when

  • Read creation or expiry timestamps in an API response.
  • Check whether a log uses seconds or milliseconds.
  • Compare an offset-bearing event timestamp with local time.

How to use it

  1. Choose Unix seconds, Unix milliseconds, or an ISO date with a UTC offset.
  2. Paste a value, try an example, or use the current time.
  3. Convert and compare UTC, local time, and both Unix units. Copy or download the result.

A few useful details

Which date format is accepted?

Use YYYY-MM-DDTHH:mm:ss followed by Z or a numeric offset such as +10:30. Up to 3 fractional-second digits are supported. Dates without offsets, locale formats such as MM/DD/YYYY, invalid calendar dates, leap seconds, and the unknown offset -00:00 are rejected.

How are seconds and milliseconds handled?

Select the input unit explicitly. Seconds may have up to 3 decimal places; milliseconds must be whole numbers. Negative timestamps work. The converter preserves millisecond precision and supports UTC years 0001 through 9999.

Why can the local result differ from the input time?

The input offset, UTC, and your browser’s local timezone can show different clock times for the same instant. The local result uses your browser’s timezone rules for that instant. A typed numeric offset is used exactly and is not interpreted as a city or daylight-saving rule.