Time Zone Converter
Convert a time between any two time zones. Handles DST automatically.
Scheduling across time zones is deceptively error-prone: a single mistake means a missed interview, a call no one joins, or a friend woken at 3 a.m. This converter translates a time from one zone to another instantly, so you can plan international meetings, calls, flights, and live events with confidence rather than counting hours on your fingers and hoping you got the direction right.
As remote work, global teams, and online communities become the norm, time-zone math has gone from an occasional nuisance to a daily task. Whether you are a freelancer coordinating with overseas clients, a traveler catching a connection, or a fan trying to watch a live stream at the right moment, the tool gives you the local time on both ends. The page also explains the quirks — UTC offsets, daylight saving, and the date line — that make time zones trickier than they first appear.
Plug in some numbers —
we'll crunch.
How to use
- 1Select a date — the time zone converter uses noon (12:00) on that date.
- 2Choose the source time zone.
- 3Choose the destination time zone.
- 4See the converted time with DST handled automatically.
How it works
Every time zone is defined as an offset from Coordinated Universal Time (UTC), the global reference. New York's Eastern Time is UTC−5, London is UTC+0, Tokyo is UTC+9, and so on. To convert between two zones, you find the difference between their offsets and add or subtract that many hours: Tokyo (UTC+9) is fourteen hours ahead of New York (UTC−5), because 9 − (−5) = 14.
The complication is Daylight Saving Time. Many regions shift their clocks forward an hour in spring and back in autumn, and they do so on different dates — or not at all. That means the gap between two cities is not fixed: New York to London is usually five hours, but for a few weeks each year, when one has switched and the other hasn't, it temporarily becomes four or six. A good converter accounts for these seasonal shifts automatically.
Worked examples
Scheduling a New York–London call
You want to call London at 9:00 AM their time, from New York.
- London is normally 5 hours ahead of New York.
- Subtract 5 hours: 9:00 AM London = 4:00 AM New York.
9 AM in London is 4 AM in New York — far too early. Shifting the call to 2 PM London (9 AM New York) gives both sides a civilized hour, which is the whole point of converting before you invite anyone.
Catching a live event across the date line
A product launch streams at 10:00 AM Tokyo time and you are in Los Angeles.
- Tokyo is UTC+9; Los Angeles is UTC−8 (or −7 in summer).
- The gap is about 17 hours, with Tokyo ahead.
- 10 AM Tokyo minus 17 hours lands the previous evening in LA.
The stream airs around 5:00 PM the previous day in Los Angeles — and the date is different. Crossing many zones makes the calendar date shift, which is exactly where manual math goes wrong.
Tips & common mistakes
Daylight saving is the number-one cause of time-zone mistakes. Because regions switch on different dates (and some, like most of Asia, never switch), the offset between two cities can change by an hour for a few weeks twice a year. Never assume a fixed gap around late March and early November — always re-check.
Watch the date, not just the hour. When you cross many zones, the local day can be different on each end, so '9 AM Monday' for you might be Sunday night or Tuesday morning for them. Confirming both the time and the date prevents the embarrassing 24-hour miss.
For recurring international meetings, agree on a reference zone (UTC is the neutral choice) and use a shared calendar that auto-adjusts, so no one has to do mental math each week. When inviting people, state the time in their local zone explicitly — 'your time' — to remove ambiguity. This tool reflects standard offsets and daylight-saving rules, but always double-check critical, can't-miss events.
Frequently asked questions
Last reviewed: June 2026
About this calculator
Convert a time between any two time zones. Handles DST automatically.