Anchor one browser-local date and instant, compare it across UTC and selected IANA zones, switch between live/manual time, and align the shared instant by a target-zone hour. Essential for remote teams scheduling meetings, developers debugging time-sensitive APIs, and travelers planning across zones.
Date and time tools
UTC / GMT
UTC
Local Time
UTC
UTC
The matrix formats one Date instant through browser Intl/IANA data; manual datetime-local input begins in the device zone and DST results depend on the browser’s time-zone database.
Follow this implementation-specific workflow for IANA Time Zone Comparison Matrix; each step reflects the controls and limits in the current browser workspace.
Step 1
Decide whether the datetime-local field should represent your device zone; set the exact date and time or enable Live for the current instant.
Step 2
Keep UTC as a reference and add each required IANA zone from the provided preset list.
Step 3
Use the hour selector only when you want to shift the shared instant until the chosen reference zone displays that hour.
Step 4
Compare date as well as time in every row because conversion can cross midnight, a DST transition, or the International Date Line.
Step 5
Record the date, IANA identifiers, and resulting instants before using them in scheduling or an epoch workflow.
Consequence: The Date constructor interprets that control in the browser device’s zone, not in whichever comparison row you intended.
Fix: Set the device zone as the source or translate the desired source-zone wall time into an instant with a zone-aware scheduling system.
Consequence: Offsets change with daylight-saving rules and political updates, while names such as America/New_York select date-specific rules.
Fix: Store the IANA zone ID and date/instant; avoid labels like EST or a hard-coded UTC−5 for general scheduling.
Consequence: A destination can be on the previous or next calendar date, and ambiguous/skipped DST wall times need more context.
Fix: Verify the full localized date plus time and communicate the UTC instant alongside the named zone.
Choose a source instant and named zones, verify every calendar date, then serialize the approved instant as an epoch value for system exchange.
On that date New York is UTC−05:00 and Paris is UTC+01:00 according to IANA rules; summer dates can produce a different relationship around transition weeks.
JavaScript Date interprets it in the browser device’s local zone; the control does not carry an IANA zone identifier.
Intl applies the browser’s date-specific IANA rules, so yes when its time-zone data is current; the app does not ship a separate tz database.
Their browser or operating-system time-zone database versions may differ after a government announces a rule change.
Validation can test an identifier, but the current UI’s add control exposes only its predefined list of twelve zones.
It shifts the shared instant until the selected zone displays that target hour; it does not merely relabel one row or choose minutes.
Selected zones and dates are formatted entirely with browser Date/Intl APIs and are not uploaded or stored by this workspace. It works offline using the time-zone data shipped with the browser or operating system.
