Skip to main content

Developer Tools · No account required

Convert Unix Timestamps and ISO Dates

Convert Unix seconds, milliseconds and ISO dates, with explicit timezone handling and readable timezone output.

Instructions, examples and limitations ↓

What this tool does

Translate Unix seconds or milliseconds into an ISO UTC date and a readable time in a selected timezone. Convert an ISO date back to both timestamp units using an explicit timezone offset, avoiding assumptions about the device clock’s timezone.

Enable JavaScript to use the local processing controls. Instructions and examples are available below.

Practical guide

Convert Unix Timestamps and ISO Dates

By MultiZest · Updated

How to use this tool

  1. Select seconds, milliseconds or ISO date as the input format.
  2. Enter the value. ISO input must include Z for UTC or an offset such as +05:00.
  3. Choose the output timezone, convert and compare the ISO, seconds and milliseconds values.

Worked example

Unix 0 seconds is 1970-01-01T00:00:00.000Z. Choosing Asia/Karachi changes the readable display to 05:00 on the same date; the underlying timestamp remains zero.

Seconds and milliseconds are different units

A millisecond timestamp is one thousand times the corresponding second value. Choosing the wrong unit can produce a date far from the intended year. Use the explicit selector instead of guessing from the digit count.

Negative timestamps represent instants before January 1, 1970 UTC. Conversion to whole seconds floors the millisecond value. Fractional numeric inputs are rejected so the unit stays unambiguous.

Timezone conversion and daylight saving

The output timezone is an IANA region such as Europe/London. Your browser’s timezone database determines daylight-saving rules for that region. An ISO offset identifies an instant; a region identifies how that instant is displayed.

Invalid calendar dates are rejected. This converter is for supported JavaScript date ranges, not leap-second accounting or historical calendar research.

Resolve the unit before investigating a strange date

A timestamp copied from an API may be in seconds while a JavaScript Date value is in milliseconds. Choosing the wrong unit can produce an obviously wrong year. Find the unit in the API documentation or source field definition before assuming the number is damaged; the converter lets you choose it explicitly.

For a log investigation, compare the ISO UTC output with a readable time in the relevant region. The timestamp identifies one instant, while the chosen timezone changes how that instant is displayed. Write down the timezone when sharing the result so another person does not read a local time as UTC.

Use offsets for dates and regions for display rules

An ISO date with Z identifies UTC; an explicit offset such as +05:00 identifies the corresponding instant. A date without either can be interpreted differently across devices, which is why this converter requires a timezone in ISO input. That requirement makes a copied result easier to reproduce.

A region such as America/New_York includes daylight-saving rules that a fixed offset does not describe for every date. Check the actual date being converted rather than assuming one offset applies all year. For audit records, keep the original timestamp and UTC representation alongside any human-readable regional display.

Questions and troubleshooting

Does selecting a timezone change the timestamp?

No. It changes the readable representation of the same instant. ISO output always uses UTC.

Why must my date include a timezone?

A date without an offset is ambiguous across devices. Use Z or an explicit offset to identify the intended instant.

Should I label a converted time with a timezone?

Yes. Include UTC, an explicit offset or the selected region. A bare clock time can be ambiguous, especially when people compare logs across regions or daylight-saving transitions.

Continue with a related tool

More detailed guides

Sources and further reading

Found an error or an unclear instruction? Report it. Read our editorial policy and privacy policy.