Convert date-aware IANA local times, explicitly resolve repeated clocks and compare multi-location business-hour meeting options.
01 / LOCATIONS, DATE & TIME
Search by city, then choose a region/country match. Exact IANA identifiers stay visible and can always be entered manually. Cities are labels only; the original runtime-based conversion engine determines offsets and daylight saving.
Nonexistent local times are rejected. Repeated clock times require earlier/later selection. Offsets come from the runtime IANA database; future law changes and stale databases can affect results.
02 / CONVERTED DATE & TIME
Supported local input dates are 1900–2100. Use unambiguous IANA location identifiers. Time-zone abbreviations are not unique locations. This is runtime-database conversion, not a guarantee against future rule changes; no third-party time-processing service receives your input.
Inspected UTC 2026-01-15T17:00:00.000Z. 1. America/New_York: 2026-01-15 12:00 UTC-05:00; 2. Europe/London: 2026-01-15 17:00 UTC+00:00
| City / exact IANA zone | Local date | Local time | Date-aware UTC offset | Date change versus source |
|---|---|---|---|---|
| New York, New York, United States · America/New_York | 2026-01-15 | 12:00 | UTC-05:00 | Same calendar day |
| London, England, United Kingdom · Europe/London | 2026-01-15 | 17:00 | UTC+00:00 | Same calendar day |
Date, time and location inputs stay in browser memory. No account, external service, calendar connection or saved travel history is used.
Select your source city or IANA time zone, then enter the local date and time.
Choose the destination city or time zone. If the source time occurs twice during a daylight-saving transition, select the earlier or later occurrence.
Click Calculate to view the converted time, UTC offset, calendar-day difference, and interactive timeline. Use the comparison or meeting-planner modes when needed.
Identifiers such as America/New_York and Europe/London let the runtime apply date-specific timezone rules. Abbreviations can be ambiguous, and a fixed offset is not substituted for a city that observes DST.
Convert date-aware IANA local times, explicitly resolve repeated clocks and compare multi-location business-hour meeting options. Inspect real calculated values through accessible visual controls and review the worked assumptions.
Time Zone Converter calculates locally in browser memory. Financial values, schedules, measurements, health inputs and other entries are not sent to a third-party calculation-processing API or stored as a personal profile. Ordinary page requests may still be logged. Clipboard access occurs only when you choose Copy Result.
Identifiers such as America/New_York and Europe/London let the runtime apply date-specific timezone rules. Abbreviations can be ambiguous, and a fixed offset is not substituted for a city that observes DST.
It gathers nearby runtime offsets, forms candidate instants and formats each candidate back to the exact requested local date/time. If none matches, the local clock time is rejected as nonexistent rather than silently shifted.
When more than one instant matches the local clock, the default rejects ambiguity. Select earlier or later explicitly. Every destination then preserves that one selected underlying UTC instant.
Each destination’s local calendar date is compared with the source local date at the same instant. Larger date-line differences are labeled numerically rather than forced into a one-day indicator.
Across a rolling 24-elapsed-hour view, starts are sampled every fifteen minutes. Every minute of the requested meeting must fit each location’s entered business window and local weekday policy. The result is sampled valid starts, not every possible continuous start.
Yes. Results use the installed Intl/IANA database, which can be stale or differ by runtime. Political rule changes, historical coverage and future assumptions are limitations. Civil 07:00–19:00 timeline bands are not astronomical sunrise/sunset predictions.