Time Zone Converter
Convert time between cities and time zones instantly. Choose a date and local time to see the exact destination time, UTC offsets, time difference and daylight-saving status that apply on that date.
Convert time between cities and time zones instantly. Choose a date and local time to see the exact destination time, UTC offsets, time difference and daylight-saving status that apply on that date.
9:00 AM in New York is 2:00 PM in London. London is 5 hours ahead on the selected date.
CalendarHours checks the selected civil time zones for seasonal offset changes instead of assuming today's difference lasts all year.
Scan the selected day at two-hour intervals. Each row shows both 12-hour and 24-hour clock formats so you can compare the two zones without doing mental arithmetic.
| Source — 12h | Source — 24h | Destination — 12h | Destination — 24h | Date |
|---|---|---|---|---|
| 12:00 AM | 00:00 | 5:00 AM | 05:00 | Same day |
| 2:00 AM | 02:00 | 7:00 AM | 07:00 | Same day |
| 4:00 AM | 04:00 | 9:00 AM | 09:00 | Same day |
| 6:00 AM | 06:00 | 11:00 AM | 11:00 | Same day |
| 8:00 AM | 08:00 | 1:00 PM | 13:00 | Same day |
| 10:00 AM | 10:00 | 3:00 PM | 15:00 | Same day |
For the selected date, CalendarHours checks where 9:00 AM–5:00 PM business hours overlap in both locations.
Add common reference locations to the same instant without changing the main source and destination conversion.
Add up to four comparison locations to the same converted instant.
Use a dedicated conversion guide when your task matches one of these common directional pairs. For any other combination, keep using the converter above.
A reliable conversion needs more than subtracting two labels. CalendarHours resolves the source local time to an instant, then applies the destination rules for that same instant.
The date matters because the same place can use different UTC offsets at different times of year.
A city or IANA identifier provides civil-time rules. A fixed UTC/GMT offset remains fixed and does not carry seasonal transitions.
The source local time is resolved to a single global instant before the destination clock is calculated.
The destination's active offset, abbreviation and calendar date are determined for that exact instant.
The time difference is calculated from the offsets actually in effect on the selected date, including fractional-hour systems.
If the two places change clocks on different schedules, their relative difference can temporarily change during the year.
CST and IST do not always identify one unique zone. A short code can be reused in different parts of the world, and standard/daylight abbreviations can describe fixed offsets rather than a full location ruleset.
An IANA identifier such as America/New_York can represent changes in civil time over dates. A fixed offset such as UTC−05:00 is only a numerical relationship to UTC.
Choose the next tool based on what you need to do after the conversion.
Detect the IANA zone, current UTC offset and abbreviation reported by your browser.
Detect my zone →Focus on how far apart two zones or locations are and how the gap changes by date.
Compare differences →Find practical working-hour overlap for teams, clients and calls across time zones.
Plan a meeting →Use a reference table for time-zone names, abbreviations and UTC relationships.
Open the chart →Browse geographic time-zone references by country, region and major location.
Browse world zones →Switch to a visual geographic view when boundaries and zone coverage matter.
Open the map →CalendarHours uses location-aware, date-aware time-zone logic rather than permanently hardcoding civil offsets. When you select a city or IANA zone, the converter uses the time-zone data available to your browser for the requested date. Fixed UTC/GMT offsets are treated separately because an offset by itself does not contain daylight-saving or jurisdiction-specific transition rules.
The IANA Time Zone Database is the primary rules source for civil offsets and transitions. The latest IANA release verified for this page is tzdb 2026c, released July 8, 2026. U.S. time and daylight-saving references are checked against NIST and Time.gov.
Reviewed August 18, 2026. The page URL remains evergreen; conversion results change with the selected date, time and time-zone rules.
Choose a source city or zone, enter its local date and time, then choose the destination. CalendarHours resolves that source time to a global instant and applies the destination's rules for the same moment.
Yes. For location-based IANA zones, the applicable UTC offset is calculated for the selected date. That is why the result can change when one place enters or leaves daylight saving time.
Places can change clocks on different dates, follow different seasonal rules or stay on one offset all year. Their relative difference can therefore change during part of the year.
No. EST is specifically UTC−05:00. Eastern Time is an umbrella term that can mean EST or EDT depending on the date and location.
Choose the full meaning, a city or an IANA identifier. A short abbreviation can be reused by unrelated regions, so the converter does not silently assume one meaning when the code is ambiguous.
Yes. Select the date you need. The converter uses the browser's available time-zone data for that date rather than assuming the current offset.
Yes. Inputs such as UTC+05:30, GMT−04:00 and UTC are treated as fixed offsets. Fixed offsets do not contain daylight-saving transitions by themselves.
Time-zone conversion preserves the same global instant. When the destination is far enough ahead or behind the source, its local calendar date can be different.
Use these pages when your task is current-time discovery or visual time-zone geography rather than conversion.