What UTC offsets should I use?

Common US offsets: EST -5 (NYC), CST -6 (Chicago), MST -7 (Denver), PST -8 (LA), AKST -9 (Alaska), HST -10 (Hawaii). During Daylight Saving (March-November), add 1: EDT -4, CDT -5, MDT -6, PDT -7. International common: GMT/UTC 0 (London standard), CET +1 (Paris/Berlin), JST +9 (Tokyo), AEST +10 (Sydney), IST +5:30 (India — note half-hour), NZST +12 (New Zealand). For DST-affected zones, verify current actual offset for the specific date.

UTC (Coordinated Universal Time) and GMT (Greenwich Mean Time) are essentially identical for most practical purposes. Technical distinction: UTC is the modern atomic-clock-based standard; GMT historically based on Earth's rotation. For everyday timezone conversion, treat as same. UTC is more commonly used in modern technology and aviation; GMT is legal time in UK during winter (BST UTC+1 during summer). Most international standards use UTC reference. "UTC-5" and "GMT-5" mean the same thing for scheduling purposes.

How do I handle Daylight Saving Time?

This calculator uses static UTC offsets — doesn't auto-adjust for DST. Workarounds: (1) For US DST (mid-March to early November), use -4 EDT instead of -5 EST, etc. (2) For EU DST (late March to late October), use +2 CEST instead of +1 CET, etc. (3) Verify if your specific date falls in DST window for source and target locations. (4) For programming/calendar tools, use IANA timezone names (America/New_York, Europe/London) which auto-handle DST. Some countries don't observe DST — Arizona, Hawaii, most equatorial nations — these stay constant year-round.

Why doesn't my city follow strict longitude time?

Many factors: political decisions (China uses one time zone despite spanning 5 hours of geographic time), economic reasons (alignment with trading partners), historical compromise (UTC+5:30 for India), or geographic accommodation (Spain uses CET +1 despite being mostly west of Greenwich). The "natural" longitude-based timezone is approximation only; actual timezone boundaries follow political/administrative borders. Some places have offsets you wouldn't expect from looking at a globe.

How do I schedule across many time zones?

Best practices: (1) Use timezone visualization tools (worldtimebuddy.com) showing all participants' working hours. (2) Aim for time block in working hours for ALL participants (often 7-8 AM in westernmost zone aligns with 6-7 PM in easternmost). (3) For East-West teams (US-Asia): rotate inconvenience, sometimes early morning, sometimes evening for each team. (4) Use UTC notation in invitations: "10:00 UTC" eliminates ambiguity. (5) Consider asynchronous alternatives — Slack, video messages, async docs — for teams with very large time differences. Synchronous meetings often impractical for trans-Pacific teams.

Time Zone Converter

Convert a time from one time zone to another by specifying UTC offset hours. Enter the source time and both offsets to instantly see the converted result.

Last updated: July 28, 2026

About this calculator

Time zones convert universal time (UTC) to local times based on geographic offset. Earth has 24 main time zones (one per hour of rotation), but practical timezone count is higher due to half-hour and quarter-hour offsets (India UTC+5:30, Nepal UTC+5:45, Newfoundland UTC-3:30) and political/cultural boundaries that don't follow pure longitude. Daylight Saving Time further complicates: many countries shift clocks twice yearly, changing offsets seasonally.

International scheduling — business meetings, video calls, content distribution, travel — requires accurate timezone conversion. The challenge: "Let's meet at 2 PM" is ambiguous without timezone specification. "2 PM Pacific" or "2 PM Tokyo" or "2 PM UTC" clarifies. International meetings sometimes use UTC (no DST shifts, single global reference) or specify both endpoints. Modern tools (Google Calendar, Outlook, Zoom) auto-convert if configured correctly, but understanding underlying math helps prevent costly scheduling errors.

This calculator converts a time from one UTC offset to another. Use it for: international meeting scheduling, calculating time differences between locations, planning international travel, content publishing across timezones, or learning timezone mechanics. Important context: this calculator uses simple UTC offset arithmetic. It doesn't automatically handle DST (which shifts offsets seasonally) or named time zone references (which have political complexity). For practical scheduling, dedicated tools (worldtimebuddy.com, Google Calendar) automatically handle DST and provide visual timezone alignment. For programmatic use, libraries like Moment.js or modern date libraries handle full timezone complexity.

Formula

