Why the calculation is structured this way
Fixed-offset conversion subtracts the source offset to reach UTC, then adds the destination offset. Named zones instead map a date and local time through IANA rules. An offset is not a zone: New York’s clock relationship changes during the year, and destination dates can shift when offsets cross midnight.
A second scenario you can verify
At 09:00 New York on January 15, 2026, London is 14:00. On March 15 it is 13:00 because the two cities have changed seasonal offsets on different dates. New York November 1, 2026 at 01:30 occurs twice: earlier 05:30 UTC and later 06:30 UTC. New York March 8 at 02:30 does not occur.
What changes the interpretation
Zone rules depend on the runtime’s installed database and can change with legislation. Preserve the named zone and resolved instant for a meeting, and distinguish recurring wall-clock schedules from fixed elapsed intervals. Rejecting ambiguity is more informative than silently selecting an occurrence.
The same city pair can have different seasonal differences
For New York 09:00 on March 22, 2026, London is 13:00: New York has advanced to summer offset while London has not. On March 29 at the same source time, London is 14:00 because both use seasonal offsets. City names without the source date cannot distinguish these answers.
For fixed offsets, source 23:30 at UTC +5.5 and target UTC −4 gives 14:00 on the same date after subtracting 9.5 hours. This applies explicitly specified offsets. It does not promise that a city remains at either offset throughout the year; use city mode when calendar rules matter.
Repeated and missing times need different handling
New York 01:30 on November 1, 2026 occurs twice. The earlier choice corresponds to 05:30 UTC, and the later choice to 06:30 UTC. Showing only the local clock and date leaves an hour of ambiguity. The selection records the intended instant and should accompany a saved appointment or timestamp.
New York 02:30 on March 8, 2026 does not occur because the clock advances through that interval. Earlier or later is not a valid resolution for a missing time; the input is rejected. A clock adjustment also need not equal one hour: Lord Howe’s April 5, 2026 01:45 repeats with instants thirty minutes apart, at 14:45 and 15:15 UTC on April 4.
Store the instant and the intended local meaning
Tokyo conversion of New York 23:30 on July 15, 2026 gives July 16 at 12:30. The target date is therefore as important as its clock. Store an actual instant for a one-time meeting, but retain the local city and recurrence rule for a recurring “09:00 each Monday” schedule, whose UTC time may change seasonally.
City mode uses runtime IANA rules and source and target dates from 1970 through 9999. Future civil-time policy can change, so a distant result is conditional on that database. Updating the runtime and rechecking future events is more reliable than hard-coding today’s offset or assuming historical transitions were whole-hour shifts.
Input reference and units
These values reproduce the model’s demonstration. Replace them with your own records or measurements; they are not recommended targets.
On a small screen, swipe horizontally to see all columns. With a keyboard, focus the table and use the arrow keys.
| Parameter | Demonstration value | How to enter it |
|---|---|---|
| Time-zone method | Fixed UTC offsets | Select the explicitly labeled convention before interpreting the numerical input. |
| Source time | 12:00 | 24-hour HH:MM clock time, not decimal hours. |
| Source UTC offset hours | 0 | Enter source utc offset hours without adding a unit suffix. Scope: Fixed mode keeps offsets from −12 to +14 with whole-minute precision. City mode uses dates from 1970 through 9999 and the browser or server IANA database; future policy changes require an updated runtime. |
| Target UTC offset hours | 8 | Enter target utc offset hours without adding a unit suffix. Scope: Fixed mode keeps offsets from −12 to +14 with whole-minute precision. City mode uses dates from 1970 through 9999 and the browser or server IANA database; future policy changes require an updated runtime. |
| Source local date (city mode) | 2026-01-15 | Source LOCAL Gregorian date in 1970–9999. City mode uses the IANA database to apply date-specific clock-change rules. |
| Source city (IANA) | New York | IANA source zone, whose UTC offset is determined at the entered local date and time, not today. |
| Target city (IANA) | London | IANA target zone; its offset is evaluated for the same instant as the source time. |
| Repeated local time during autumn clock change | Ask for an explicit occurrence | A clock moving backward may repeat a time. Choose earlier or later explicitly; this never makes a skipped spring time valid. |
Time Zone Converter: calendar conventions
Convert fixed UTC offsets or date-aware IANA city zones. City mode uses the entered source date to apply daylight-saving rules, rejects skipped local times and asks you to choose between repeated autumn times. Fixed mode keeps offsets from −12 to +14 with whole-minute precision. City mode uses dates from 1970 through 9999 and the browser or server IANA database; future policy changes require an updated runtime. A missing spring time or skipped date is rejected even when an earlier/later option is selected. That option only resolves actual repeated times; clock output may include historical offset seconds.
A city zone describes rules, not a permanent number. At noon in New York on July 15, 2026 the offset is UTC−4, so the corresponding instant is 16:00 UTC. London is UTC+1 on that date, giving 17:00. On March 15, New York has already changed clocks but London has not, so the same noon converts to 16:00. During the autumn repeat, select the earlier or later occurrence explicitly; skipped spring times produce an error.
fixed: target = source − from offset + to offset; city: match local date/time to an instant using IANA rules, then format in target zone
- mode: Time-zone method. Select the explicitly labeled convention before interpreting the numerical input.
- time: Source time. 24-hour HH:MM clock time, not decimal hours.
- from: Source UTC offset hours. Enter source utc offset hours without adding a unit suffix. Scope: Fixed mode keeps offsets from −12 to +14 with whole-minute precision. City mode uses dates from 1970 through 9999 and the browser or server IANA database; future policy changes require an updated runtime.
- to: Target UTC offset hours. Enter target utc offset hours without adding a unit suffix. Scope: Fixed mode keeps offsets from −12 to +14 with whole-minute precision. City mode uses dates from 1970 through 9999 and the browser or server IANA database; future policy changes require an updated runtime.
- date: Source local date (city mode). Source LOCAL Gregorian date in 1970–9999. City mode uses the IANA database to apply date-specific clock-change rules.
- fromZone: Source city (IANA). IANA source zone, whose UTC offset is determined at the entered local date and time, not today.
- toZone: Target city (IANA). IANA target zone; its offset is evaluated for the same instant as the source time.
- disambiguation: Repeated local time during autumn clock change. A clock moving backward may repeat a time. Choose earlier or later explicitly; this never makes a skipped spring time valid.
- Result units: stated beside each output
- Calculation relationship: fixed: target = source − from offset + to offset; city: match local date/time to an instant using IANA rules, then format in target zone
- Supported domain: see the limits below
Worked example
Time Zone Converter baseline input: Time-zone method: Fixed UTC offsets; Source time: 12:00; Source UTC offset hours: 0; Target UTC offset hours: 8; Source local date (city mode): 2026-01-15; Source city (IANA): New York; Target city (IANA): London; Repeated local time during autumn clock change: Ask for an explicit occurrence. Output: Target time (fixed UTC offset) = 20:00; Day offset = 0. Substitute these values into the displayed equation to reproduce the result.
Reproduce the default scenario
This reproduces the default inputs in the reference table above; it is not an additional independent example. Displayed rounding may differ from intermediate precision.
- Target time (fixed UTC offset)
- 20:00
- Day offset
- 0
Common questions and boundary checks
Is UTC−5 always New York?
No. A fixed offset has no seasonal rules.
Why do I need a date in city mode?
The zone’s offset can depend on that date.
What does earlier/later resolve?
It chooses the first or second instant represented by a repeated local time.
Can a spring-gap time be converted?
It has no matching city-zone instant and is rejected.
Are future offsets guaranteed forever?
No. Time-zone data and civil-time laws can change.
Sources and content notes
Toolify describes the implemented algorithm and its assumptions. Sources below support the topic or applicable rules; they do not endorse this calculator. Examples are illustrative, and published rules take precedence over simplified estimates.
Report a formula, example or translation issue through our contact page. Include the tool name, inputs and expected result so it can be reproduced. Contact Toolify