How to Convert Time Zones Without Getting Daylight Saving Wrong
Converting a time between zones is simple arithmetic until daylight saving moves the clocks. Here is how to convert times correctly, plan meetings across zones, and avoid the two days a year that break everything.
Updated October 22, 20266 min read
"Let's talk at 9am my time" is one of the most expensive sentences in remote work. Someone always lands an hour early or an hour late — usually not because they added wrong, but because one of the two places changed its clocks and the other did not. Converting a time zone is easy on an ordinary Tuesday. Doing it correctly every day of the year means knowing where the offsets come from and where they quietly change.
The basic conversion
Every time zone is defined as an offset from Coordinated Universal Time (UTC). New York in winter is UTC−5, India is UTC+5:30, Tokyo is UTC+9. To convert a time, go through UTC: subtract the source offset to get UTC, then add the destination offset.
Example: 9:00 in New York in January (UTC−5) is 14:00 UTC. India is UTC+5:30, so it is 19:30 in Mumbai. The same meeting in July, when New York is on daylight time (UTC−4), is 13:00 UTC and therefore 18:30 in India — a full hour earlier for the person in India, even though nothing changed in India.
Choose the two places, not the abbreviations
Pick cities or regions in the time zone converter rather than typing "EST" or "IST". Abbreviations are ambiguous, and the place determines which rules apply on which date.
Set the actual date
The offset between two places depends on the date. A conversion for next month can differ from today's by an hour.
Read the warnings
If the time falls in a daylight-saving changeover, the converter says so — including when a time does not exist at all, or happens twice.
Why abbreviations cause half the mistakes
Time zone abbreviations are not unique and not even consistent. "IST" means India Standard Time, Irish Standard Time and Israel Standard Time — three offsets spread across four and a half hours. "CST" is Central Standard Time in the US and China Standard Time, which are 14 hours apart. And "EST" strictly means New York's *winter* offset, but people write "EST" all year, including in summer when New York is actually on EDT.
| Abbreviation | Could mean | Offsets |
|---|---|---|
| IST | India / Ireland / Israel | UTC+5:30 / UTC+1 / UTC+2 |
| CST | US Central / China / Cuba | UTC−6 / UTC+8 / UTC−5 |
| BST | British Summer Time / Bangladesh | UTC+1 / UTC+6 |
| EST | US Eastern (winter) — often misused in summer | UTC−5 (UTC−4 in summer as EDT) |
Daylight saving: the two days a year everything breaks
Places that use daylight saving time move their clocks forward one hour in spring and back one hour in autumn — but not on the same dates. The United States and Canada change on the second Sunday in March and the first Sunday in November. The European Union changes on the last Sunday of March and of October. Most of Asia, Africa and South America do not change at all, and the southern hemisphere changes in the opposite season.
So for a few weeks every spring and autumn, the difference between New York and London is four hours instead of the usual five. Recurring meetings set up in one zone shift by an hour for attendees in the other, and nobody's calendar warns them. A good converter shows the weeks when a pair's difference is not its usual one, so you can plan for them instead of discovering them.
Times that do not exist, and times that happen twice
On the spring changeover, clocks jump from 2:00 straight to 3:00, so 2:30 that night never happens. On the autumn changeover, 1:00 to 2:00 happens twice. Scheduling anything in those hours — a backup job, an automated report, a flight connection — is a classic source of bugs. The converter flags both cases instead of silently picking an answer.
Uses the official IANA time zone database, knows each region's daylight-saving rules, warns about changeover hours, and shows an hour-by-hour table for the whole day. Free, and it runs in your browser.
Convert a time between zonesPlanning a meeting across several zones
With two places, any converter works. With five, you need to see everyone's day at once. Compare the places side by side and look for the overlap of working hours — typically 9:00 to 17:00 local time for each person.
- US East Coast + Western Europe: the overlap is roughly 9:00–12:00 New York, 14:00–17:00 London. Comfortable.
- Western Europe + India: about 3.5–4.5 hours apart depending on the season; mornings in Europe meet afternoons in India.
- US West Coast + India: 12.5–13.5 hours apart. There is no shared working day; someone takes an early morning or a late evening.
- London + Sydney: 9–11 hours apart, because both sides change clocks in opposite seasons, so the gap moves several times a year.
When there is no overlap, rotate the inconvenient slot so the same people are not always on the late call, and state the time in each attendee's zone in the invitation.
Converting a list of times at once
Event schedules, shipping cut-offs and conference agendas are lists, not single times. Paste the whole list into the converter's bulk mode and every line is converted in one go, with the same daylight-saving checks applied to each. That avoids the most common spreadsheet mistake: applying one fixed offset to dates that sit on both sides of a changeover.
If you work with times in data files, store them in UTC or with an explicit offset such as 2026-11-03T14:00:00Z or 2026-11-03T09:00:00-05:00. A time written without a zone is a guess waiting to go wrong. For more on handling data files cleanly, see opening CSV files in Excel correctly.
Quick reference: common conversions
| From | To | Usual difference | Changes during the year? |
|---|---|---|---|
| New York | London | London is 5 h ahead | Yes — 4 h for a few weeks in March and Oct/Nov |
| New York | India | India is 9 h 30 min ahead (10 h 30 min in winter) | Yes — India does not change, New York does |
| London | India | India is 4 h 30 min ahead (5 h 30 min in winter) | Yes — UK changes, India does not |
| Los Angeles | New York | New York is 3 h ahead | No — both change on the same dates |
| UTC | Tokyo | Tokyo is 9 h ahead | No — Japan does not use daylight saving |
Treat this table as a sanity check, not a schedule. Countries do change their rules — several have abolished or adopted daylight saving in recent years — which is why a converter built on the maintained IANA database is more reliable than any table you memorise.
Frequently asked questions
What is the time difference between EST and IST?
India (UTC+5:30) is 10 hours 30 minutes ahead of New York in winter, when New York is on EST (UTC−5), and 9 hours 30 minutes ahead in summer, when New York is on EDT (UTC−4). India does not use daylight saving, so the difference changes twice a year.
Why is my meeting an hour off this week?
Almost always because one place changed its clocks for daylight saving and the other did not yet. The US, Europe and the southern hemisphere change on different dates, so for a few weeks a year the usual difference between two cities shifts by an hour.
Should I use UTC or GMT?
For scheduling and data, use UTC. GMT is the UK's winter time zone and shares the same offset, but the UK moves to BST in summer, so 'GMT' is often used loosely. UTC never changes.
Is the time zone converter accurate for future dates?
Yes, as far as the rules are known. It uses the IANA time zone database with each region's daylight-saving rules, so it accounts for changeovers on the date you pick. If a country changes its rules in the future, the database is updated to match.