Time zone conversion: Convert source time to UTC, then to target: UTC Time = Source Time − Source UTC Offset Target Time = UTC Time + Target UTC Offset Or directly: Target Time = Source Time + (Target Offset − Source Offset) Example: 12:00 noon EST (UTC-5) to UTC (UTC+0). Source offset: −5 Target offset: 0 Difference: 0 − (−5) = +5 hours 12:00 + 5 hours = 17:00 (5 PM UTC) Example: 9:00 AM Tokyo (UTC+9) to New York EST (UTC-5). Difference: −5 − 9 = −14 hours 9:00 AM − 14 hours = 19:00 (7 PM) previous day in New York Same time, different perspectives: 9:00 AM Tokyo today = 7:00 PM New York yesterday Common UTC offsets: UTC-12: Baker Island (uninhabited) UTC-11: American Samoa UTC-10: Hawaii UTC-9: Alaska UTC-8: Pacific (LA, Seattle) — PST (DST: PDT UTC-7) UTC-7: Mountain (Denver) — MST (DST: MDT UTC-6) / Arizona stays UTC-7 UTC-6: Central (Chicago) — CST (DST: CDT UTC-5) UTC-5: Eastern (NYC) — EST (DST: EDT UTC-4) UTC-4: Atlantic Canada — AST UTC-3: Argentina, Brazil (no DST in most areas) UTC-2: Mid-Atlantic UTC-1: Azores UTC+0: London — GMT (DST: BST UTC+1) UTC+1: Berlin, Paris — CET (DST: CEST UTC+2) UTC+2: Cairo, Athens — EET (DST: EEST UTC+3) UTC+3: Moscow, Saudi Arabia UTC+3:30: Iran (DST: UTC+4:30 in summer) UTC+4: Dubai UTC+4:30: Afghanistan UTC+5: Pakistan UTC+5:30: India, Sri Lanka UTC+5:45: Nepal UTC+6: Bangladesh UTC+6:30: Myanmar UTC+7: Bangkok, Jakarta, Vietnam UTC+8: Beijing, Singapore, Hong Kong, Perth UTC+9: Tokyo, Seoul UTC+9:30: Adelaide UTC+10: Sydney, Melbourne (DST: UTC+11) UTC+10:30: Lord Howe Island UTC+11: New Caledonia UTC+12: New Zealand (DST: UTC+13) UTC+12:45: Chatham Islands UTC+13: Tonga UTC+14: Kiribati Daylight Saving Time complications: Many countries shift clocks twice yearly: US (most states): Spring forward second Sunday March; Fall back first Sunday November EU: Last Sunday March (forward); Last Sunday October (back) Australia: First Sunday October (forward); First Sunday April (back) — only some states Many tropical countries: no DST (Singapore, India, Hawaii) During DST shift periods, US and EU don't align — for ~2 weeks each year, the normal 5-hour difference between NYC and London becomes 4 hours (when US has shifted but EU hasn't, or vice versa). This calculator uses static UTC offsets. For DST-aware conversion, verify which timezone's DST is currently active. Date line considerations: International Date Line (approximately 180° longitude) separates calendar days. Crossing east-to-west: "lose" a day. West-to-east: "gain" a day. Trip from Tokyo (UTC+9) to Honolulu (UTC-10): 19-hour difference. Departing Sunday afternoon Tokyo could arrive Sunday morning Honolulu (same calendar day despite long flight). Trip from Honolulu to Tokyo: arrive ~2 calendar days later despite ~10 hour flight. For international travel timing, both clock time and date matter. Time zone abbreviations (commonly used but ambiguous): CST: Central Standard Time (US, UTC-6) OR China Standard Time (UTC+8) — ambiguous! PST: Pacific Standard Time (US) OR Philippine Standard Time IST: Indian Standard Time (UTC+5:30) OR Israel Standard Time (UTC+2) OR Irish Standard Time EST: Eastern Standard Time (US) OR Eastern European Summer Time To avoid ambiguity, use: - UTC offset notation (UTC-5, UTC+9) - IANA timezone names (America/New_York, Europe/London) - Full timezone names with country/region context Modern scheduling best practices: 1. Use UTC for any system involving multiple timezones 2. Display in user's local timezone 3. Use IANA timezone names internally 4. Account for DST transitions 5. For meetings spanning timezones: pick reasonable hour ranges in all participating timezones (9-5 local in each) 6. Use tools that visualize timezone alignment (worldtimebuddy, when-x-where) Calculating timezone differences: Difference = Target Offset − Source Offset Positive: target is later (east) Negative: target is earlier (west) Example: NYC (UTC-5) to London (UTC+0): Difference = 0 − (−5) = +5 London is 5 hours later than NYC. Example: NYC (UTC-5) to LA (UTC-8): Difference = −8 − (−5) = −3 LA is 3 hours earlier than NYC.

