Time Zone Converter
Compare a time across cities worldwide, with daylight saving handled for you.
Conversions use your browser’s own time zone database, so daylight saving transitions are handled for the exact date you pick — not just today’s offset.
Compare a specific time across multiple cities and time zones at once, with daylight saving transitions handled automatically — so you don't have to remember which regions are currently observing DST.
Useful for scheduling calls across time zones, or just working out what time it is somewhere else in the world right now.
Daylight saving is where scheduling breaks
The gap between two cities is not constant. New York and London are usually five hours apart, but for about two weeks each year they are four, because the US and EU change their clocks on different dates. A recurring meeting set during that window drifts for everyone.
The southern hemisphere inverts the problem: when Europe springs forward, Australia falls back, so the gap between London and Sydney swings by two hours across the year. And several regions — most of Asia, Africa, and all of India — don't observe DST at all.
- Always agree a meeting time in a named city, not a UTC offset. 'ET' is unambiguous; 'GMT+5' is not, because it might be a summer value.
- Watch for the two- to three-week windows in March/April and October/November when hemispheres are out of step.
- India is UTC+5:30, Nepal UTC+5:45, and parts of Australia UTC+8:45 — half- and quarter-hour offsets are real and catch people out.
- For a recurring series, let the calendar software store the time zone rather than a fixed UTC time.
Finding a workable window across three regions
- List each participant's normal working hours in their own local time.
- Add every city to the comparison above and pick a candidate time.
- Check that nobody lands before 08:00 or after 18:00 local — if that's impossible, rotate which region takes the inconvenient slot.
- Verify the date as well as the time: a 22:00 Tuesday call in London is 06:00 Wednesday in Tokyo.
- Confirm in writing using each participant's local time, so nobody has to do the conversion themselves.
Frequently asked questions
- Does this account for daylight saving time automatically?
- Yes — each city's offset adjusts automatically based on its current DST status for the date you select, not a fixed year-round offset.
- Can I compare more than two time zones at once?
- Yes — add as many cities as you need to see them all side by side for the same moment in time.
- What if a country doesn't observe daylight saving?
- Regions without DST are shown at their fixed offset year-round, and the tool reflects that correctly.
- Why did my recurring meeting suddenly shift by an hour?
- Almost always a DST transition where one participant's region changed its clocks and another's hadn't yet. The gap between two cities isn't constant across the year.
- What's the difference between GMT and UTC?
- For everyday purposes they're the same. UTC is the modern atomic-clock standard; GMT is a time zone based on the Greenwich meridian. Use UTC when precision matters.
- Why is India's offset 5:30 and not a whole number?
- Indian Standard Time is set to the 82.5°E meridian, which falls halfway between two hourly zones. Nepal goes further with UTC+5:45.