Time Zone Converter
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.
- Explicit formulas and worked examples
- Check your inputs, then calculate
- Data is calculated in this browser only
Check the stated input format, calculation convention and limits before using the result.
Check the example inputs, then calculate. Your values stay in this browser.
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.
Understand the Time Zone Converter
Choose the right record before calculating
Use fixed mode for deliberately constant UTC offsets, and city mode for named zones on a specific date. City mode resolves seasonal rules and exposes missing or repeated local times. For overlaps choose reject, earlier or later explicitly; a spring-gap local time has no matching instant.
Content and calculation reviewed:
Understand the calculation
How to use it and the math behind it
Four steps to check your inputs and results
- 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.
- Enter Time-zone method, Source time, Source UTC offset hours, Target UTC offset hours, Source local date (city mode), Source city (IANA), Target city (IANA), Repeated local time during autumn clock change in the stated format. Baseline values are for reproduction.
- Check the output unit and convention: Read target time (fixed utc offset) with its stated unit and convention. The default example and the independent worked scenario use different inputs, so compare the assumptions before comparing the numbers.
- Change one input and compare the result. 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.
Time Zone Converter: calendar conventions
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
The detailed guide adds variable definitions, a reproducible example, a practice question and model limitations.
Questions before you calculate
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.
From question to result