How to use this calculator

Enter the source time (hour 0-23, minute 0-59).
Enter the source UTC offset (e.g., -5 for EST, -8 for PST, 0 for UTC, 9 for Japan).
Enter the target UTC offset.
Review the converted time.
For US standard time: use offset matching your zone (EST -5, CST -6, MST -7, PST -8).
For US daylight time (March-November typically): subtract 1 from standard offset (EDT -4, CDT -5, MDT -6, PDT -7).
For international meetings: convert your local time to participants' local times. Aim for reasonable hours (9 AM - 6 PM local) for all.
For DST awareness: this calculator uses simple offset math. For DST-active periods, verify current actual offset (check timeanddate.com or similar).
For India (UTC+5:30) and Nepal (UTC+5:45): note the half-hour and quarter-hour offsets.
For arctic/antarctic research stations: verify local timezone — often chosen for convenience, not strict longitude.
For cruise ship / mid-ocean: ships typically use the timezone of their next port. Doesn't follow strict longitude.
For digital nomads / international workers: use IANA timezone names in software (America/Los_Angeles, Asia/Tokyo) for DST accuracy.

Worked examples

Coast-to-coast meeting

Schedule 10 AM Pacific meeting. Find equivalent in other US zones. Source: 10:00 AM PST (UTC-8) Convert to other US time zones: MST (UTC-7): 10:00 + (-7 − (-8)) = 10:00 + 1 = 11:00 AM CST (UTC-6): 10:00 + 2 = 12:00 PM (noon) EST (UTC-5): 10:00 + 3 = 1:00 PM Same meeting from different perspectives: Seattle/LA: 10:00 AM PST Denver/Phoenix*: 11:00 AM MST (* if not in DST, AZ stays static) Chicago: 12:00 PM CST New York: 1:00 PM EST Reasonable for everyone — within standard working hours. Good US-internal meeting time. During DST: all US zones shift forward 1 hour, but relative differences stay same. 10 AM Pacific in summer = 1 PM Eastern in summer.

International business call

San Francisco team wants call with Tokyo team. What time works? San Francisco PST (UTC-8) vs. Tokyo (UTC+9): 17-hour difference. Option 1: 5 PM SF Friday = 10 AM Tokyo Saturday Tokyo: Saturday morning (weekend — typically not preferred) SF: end of workday — acceptable Option 2: 8 AM SF Monday = 1 AM Tokyo Tuesday Tokyo: middle of night (unworkable) SF: start of workday — acceptable Option 3: 5 PM SF Thursday = 10 AM Tokyo Friday Tokyo: Friday morning (good — fresh) SF: late afternoon Thursday (manageable) Best option: Thursday afternoon SF / Friday morning Tokyo. Or alternate: rotate "burden" — one week SF early morning, next week SF late evening, to share the inconvenience. For ongoing collaboration: shifted work hours by one team often necessary. Or asynchronous workflow (Slack, email-based) instead of synchronous meetings.

Date line crossing

Flight from Tokyo Saturday 6 PM departure to Honolulu. Tokyo (UTC+9): Saturday 18:00 departure Flight duration: 7 hours Tokyo time at arrival: Saturday 25:00 (Sunday 1:00 AM Tokyo) Convert to Honolulu (UTC-10): Difference: −10 − 9 = −19 hours Sunday 1:00 AM Tokyo − 19 hours = Saturday 6:00 AM Honolulu (same calendar day, earlier in day) So: depart Tokyo Saturday evening, arrive Honolulu Saturday morning — same calendar day despite 7-hour flight, due to crossing International Date Line going east. Reverse direction (Honolulu to Tokyo) "loses" a day: Honolulu Sunday 9 AM departure + 8 hour flight = Honolulu 5 PM Sunday Convert to Tokyo: Sunday 5 PM HI + 19 hours = Monday noon Tokyo This is why westbound trans-Pacific flights often feel like losing a day, while eastbound feel like extra day.

When to use this calculator

Use this calculator for international meeting scheduling, planning calls with overseas teams or family, content scheduling across timezones, travel planning, or understanding timezone mechanics.

