There are moments when the question sounds absurdly simple: if it's 3 PM in New York, what time is it in London? You'd think the answer would always be the same. Add five hours, done. But then March rolls around, and suddenly the gap is four hours for a few weeks before snapping back to five. Or you're trying to set up a call with a colleague in Mumbai and discover that India's time zone isn't a clean whole-number offset — it's UTC+5:30, which means the math never rounds neatly. And if you've ever tried to schedule something with someone in Kathmandu, you've encountered UTC+5:45, which feels like the universe is deliberately making things difficult.
The reality is that millions of people deal with time zone conversion every single day. Remote teams scattered across continents need to find overlapping working hours. Travelers need to know when to call home without waking anyone up. Financial traders need to know exactly when foreign markets open in their local time. Parents with kids studying abroad want to FaceTime at a reasonable hour on both ends. And anyone who's ever missed a live event because they forgot to account for the time difference knows the quiet frustration of getting it wrong.
This guide is designed to take the confusion out of time conversion for good. Whether you prefer to do the math yourself or want a tool that handles everything instantly, by the end of this article you'll understand how time zones actually work, how to convert between any two cities on Earth, and how to avoid the sneaky traps — like daylight saving transitions and the International Date Line — that catch even experienced travelers off guard.
How Time Zones Work: A Quick Primer
Before jumping into conversion techniques, it helps to understand why time zones exist and how they're structured. The Earth rotates 360 degrees every 24 hours, which means it turns 15 degrees per hour. In theory, this divides the planet into 24 neat time zones, each spanning 15 degrees of longitude and each exactly one hour apart. In practice, things are far messier.
The entire system is anchored to Coordinated Universal Time, or UTC. UTC is the successor to Greenwich Mean Time and serves as the global reference point — the zero line from which every other time zone is measured. New York, for instance, is UTC-5 during standard time, meaning it's five hours behind UTC. Tokyo is UTC+9, meaning it's nine hours ahead. When you convert time between two cities, what you're really doing is comparing each city's offset from UTC.
But there are far more than 24 time zones. Political boundaries, historical decisions, and practical considerations have carved the map into over 30 distinct offsets. China, despite spanning five geographical time zones, uses a single offset (UTC+8) nationwide. India chose UTC+5:30 as a compromise between its eastern and western extremes. Nepal, perhaps wanting to distinguish itself from its giant neighbor, picked UTC+5:45. The Chatham Islands of New Zealand use UTC+12:45. And the line where one calendar day becomes the next — the International Date Line — zigzags wildly through the Pacific to avoid splitting island nations in half.
The result is a system that looks simple on a textbook diagram but is genuinely complex in practice. Knowing the rules behind it, though, makes conversion much easier.
Step-by-Step: How to Convert Time Between Any Two Cities
There are two ways to convert time between cities: doing the math manually using UTC offsets, or using a time zone converter tool that does it for you. Both have their place, and understanding the manual method makes you better at catching errors even when you're relying on software.
The Manual Method: UTC Offset Math
Every time zone can be expressed as an offset from UTC. To convert time between two cities, you need three pieces of information: the current time in the source city, the UTC offset of the source city, and the UTC offset of the destination city. The formula is straightforward:
Destination Time = Source Time + (Destination UTC Offset − Source UTC Offset)
Let's walk through a concrete example. Suppose it's 2:00 PM in New York and you want to know what time it is in Berlin. New York is on Eastern Standard Time, which is UTC-5. Berlin is on Central European Time, which is UTC+1. The difference is: +1 − (−5) = +6 hours. So 2:00 PM in New York is 8:00 PM in Berlin.
Another example: it's 10:00 AM in Los Angeles (UTC-8 during standard time) and you want to know the time in Tokyo (UTC+9). The difference is: +9 − (−8) = +17 hours. So 10:00 AM plus 17 hours is 3:00 AM the next day in Tokyo. Notice how the conversion pushed us past midnight and into the following calendar day — this is something you always need to watch for when the offset difference is large.
One more: it's 6:00 PM in London (UTC+0 during GMT) and you need the time in Mumbai (UTC+5:30). The difference is +5:30, so it's 11:30 PM in Mumbai. The half-hour offset means you can't just add whole hours — you need to add the minutes too.
Using a Time Zone Converter Tool
Manual math works, but it's error-prone — especially when daylight saving time is involved, when you're tired, or when you're juggling more than two cities at once. A dedicated time zone converter eliminates the guesswork. You select your source city, your destination city, enter the time, and the tool gives you the answer instantly, accounting for DST, half-hour offsets, and date changes automatically.
Time.Global offers a converter that does exactly this. You pick any two cities from a comprehensive global database, and it shows you the current time in both places, the exact offset between them, and whether either city is currently observing daylight saving time. It's especially useful when you're scheduling something days or weeks in advance, because the DST status of a city might change between now and the date you're planning for.
The Tricky Parts of Time Zone Conversion
If time zones were just fixed offsets from UTC, conversion would be trivial. But several real-world complications make it significantly harder. These are the traps that catch people most often.
Daylight Saving Time (DST)
Daylight saving time is the single biggest source of time conversion errors. About 70 countries observe it, but they don't all switch on the same date. The United States and Canada spring forward on the second Sunday of March and fall back on the first Sunday of November. The European Union changes on the last Sundays of March and October. Australia shifts in October and April — but since it's in the Southern Hemisphere, its DST runs during the Northern Hemisphere's winter.
This creates chaotic transition periods. For most of the year, New York is five hours behind London. But for a few weeks in March — after the US springs forward but before the UK does — the gap shrinks to four hours. Then it goes back to five. Then in late October, Europe falls back before the US does, and the gap becomes four hours again briefly. If you've memorized "New York is five hours behind London" as a fixed fact, you'll be wrong roughly four to six weeks per year.
Some regions within the same country don't observe DST at all. Arizona, for instance, stays on Mountain Standard Time year-round — except for the Navajo Nation, which does observe DST. Hawaii never changes its clocks. In Australia, Queensland doesn't use DST while New South Wales does, so two neighboring states can be an hour apart for half the year and on the same time for the other half.
Half-Hour and Quarter-Hour Offsets
Not every time zone is a whole number of hours from UTC. India uses UTC+5:30, which affects over 1.4 billion people — making it the most-used non-standard offset in the world. Iran is UTC+3:30. Afghanistan is UTC+4:30. Myanmar is UTC+6:30. And then there are the rare quarter-hour offsets: Nepal at UTC+5:45 and the Chatham Islands at UTC+12:45.
These non-standard offsets mean you can't simply count hours on your fingers. A 2:00 PM meeting in San Francisco (UTC-8) is 3:30 AM the next day in India (UTC+5:30) — that's a 13-hour-and-30-minute difference. Missing the 30 minutes doesn't just make you slightly late; it can put you in the wrong half-hour slot entirely, which is awkward when calendar apps round to the nearest hour.
The International Date Line
The International Date Line runs roughly along the 180th meridian in the Pacific Ocean, and crossing it means jumping forward or backward an entire calendar day. Time zones to the east of the line (like American Samoa at UTC-11) can be a full 25 or even 26 hours behind time zones to the west (like Kiribati's Line Islands at UTC+14). This means there are places on Earth where it's already tomorrow while nearby islands are still in yesterday.
For most people, the Date Line is a curiosity. But if you're scheduling a call between, say, Honolulu and Auckland, you need to be aware that Auckland is 22 hours ahead during New Zealand's DST — meaning a Monday afternoon call in Hawaii is a Tuesday afternoon call in New Zealand. Getting the day wrong is worse than getting the hour wrong.
Most Common Time Conversions People Search For
Certain city pairs come up over and over again in time zone searches, usually because they represent major business, travel, or personal corridors. Here are the most common conversions, with the standard time differences and notes on DST variations.
New York to London
The time difference between New York and London is 5 hours during standard time (EST to GMT), with London ahead. During DST overlap periods — roughly late March to early November — the gap is still 5 hours because both cities shift their clocks. But during the transition weeks when only one has changed, the difference drops to 4 hours. If it's 9:00 AM in New York, it's 2:00 PM in London (standard time).
Los Angeles to Tokyo
Los Angeles (PST, UTC-8) and Tokyo (JST, UTC+9) are 17 hours apart during standard time, with Tokyo ahead. Japan does not observe daylight saving time, so the gap changes to 16 hours when LA moves to PDT in March. A 5:00 PM Friday in Los Angeles is 10:00 AM Saturday in Tokyo during standard time — so nearly every weekday afternoon call from the West Coast of the US lands on the next morning in Japan.
New York to Paris
New York (EST, UTC-5) to Paris (CET, UTC+1) is a 6-hour difference during standard time. Both observe DST, but they switch on different dates, so for a few weeks per year the difference is only 5 hours. During the summer, when both are on their respective summer times (EDT and CEST), it's back to 6 hours. A 10:00 AM meeting in New York is 4:00 PM in Paris.
London to Dubai
Dubai is on Gulf Standard Time (UTC+4) year-round — the UAE does not observe DST. London, however, shifts between GMT (UTC+0) in winter and BST (UTC+1) in summer. That means the gap is 4 hours in winter and 3 hours in summer. A noon call in London is 4:00 PM in Dubai during winter or 3:00 PM during summer.
Sydney to San Francisco
This one is notoriously confusing because both cities observe DST but in opposite seasons. During the US winter / Australian summer, Sydney (AEDT, UTC+11) is 19 hours ahead of San Francisco (PST, UTC-8). During the US summer / Australian winter, Sydney (AEST, UTC+10) is 17 hours ahead of San Francisco (PDT, UTC-7). And during the transition weeks, the difference can be 18 hours. Finding a reasonable overlapping work hour between these two cities is genuinely hard.
Chicago to Berlin
Chicago (CST, UTC-6) and Berlin (CET, UTC+1) are 7 hours apart in winter. Both spring forward, but on different dates, so the gap temporarily becomes 6 hours for a few weeks in March. During summer (CDT and CEST), it's 7 hours again. An 8:00 AM start in Chicago is 3:00 PM in Berlin.
Best Tools for Converting Time Between Cities
While manual conversion is a useful skill, the smartest approach is to use a reliable tool and save your mental energy for the meeting itself rather than the arithmetic required to schedule it. Here are the most practical options.
Time.Global Time Zone Converter
Time.Global provides a clean, fast time zone converter that lets you select any two cities and see the converted time instantly. It automatically accounts for DST, shows you the current UTC offset for each city, and indicates whether either location is currently observing daylight saving time. You can also convert times for future dates, which is critical when scheduling across DST transitions. The city comparison pages on Time.Global are especially useful — they show you the time difference, overlapping business hours, and a visual timeline for any city pair.
Meeting Planners and World Clocks
If you regularly work with people in three or more time zones, a world clock or meeting planner is more useful than a simple converter. These tools show you the current time in multiple cities simultaneously and let you drag a slider to find a time that works for everyone. Time.Global's meeting planner is designed specifically for this — you add the cities you care about, and it highlights the overlapping business hours in green so you can visually identify the best meeting window.
Calendar Apps with Built-In Conversion
Google Calendar, Outlook, and Apple Calendar all support multiple time zones. You can display a secondary time zone alongside your primary one, and when you create events, the calendar automatically converts the time for each attendee based on their configured location. This is the most seamless solution for recurring meetings, because the calendar handles DST transitions automatically — you set the meeting once and it adjusts throughout the year.
Tips for Never Getting Time Zones Wrong
After years of watching people (and occasionally being the person) who shows up to a call an hour early, an hour late, or on the wrong day entirely, a few habits stand out as genuinely effective at preventing time zone mistakes.
1. Always Specify the Time Zone When Sharing a Time
Never send a message that says "Let's meet at 3 PM" without specifying whose 3 PM you mean. Write "3 PM ET" or "3 PM London time" or "15:00 UTC." This one habit eliminates the majority of scheduling confusion. If you're posting a public event or deadline, include at least two references — for example, "Applications close at 5:00 PM EST / 10:00 PM GMT." Even better, include a link to a time zone converter with the time pre-filled.
2. Use 24-Hour Format When Precision Matters
The 12-hour clock with AM/PM is a source of confusion in international communication. Not everyone is accustomed to it, and the difference between 12:00 AM and 12:00 PM is genuinely counterintuitive — 12:00 AM is midnight, not noon. The 24-hour format eliminates this ambiguity entirely: 00:00 is midnight, 12:00 is noon, 13:00 is 1 PM, and so on. Military organizations, airlines, and most of the world outside the US use 24-hour time for exactly this reason.
3. Check DST Status Before Scheduling Across Transitions
If you're scheduling a meeting for a date that's more than a couple of weeks away, take 30 seconds to check whether a DST transition will happen between now and then in any of the relevant cities. The two most dangerous periods are mid-March (when North America springs forward but Europe hasn't yet) and late October (when Europe falls back but North America hasn't yet). A quick check on Time.Global will show you the offset for any specific future date.
4. Anchor to UTC for Group Scheduling
When coordinating across more than two time zones, it often helps to express the time in UTC and let each person convert to their own local time. UTC never changes — there's no DST, no ambiguity. Saying "The deadline is 23:59 UTC on April 15" gives everyone a single unambiguous reference point. It's the same strategy used by airlines, international shipping, and space agencies.
5. Double-Check the Date, Not Just the Time
Large time differences can push a conversion into the next (or previous) calendar day. A 7:00 PM Friday call in New York is 9:00 AM Saturday in Sydney. If you're only thinking about hours and not days, you'll be looking at your phone on the wrong morning wondering why nobody joined. Always verify whether the conversion crosses midnight.
Frequently Asked Questions About Time Zone Conversion
How do I find the time difference between two cities?
The fastest way is to use a time zone converter like the one on Time.Global. Enter both cities, and the tool will show you the current time difference, accounting for DST and any non-standard offsets. If you want to do it manually, look up the UTC offset for each city and subtract: if City A is UTC-5 and City B is UTC+2, the difference is 7 hours, with City B ahead.
Does the time difference between two cities ever change?
Yes, frequently. If either city observes daylight saving time, the difference will change at least twice a year. And if both cities observe DST but switch on different dates (which is very common), the difference can change four times a year. The only city pairs with a truly constant time difference year-round are those where neither city observes DST — for example, Dubai to Tokyo is always 5 hours, no matter the date.
What is UTC, and why is it used as the reference for time zones?
UTC stands for Coordinated Universal Time. It's the global time standard maintained by a network of over 450 atomic clocks worldwide. Every time zone on Earth is defined as an offset from UTC — for example, Eastern Standard Time is UTC-5. UTC was chosen as the reference because it's extraordinarily precise (atomic clocks lose less than a second over millions of years) and because it doesn't observe daylight saving time, making it a stable, unambiguous anchor for the entire system.
Why are some time zones offset by 30 or 45 minutes instead of whole hours?
When the standard time zone system was designed, each zone was meant to be one hour wide. But many countries chose offsets that better matched their geographic position or served as a political compromise. India, for example, spans about 30 degrees of longitude — roughly two time zones — but uses a single UTC+5:30 offset as a middle ground. Nepal uses UTC+5:45, partly to differentiate itself from India. These non-standard offsets are permanent political decisions, not mathematical anomalies.
Can a time zone conversion result in a different date?
Absolutely. Any time the conversion crosses midnight, the date changes. If it's 11:00 PM on Tuesday in London, it's already 8:00 AM on Wednesday in Tokyo. Conversely, if it's 1:00 AM on Monday in Sydney, it's still Sunday afternoon in New York. The larger the time difference between two cities, the more likely a conversion will land on a different date. This is especially important when scheduling across the Pacific, where differences can exceed 20 hours.