Time Zone Converter: How to Schedule Across Time Zones Without Making Anyone Miss a Meeting

## The Meeting That Wasn't (And How to Never Have It Again) You send a calendar invite for 2 PM. Your colleague in London joins at 7 PM, which is fine. Your contact in Tokyo doesn't join at all — because you forgot they're in JST, not GMT, and 2 PM EST is 4 AM the next day in Tokyo. Time zone math is genuinely tricky. The same moment in time has a different clock reading in every time zone on Earth, and many regions shift twice a year for daylight saving time — but not all of them, and not on the same dates. Our [time zone converter](/category/tools/time-zone-converter) handles all of this. This guide explains how time zones work and how to schedule across them without mistakes. --- ## How Time Zones Work: The Basics Time zones are defined as offsets from Coordinated Universal Time (UTC), the international time standard. UTC itself doesn't observe daylight saving time. | Offset | Zone Name | Example Locations | |--------|-----------|-------------------| | UTC-8 | Pacific Standard Time (PST) | Los Angeles, Seattle | | UTC-7 | Mountain Standard / Pacific Daylight | Denver, Phoenix, LA in summer | | UTC-6 | Central Standard Time (CST) | Chicago, Dallas, Mexico City | | UTC-5 | Eastern Standard Time (EST) | New York, Miami, Toronto | | UTC+0 | Greenwich Mean Time (GMT/UTC) | London (winter), Reykjavik | | UTC+1 | Central European Time (CET) | Paris, Berlin, Rome | | UTC+5:30 | India Standard Time (IST) | Mumbai, Delhi, Bangalore | | UTC+8 | China Standard Time (CST) | Beijing, Singapore, Perth | | UTC+9 | Japan Standard Time (JST) | Tokyo, Seoul | | UTC+10 | Australian Eastern Standard Time | Sydney (winter) | To convert between any two time zones: find both UTC offsets, calculate the difference, apply it. **Example:** New York (UTC-5) to London (UTC+0) = 5-hour difference. When it's 9 AM in New York, it's 2 PM in London. --- ## The Daylight Saving Time Complication DST shifts the offset by +1 hour for part of the year. The problem: different regions switch on different dates. | Region | DST Start (2026) | DST End (2026) | Offset Change | |--------|-----------------|----------------|---------------| | United States | Mar 8 | Nov 1 | EST→EDT: UTC-5 → UTC-4 | | European Union | Mar 29 | Oct 25 | CET→CEST: UTC+1 → UTC+2 | | United Kingdom | Mar 29 | Oct 25 | GMT→BST: UTC+0 → UTC+1 | | Australia (East) | Apr 5 | Oct 5 | AEST→AEDT: UTC+10 → UTC+11 | | Japan | No DST | — | UTC+9 year-round | | India | No DST | — | UTC+5:30 year-round | | China | No DST | — | UTC+8 year-round | | Arizona (US) | No DST | — | UTC-7 year-round | **Critical window:** Between US DST switch (Mar 8) and EU switch (Mar 29), New York and London are only 4 hours apart instead of the usual 5. A weekly 9 AM ET call lands at 1 PM in London during this window, not 2 PM. This is the most common source of missed international meetings. The [time zone converter](/category/tools/time-zone-converter) shows the current correct offset for any date. --- ## The Most Common Time Zone Pairs (with Current Offsets) ### US Time Zones to Each Other | From | To | Difference | |------|----|------------| | EST | CST | -1 hour | | EST | MST | -2 hours | | EST | PST | -3 hours | | CST | PST | -2 hours | ### US to International | From (EST) | To | Summer (EDT) | Winter (EST) | |-----------|----|--------------|--------------| | New York | London | +5 hours | +5 hours | | New York | Paris/Berlin | +6 hours | +6 hours | | New York | Dubai | +8 hours | +8 hours | | New York | Mumbai | +9:30 hours | +10:30 hours | | New York | Singapore | +12 hours | +13 hours | | New York | Tokyo | +13 hours | +14 hours | | New York | Sydney | +14–15 hours | +16 hours | *Note: India's 30-minute offset (UTC+5:30) means the New York-Mumbai difference is never a round number.* --- ## How to Schedule the Best Meeting Time for Global Teams The golden rule: **find the overlap window first, then schedule.** ### Example: Team Across New York, London, and Singapore | Time (New York, EDT) | London (BST, +5) | Singapore (+12) | |---------------------|-----------------|------------------| | 6:00 AM | 11:00 AM | 6:00 PM ✓ | | 7:00 AM | 12:00 PM | 7:00 PM ✓ | | 8:00 AM | 1:00 PM | 8:00 PM ✓ | | 9:00 AM | 2:00 PM | 9:00 PM (late) | | 10:00 AM | 3:00 PM | 10:00 PM ✗ | The 7–8 AM EST window works for everyone: business hours in London and early evening in Singapore. Earlier than 6 AM ET pushes Singapore past 6 PM, which most prefer to avoid. [Find your overlap window with the time zone converter →](/category/tools/time-zone-converter) --- ## 3 Tips for Scheduling Across Time Zones **1. Always confirm the exact date AND time zone abbreviation.** Don't just say "2 PM" — say "2 PM EDT (UTC-4)" or "2 PM Thursday New York time." When someone says "Tuesday at 3 PM" from a different time zone, ask them to clarify which time zone and whether daylight saving is in effect. **2. Use UTC for technical scheduling.** Server logs, deployments, and database timestamps should always be in UTC. When communicating across global teams, referencing UTC first and then local conversions eliminates ambiguity: "Deploy at 00:00 UTC (8 PM ET / 1 AM London / 8 AM Singapore)". **3. Watch the DST transition windows.** The two to three weeks between when the US switches and Europe switches are the highest-risk period for scheduling errors. Set a calendar reminder for March 8 and March 29 each year. --- ## International Date Line: When "Tomorrow" Means Different Things The International Date Line runs roughly along the 180° meridian in the Pacific Ocean. Crossing it eastward moves you back a calendar day; westward moves you forward. This means that at the same moment in time: - It is Saturday in Los Angeles - It is Sunday in Tokyo (17 hours ahead) - It is still Friday in Honolulu (3 hours behind LA) For calls spanning this line, confirm the day as well as the time: "Friday at 3 PM Los Angeles is Saturday at 8 AM Tokyo." --- ## Useful Time Zone Abbreviations Reference | Abbreviation | Full Name | UTC Offset | |-------------|-----------|------------| | EST / EDT | Eastern Standard / Daylight | UTC-5 / UTC-4 | | CST / CDT | Central Standard / Daylight | UTC-6 / UTC-5 | | MST / MDT | Mountain Standard / Daylight | UTC-7 / UTC-6 | | PST / PDT | Pacific Standard / Daylight | UTC-8 / UTC-7 | | GMT | Greenwich Mean Time | UTC+0 | | BST | British Summer Time | UTC+1 | | CET / CEST | Central European Time / Summer | UTC+1 / UTC+2 | | IST | India Standard Time | UTC+5:30 | | CST (China) | China Standard Time | UTC+8 | | JST | Japan Standard Time | UTC+9 | | AEST / AEDT | Australian Eastern Standard / Daylight | UTC+10 / UTC+11 | --- ## Related Tools - [Date Calculator](/category/tools/date-calculator) — days between dates, deadline countdowns - [Hours Calculator](/category/tools/hours-calculator) — convert time differences to hours and pay - [Date & Time Converter](/category/tools/unit-converter) — convert units including time --- ## Frequently Asked Questions **What is the time difference between New York and London?** In summer (both on daylight time): 5 hours. London is ahead. In winter (both on standard time): 5 hours. During the transition gap in March (US has switched, UK has not): 4 hours. The time zone converter shows the exact current difference for any date. **What time zone should I use for international business calls?** Reference UTC for precision, then convert to each participant's local time. For scheduling tools, use the IANA time zone names (America/New_York, Europe/London, Asia/Tokyo) rather than abbreviations, since abbreviations are ambiguous (CST means Central Standard Time in the US AND China Standard Time). **Does China observe daylight saving time?** No. China uses a single time zone (UTC+8) for the entire country and does not observe DST. Japan, India, and several other countries also do not observe DST. **How do I convert time zones in my head?** Learn your UTC offset first, then convert to UTC, then to the target zone. New York to Tokyo: NY (UTC-4 in summer) → add 4 hours to get UTC → add 9 more hours to get JST (UTC+9) = 13 hours ahead. 9 AM New York = 10 PM Tokyo.