Pair with time-calculator (duration arithmetic) and date-calculator (calendar date operations).

Important timezone considerations:

1. **Use UTC for system internals.** Avoid timezone confusion by using UTC for any database, scheduling, or logging. Convert to local time only for display.

2. **DST shifts offsets seasonally.** Most countries shift clocks twice yearly. Static calculator doesn't handle this automatically — verify if current period is DST.

3. **DST timing differs by region.** US shifts 2nd Sunday March (forward) and 1st Sunday November (back). EU shifts last Sunday March/October. For ~2 weeks each year, these are misaligned.

4. **Some countries don't observe DST.** Hawaii, Arizona, most of Indiana don't. Most equatorial countries don't. Verify recipient's actual timezone.

5. **Time zone abbreviations are ambiguous.** "CST" can mean Central Standard Time (US, UTC-6) OR China Standard Time (UTC+8). Use UTC offset notation or IANA names for clarity.

6. **India (UTC+5:30) and Nepal (UTC+5:45) are unusual.** Half-hour and quarter-hour offsets exist. Don't assume timezones are whole-hour offsets.

7. **International Date Line shifts dates.** Crossing east-to-west: subtract a day. West-to-east: add a day. Major impact on trans-Pacific scheduling.

8. **Use timezone visualization tools.** worldtimebuddy.com, when-x-where, and similar tools show overlapping work hours visually. Better than mental math for multi-timezone scheduling.

9. **For ongoing teams across timezones.** Consider asynchronous workflows (Slack, email, video messages) over synchronous meetings when time differences are large.

10. **For recurring international meetings.** Some teams use fixed UTC time to avoid DST confusion. Others rotate inconvenience across team members.

11. **Time zones aren't purely longitudinal.** Political/cultural choices shape boundaries. China uses one time zone (Beijing time) for the entire country despite spanning 5 geographic hours.

12. **Mobile devices auto-convert.** Most smartphones convert calendar events to local time automatically. Set calendar invitations in your timezone; recipients see in theirs.

Common mistakes to avoid

Forgetting DST shifts. Static offsets don't change with seasonal time shifts.
Using ambiguous timezone abbreviations (CST, IST, PST). UTC offsets or IANA names eliminate ambiguity.
Ignoring half-hour and quarter-hour offsets. India (UTC+5:30), Nepal (UTC+5:45) are exceptions.
Not accounting for date changes. Crossing International Date Line changes calendar date.
Scheduling assuming opposite-side-of-world meetings can work normally hours. Often requires significant time accommodation.
Manual conversion across multiple zones. Tools like worldtimebuddy easier and more accurate.

Frequently Asked Questions

Sources & further reading

Time Zone Database — Internet Assigned Numbers Authority (IANA)
World Clock Reference — timeanddate.com
International Date and Time Standards — International Organization for Standardization

Related Calculators

Time Calculator

Add or subtract hours, minutes, and seconds.

Date Calculator

Find days between two dates or add/subtract days from a date.

Electricity Cost Calculator

Calculate electricity cost from watts, hours of use, and rate per kWh.

Unit Price Calculator

Compare unit prices of different package sizes to find the best deal.

Discount Calculator

Calculate discount amount and final price after a percentage discount.

GPA Calculator

Calculate GPA from grades and credit hours.

About this calculator

Formula

How to use this calculator

Enter the source time (hour 0-23, minute 0-59).

Enter the source UTC offset (e.g., -5 for EST, -8 for PST, 0 for UTC, 9 for Japan).

Enter the target UTC offset.

Review the converted time.

For US standard time: use offset matching your zone (EST -5, CST -6, MST -7, PST -8).

For US daylight time (March-November typically): subtract 1 from standard offset (EDT -4, CDT -5, MDT -6, PDT -7).

For international meetings: convert your local time to participants' local times. Aim for reasonable hours (9 AM - 6 PM local) for all.

For DST awareness: this calculator uses simple offset math. For DST-active periods, verify current actual offset (check timeanddate.com or similar).

For India (UTC+5:30) and Nepal (UTC+5:45): note the half-hour and quarter-hour offsets.

For arctic/antarctic research stations: verify local timezone — often chosen for convenience, not strict longitude.

For cruise ship / mid-ocean: ships typically use the timezone of their next port. Doesn't follow strict longitude.

For digital nomads / international workers: use IANA timezone names in software (America/Los_Angeles, Asia/Tokyo) for DST accuracy.