Time Zone Converter: How to Schedule Across Time Zones in 2026
Quick Answer
- *UTC (Coordinated Universal Time) is the global time anchor — every time zone is expressed as UTC plus or minus an offset, e.g., New York is UTC−5 in winter.
- *To convert: subtract your UTC offset to get UTC, then add the target offset. New York 3 PM (UTC−5) → UTC 8 PM → London 8 PM (UTC+0) in winter.
- *Daylight Saving Time shifts US clocks +1 hour from the second Sunday of March to the first Sunday of November — complicating cross-border meetings twice a year.
- *About 40% of countries observe DST (IANA, 2024). China, Japan, India, and most of Africa do not — their offsets never change.
What Is UTC and Why Does It Matter?
UTC stands for Coordinated Universal Time. It is the primary time standard used worldwide to regulate clocks and timekeeping, maintained by the International Bureau of Weights and Measures (BIPM) using a weighted average of more than 400 atomic clocks in 70+ national laboratories.
Before UTC, the world relied on Greenwich Mean Time (GMT) — a solar-based standard from the Royal Observatory in Greenwich, England. UTC replaced GMT as the international standard in 1972 because atomic timekeeping is far more precise than astronomical observation. The two differ by less than one second at any moment, but UTC is the correct technical term for global time coordination.
The critical property of UTC: it never observes Daylight Saving Time. UTC is fixed. Every time zone on Earth is defined as UTC plus or minus an offset, and that offset may change when DST begins or ends — but UTC itself stays constant. This makes UTC the reliable anchor for all time conversions, software systems, API timestamps, flight schedules, and international contracts.
How UTC Offsets Work
A UTC offset is a value, expressed in hours and sometimes half-hours, that tells you how far a location's local time is ahead of or behind UTC. Offsets range from UTC−12:00 (Baker Island in the Pacific) to UTC+14:00 (Line Islands, Kiribati) — a total span of 26 hours, which is why some date lines can differ by a full calendar day.
The math is straightforward:
- Local time to UTC: subtract the offset. If it's 9:00 AM in Tokyo (UTC+9), UTC is 9:00 AM minus 9 hours = midnight UTC.
- UTC to local time: add the offset. Midnight UTC in Mumbai (UTC+5:30) = 5:30 AM Mumbai time.
For conversions between two non-UTC zones: convert the source to UTC first, then convert UTC to the target. This two-step method always works correctly and avoids the common mistake of trying to subtract offsets directly.
The 6 US Time Zones and Their UTC Offsets
The continental US spans four time zones. Including territories, there are six distinct zones:
| Zone | Abbreviation | UTC Offset (Standard) | UTC Offset (DST) | Key Cities |
|---|---|---|---|---|
| Eastern | ET | UTC−5 | UTC−4 | New York, Miami, Atlanta |
| Central | CT | UTC−6 | UTC−5 | Chicago, Dallas, Houston |
| Mountain | MT | UTC−7 | UTC−6 | Denver, Phoenix* |
| Pacific | PT | UTC−8 | UTC−7 | Los Angeles, Seattle |
| Alaska | AKT | UTC−9 | UTC−8 | Anchorage, Fairbanks |
| Hawaii–Aleutian | HAT | UTC−10 | no DST | Honolulu |
*Phoenix and most of Arizona observe Mountain Standard Time year-round and never observe DST. They are effectively on Pacific Daylight Time during summer months.
UTC Offsets for Major World Cities
The following reference table shows standard (non-DST) UTC offsets for major cities. Observe DST column indicates whether clocks shift seasonally.
| City | Country | Standard UTC Offset | Observes DST? |
|---|---|---|---|
| London | UK | UTC+0 | Yes (GMT/BST) |
| Paris / Berlin | France / Germany | UTC+1 | Yes (CET/CEST) |
| Cairo | Egypt | UTC+2 | No |
| Moscow | Russia | UTC+3 | No |
| Dubai | UAE | UTC+4 | No |
| Mumbai / Kolkata | India | UTC+5:30 | No |
| Dhaka | Bangladesh | UTC+6 | No |
| Bangkok / Jakarta | Thailand / Indonesia | UTC+7 | No |
| Beijing / Singapore | China / Singapore | UTC+8 | No |
| Tokyo / Seoul | Japan / South Korea | UTC+9 | No |
| Sydney | Australia | UTC+10 | Yes (AEST/AEDT) |
| Auckland | New Zealand | UTC+12 | Yes (NZST/NZDT) |
India's UTC+5:30 and Nepal's UTC+5:45 are among the world's few half- and quarter-hour offsets. The IANA Time Zone Database (the authoritative source used by all major operating systems) tracks 595 distinct named time zones as of 2024, reflecting historical changes, political decisions, and boundary adjustments.
Daylight Saving Time: The Scheduling Wildcard
Daylight Saving Time (DST) is the practice of advancing clocks by one hour during warmer months so that evening daylight lasts longer. It was widely adopted during World War I as an energy-saving measure and has persisted — controversially — in about 40% of countries (IANA, 2024).
US DST Schedule for 2026
- Spring forward: Sunday, March 8, 2026 at 2:00 AM → clocks jump to 3:00 AM (lose one hour of sleep)
- Fall back: Sunday, November 1, 2026 at 2:00 AM → clocks fall to 1:00 AM (gain one hour of sleep)
European DST Schedule for 2026
- Spring forward: Sunday, March 29, 2026 at 1:00 AM UTC (clocks move to 2:00 AM)
- Fall back: Sunday, October 25, 2026 at 1:00 AM UTC
The gap between the US and European clock changes creates a two-to-three week window each spring where the US–Europe offset differs by one hour from its usual value. In late March 2026, Europe springs forward three weeks before the US would have already done so, briefly shrinking the New York–London gap from 5 hours to 4 hours.
Countries That Never Observe DST
Major economies with fixed UTC offsets year-round include China (UTC+8), Japan (UTC+9), India (UTC+5:30), South Korea (UTC+9), Singapore (UTC+8), and virtually all of Africa and Southeast Asia. When scheduling with teams in these regions, their offset never changes — only yours might.
Best Overlap Hours for Remote Teams
According to Axios citing Harvard Business School research (2020), remote workers in different time zones spend 24% less time in synchronous communicationthan co-located teams. Buffer's State of Remote Work (2023) found that 32% of remote workers cite scheduling across time zones as their top collaboration challenge — the single most-cited difficulty.
US East Coast ↔ Western Europe
New York (UTC−5 / −4 DST) and London (UTC+0 / +1 BST) are 5 hours apart in winter and 4 hours apart during US DST. The best overlap window is 9:00 AM – 11:00 AM ET(2:00 PM – 4:00 PM London). This gives both sides a comfortable mid-morning or mid-afternoon slot. Paris and Berlin add one more hour, tightening the window to 9:00 – 11:00 AM ET.
US West Coast ↔ Western Europe
Los Angeles (UTC−8 / −7 DST) is 8–9 hours behind London. Overlap is minimal: 8:00 AM – 9:00 AM PTcatches European afternoons at 4:00–6:00 PM. Later than that and Europe's workday ends. This is genuinely difficult and often requires one side to flex outside normal hours.
US East Coast ↔ India
New York (UTC−5) and Mumbai (UTC+5:30) are 10.5 hours apart in US winter. The narrow overlap is 7:30 AM – 9:00 AM ET(6:00 PM – 7:30 PM Mumbai). Many US–India teams use a standing 8:00 AM ET / 6:30 PM Mumbai slot.
US East Coast ↔ Asia-Pacific
New York and Tokyo (UTC+9) are 14 hours apart. Singapore and Beijing (UTC+8) are 13 hours apart. True working-hours overlap is essentially impossible without one side working early mornings or evenings. Async-first communication via detailed written updates is the practical solution for these pairings.
ISO 8601: The International Scheduling Standard
ISO 8601 is the international standard for representing dates and times, published by the International Organization for Standardization. The format:
YYYY-MM-DDTHH:MM:SS±HH:MM or YYYY-MM-DDTHH:MM:SSZ (Z = UTC)
Example: a meeting scheduled for June 15, 2026 at 2:30 PM UTC would be written as 2026-06-15T14:30:00Z.
Why it matters:
- Eliminates the 06/15/26 (US format) vs 15/06/26 (European format) ambiguity
- Sorts chronologically as a string, which makes logs, filenames, and databases easier to work with
- Supported natively by all major calendar apps, APIs, and programming languages
- Accepted by both Google Calendar and Outlook for event imports
When setting up recurring meetings with international teams, share the ISO 8601 UTC time in meeting invites alongside the local times for each participant. This removes all ambiguity during DST transitions.
Practical Tips for Cross-Time-Zone Scheduling
Rotate the Pain
No single team member should always take the inconvenient slot. If you have US and Singapore team members, rotate who takes the early-morning or late-evening slot for recurring meetings. Document this explicitly in your team's working agreement.
Always State the Time Zone in Writing
“Let's meet at 3 PM” is ambiguous. “Let's meet at 3:00 PM ET (20:00 UTC)” is not. Including the UTC time as a secondary reference protects against DST-transition confusion, especially in the two-week windows when different regions are shifting clocks.
Use UTC for Recurring Systems
For cron jobs, server logs, database timestamps, and automated reports, always use UTC. When a team member in Tokyo and one in New York both look at a UTC timestamp, there is no conversion ambiguity. Converting to local time for display is a UI concern; the data layer should always store UTC.
Watch the Date Line
New Zealand (UTC+12 or UTC+13 during DST) and Hawaii (UTC−10) are on opposite sides of the International Date Line. When it is Monday afternoon in Auckland, it is still Sunday morning in Honolulu. Always specify the full date alongside the time when scheduling across this boundary.
Convert time zones instantly
Use our free Time Zone Converter →Planning a trip? Also see our Flight Time Calculator Guide and Jet Lag Recovery Guide
Related Tools and Guides
- Time Zone Converter — instantly convert any city to any other time zone
- Meeting Cost Guide — calculate the true cost of meetings across your team
- Flight Time Guide — understand how flight durations interact with time zones
- Travel Budget Planning Guide — plan international trips with currency and time zone context
- Jet Lag Recovery Guide — science-backed strategies for resetting your circadian rhythm
Frequently Asked Questions
What is UTC and why is it used as the global standard?
UTC (Coordinated Universal Time) is the primary global time standard, maintained by the International Bureau of Weights and Measures using 400+ atomic clocks worldwide. It replaced GMT in 1972 and never observes Daylight Saving Time, making it the reliable anchor for all international time conversions and software timestamps.
How do I convert between two time zones?
Convert in two steps: first add or subtract your local UTC offset to get UTC time, then apply the target city's UTC offset. Example: 3:00 PM New York (UTC−5) = 8:00 PM UTC. London in winter is UTC+0, so it's 8:00 PM there. Sydney (UTC+11 during DST) would be 7:00 AM the next day.
Which countries do not observe Daylight Saving Time?
Most of the world does not observe DST. China, Japan, India, most of Africa, and most of Asia keep a fixed UTC offset year-round. The US, Canada, most of Europe, Australia, New Zealand, and parts of South America do shift clocks. About 40% of countries worldwide observe DST, per the IANA time zone database (2024).
When does the US change its clocks in 2026?
In 2026, US clocks spring forward one hour on Sunday, March 8 at 2:00 AM (second Sunday of March) and fall back one hour on Sunday, November 1 at 2:00 AM (first Sunday of November). Hawaii and most of Arizona do not observe DST and stay on fixed offsets year-round.
What is the best time to schedule a meeting between the US and Europe?
The sweet spot for US East Coast and Western Europe is 9:00 AM to 11:00 AM ET (2:00 PM to 4:00 PM London/Paris). For US West Coast and Europe, the window shrinks to 8:00 AM to 9:00 AM PT. Buffer's 2023 State of Remote Work found scheduling across time zones is the top challenge for 32% of remote teams.
What is ISO 8601 and why should I use it for scheduling?
ISO 8601 is the international date-time format: YYYY-MM-DDTHH:MM:SSZ (e.g., 2026-06-15T14:30:00Z). The Z denotes UTC. Using ISO 8601 eliminates ambiguity from regional formats like 06/15/26 vs 15/06/26, prevents scheduling errors across international teams, and is the standard used in all major calendar and API systems.