Time Zone Converter
Convert an explicit local date and time from an IANA source zone to an IANA target zone using the runtime’s Intl time-zone database. Nonexistent daylight-saving times are rejected, and repeated local times require a deterministic earliest or latest instant choice.
By Dr. Hassan Khames EliwaLast updated
Result
Not run
How it works
A local clock reading is not yet an instant
A date and wall-clock time need a zone before they identify an instant. The same local label can occur in different places at different moments. A numeric offset describes one relationship to UTC, while an IANA zone describes a location-based rule set that can change with the date. Enter names such as America/New_York and Europe/London rather than ambiguous abbreviations.
The source fields accept a calendar date and a local time to minute precision. Seconds are fixed at zero. Dates are restricted to the supported planning interval rather than accepting every value JavaScript can represent. The target zone changes the presentation of the resolved instant, not the instant itself. Both the target date and time are returned so a midnight crossing cannot silently lose its day.
Gaps must not be normalized away
When a local clock moves forward, some clock labels do not exist. A converter that silently shifts such a label can conceal a scheduling error. This helper instead tries candidate offsets and round-trips each candidate through Intl in the source zone. If no instant reproduces the requested local fields exactly, it reports a nonexistent-time error. The caller must choose a real time rather than accepting an invented adjustment.
When clocks move back, a local label may identify more than one instant. Earliest chooses the chronologically first matching UTC instant, and Latest chooses the last. These choices are explicit rather than delegated to browser date parsing. Neither choice is universally correct for travel or meetings; confirm which occurrence a ticket or organizer intends.
Runtime data remains part of the answer
The helper uses numeric calendar parts with an explicit locale, calendar, numbering system and hour cycle. It never reads the current clock and never parses an unzoned date string as host-local time. Candidate offsets are sampled around the requested date, then checked by an exact round trip. This accommodates ordinary daylight-saving changes without assuming an hour-sized offset shift.
Intl data comes from the runtime, so governments changing time rules can make an outdated browser disagree with a newer system. For server rendering, identical inputs alone do not guarantee identical outputs if the server and browser carry different time-zone databases. This definition uses the existing explicit-submit widget mode: the server and initial browser render show the same neutral result state, and conversion runs only after a browser submission. No server-generated zone conversion is hydrated against a potentially different browser database. The button uses the shared widget’s generic run label; submitting resolves the entered time rather than running a simulation.
The converter handles a single explicit occurrence. It does not define recurring meeting policy, business hours, travel duration or a promise that future political time rules will remain unchanged.
Worked example
Scenario A: winter meeting
Enter source date 2026-01-15 and time 12:00 in America/New_York, targeting Europe/London. The target result is 2026-01-15 17:00:00 [Europe/London], and the UTC instant is 2026-01-15T17:00:00.000Z. There is 1 matching instant, so the repeated-time selector does not change this result.
Scenario B: repeated autumn clock label
Enter 2026-11-01 at 01:30 in America/New_York and target UTC. Earliest selects 2026-11-01T05:30:00.000Z, displayed as 2026-11-01 05:30:00 [UTC]. Latest selects 2026-11-01T06:30:00.000Z, displayed as 2026-11-01 06:30:00 [UTC]. The match count is 2. The distinct instants share a source clock label, which is why keeping only a local time in a booking record is insufficient.
Expert tips
Common mistakes
- Do not substitute a fixed offset for a geographic zone when you intend local civil time. Offsets can change seasonally or politically, while the entered IANA zone is evaluated for the chosen date.
- Do not let an automatic clock-forward adjustment pass unnoticed. A rejected local time requires clarification from the organizer; choosing a different minute changes the requested appointment.
- Do not assume earliest means standard time or latest means daylight time everywhere. The selector orders matching instants chronologically instead of assigning seasonal labels that can be misleading.
Frequently asked questions
Does this use my current location?
No. Source and target zones are explicit inputs. The helper does not ask for geolocation, infer a zone from the server or use the current time.
Why can a time be invalid?
Civil clocks sometimes move forward and skip local labels. A valid calendar date can therefore contain a local time with no corresponding instant in the source zone.
What if the browser rejects a zone?
Check the IANA spelling and browser support. Abbreviations and free-form numeric offsets are not accepted as substitutes for the named-zone input convention.
Can two computers disagree?
Yes, if their runtime time-zone databases differ after a rule change. Explicit inputs remove host-local parsing ambiguity, but do not freeze the underlying political rule database.
Does this schedule a recurring meeting?
No. Each conversion resolves an explicit date. Recurring events need a separate policy for future zone changes, skipped times and repeated local labels.
Related calculators
Related guides
MathPercentages people get wrong: change, difference and pointsThe denominator determines the answer. Learn to distinguish percentage change, symmetric difference and percentage-point movements.14 November 2026 · 7 min read
MathStandard deviation without the jargonThe average tells you the centre. Standard deviation helps describe the spread, provided you know what the data represents.14 November 2026 · 7 min readSources and standards
About the author
Dr. Hassan Khames Eliwa holds a PhD in Construction & Built Environment and has more than 20 years of international project controls experience. He is Director of Eliwa Project Controls Limited in Auckland and founder of PMMilestone.org and PMMilestone.com.
Buy me a coffee