Date and time

Normalize ISO Dates Across Offsets and Clock Changes

·

Normalize a list of dates and times before comparing or importing it. Complete calendar dates stay dates, while timestamps become UTC instants. An explicit offset already fixes an instant. An unqualified local time needs the named zone and, during some clock changes, an earlier or later choice.

ISO 8601 Date Normalizer

Verify the seven date and time rows

Select Load example and Normalize dates. Expect five normalized rows and two issues. The leap date stays 2028-02-29. Week 2020-W53-7 becomes 2021-01-03, and ordinal day 2024-060 becomes 2024-02-29. These are calendar dates with no added time.

The -03:30 offset on line 4 moves 31 December to 2027-01-01T03:25:08.120004567Z. The nine significant fraction digits remain intact. Line 7 identifies the invalid date 2027-02-29.

IETF profile of Internet date and time syntax

Choose the earlier or later New York instant

Line 5 reads 2027-11-07T01:30:00 in America/New_York. Earlier gives 2027-11-07T05:30:00Z. Change Repeated local times to Choose later instant, then normalize again. The result moves to 2027-11-07T06:30:00Z. Report as ambiguous leaves that row as an issue.

Line 6 stays an issue in each run because 02:30 is skipped when the clock advances on 14 March 2027. The timestamp on line 4 already includes an offset, so changing the zone or repeated-time setting has no effect on its UTC result.

IANA time-zone database

Select Unix units before entering numbers

Choose Unix seconds and normalize -0.000000001. Its result is 1969-12-31T23:59:59.999999999Z. Use Unix milliseconds for a field documented in milliseconds. The selected unit applies to every number in the batch.

Download normalized values for successful rows in their original order. Download JSON report when the recipient needs to reconcile each original line, the chosen zone, and the reason for any skipped row.

IETF profile of Internet date and time syntax

Common questions

What does a negative zero offset mean?

A timestamp ending in -00:00 supplies a UTC time and says its original local offset is unknown. The JSON report preserves that distinction with a null offset.

Why does the output omit zero fractional digits?

Trailing zeroes after the decimal point do not change the instant. Significant digits up to nanosecond precision are retained.

Why can two browsers interpret a distant local date differently?

Named zones use the browser’s time-zone rules. Browser and operating-system updates can change future or historical offsets for a location.

Sources

Put it into practice.

Related guides