Convert with an explicit unit and timezone

Browser processing Dates, timestamps and results are calculated in your browser, not sent to or stored by Utilook or an external service. A successful conversion sends only an input-free usage-count request. Privacy Policy

Seconds allow up to three decimal places; milliseconds must be integers. Example: 1709164800 seconds. No exponent notation or separators. The unit is never guessed from digit count.

UTC years 0001–9999, up to 64 input characters. Leap seconds, 24:00 and named regional timezones are not supported. Date conversion ignores the unit selector and outputs both units.

Check the source unit before converting

Unix time measures elapsed time from 1970-01-01 00:00:00 UTC. An API may use seconds while a browser Date uses milliseconds, so the same number can describe different instants. Read the original field specification, then choose its unit. For elapsed calendar days rather than an epoch value, use the Date Difference Calculator.

This tool uses ECMAScript time values, which do not count leap seconds separately. It supports UTC years 0001–9999, but other systems may have narrower ranges. Converting a date after 2038 here does not remove a destination system's 32-bit storage limit.

Different clock readings can identify one instant

09:00 on 2024-02-29 with a +09:00 offset is midnight UTC. The offset says the displayed clock is nine hours ahead of UTC, so subtract nine hours to find UTC. A date or time without an offset leaves that reference ambiguous and is rejected here. Only the supplied fixed offset is applied; regional names and daylight-saving rules are not inferred.

2024-02-29T09:00:00+09:00
= 2024-02-29T00:00:00.000Z
= 1709164800 seconds
= 1709164800000 milliseconds

Keep negative and fractional values intact

-1 millisecond is the instant just before the epoch: 1969-12-31T23:59:59.999Z, or -0.001 seconds. Truncating negative values to whole seconds would identify a different instant, so the output preserves fractions. Seconds allow three decimal places and milliseconds must be integers; finer precision is rejected, not silently rounded.

A nonexistent date such as 2024-02-30 is not rolled into the next month. The tool also rejects 24:00, leap-second values of 60, named timezones and the unknown offset -00:00. These are this tool's input rules, not a claim to implement every ISO date format. Compare the original value, unit and UTC result before using it in another system.

Time-value reference

ECMAScript: time values, epoch and leap seconds

Frequently asked questions

Are 10-digit and 13-digit values detected automatically?

No. Select the input unit yourself. Digit count varies with the date and sign, so check the original API or log specification rather than relying on length.

Does my computer's timezone change the result?

No. Dates require Z or a fixed UTC offset, and results use UTC. The tool does not apply regional daylight-saving rules or a timezone database.

Can it convert dates before 1970 or after 2038?

Yes, within the stated range. Negative values precede 1970, and this tool does not impose a 32-bit seconds limit. Your destination system may still have a narrower supported range.

Will it fix a date such as 2024-02-30?

No. Dates that do not exist are rejected rather than rolled forward. Dates without a timezone, leap-second values of 60, 24:00 and sub-millisecond precision are also rejected.