Time Zones Explained: UTC, GMT, EST, and How to Convert Them

Published on June 3, 2026 · 10 min read

You book a Zoom call with a client in New York, a team stand-up with developers in London, and a deployment window with engineers in Sydney — all on the same day. Each calendar invite lists a different time zone abbreviation, and you suddenly realise you have no idea whether 3 PM EST is before or after 6 PM GMT. Time zones are one of those everyday topics that most people misunderstand until a missed meeting forces them to learn. This guide demystifies UTC, GMT, EST, and the rest, explains daylight saving time, and shows you how to convert between zones without breaking a sweat.

Where time zones come from

The Earth rotates 360 degrees in roughly 24 hours, which means 15 degrees of longitude equals one hour. In theory, every 15-degree strip of longitude should have its own time. In practice, political and economic borders bend those strips into jagged shapes. China, for example, uses a single time zone (UTC+8) for the entire country even though it spans five theoretical zones. Russia has eleven. The result is a world map that looks like a jigsaw puzzle designed by a committee.

UTC: the master reference

Coordinated Universal Time (UTC) is the global standard against which all other time zones are measured. It replaced Greenwich Mean Time (GMT) as the scientific reference in 1972, though GMT is still used interchangeably in everyday speech. UTC does not observe daylight saving; it is the same all year. Think of it as the "zero" on a number line — every other zone is expressed as UTC plus or minus some number of hours.

GMT vs UTC: what is the difference?

For everyday use, nothing. GMT is the older name based on the mean solar time at the Royal Observatory in Greenwich, London. UTC is the modern atomic- clock-based standard. They differ by less than a second and are only distinguishable to scientists measuring leap seconds. If someone says "GMT+2" they mean the same thing as "UTC+2."

Common time zones and their UTC offsets

Daylight saving time (DST): the seasonal shuffle

Daylight saving time moves clocks forward by one hour in spring and back by one hour in autumn. The goal is to extend evening daylight during the warmer months. Not every country uses it, and those that do rarely switch on the same date. This is the single biggest source of time-zone confusion.

• United States and Canada: DST starts the second Sunday in March and ends the first Sunday in November. During DST, EST becomes EDT (UTC−4), CST becomes CDT (UTC−5), and so on.
• European Union: DST starts the last Sunday in March and ends the last Sunday in October. CET becomes CEST (UTC+2), EET becomes EEST (UTC+3).
• No DST: Most of Asia, Africa, and parts of Australia do not observe DST at all. Japan, China, and India keep the same time year-round.

A meeting scheduled for "3 PM EST" in July is actually 3 PM EDT, which is UTC−4, not UTC−5. If you convert using the standard offset, you will be off by a full hour.

How to convert time zones step by step

Step 1: Convert everything to UTC

This is the safest method. Take the local time, subtract the zone's offset, and you have UTC. Then add the destination zone's offset.

Step 2: Check for DST

Is the source or destination zone currently in daylight saving time? If yes, use the "summer" offset (EDT, CEST, etc.).

Step 3: Add or subtract the difference

If it is 9 AM UTC, and you need JST (UTC+9), the answer is 6 PM the same day. If you need PST (UTC−8), the answer is 1 AM the same day.

Worked example: scheduling a global call

You are in Berlin (CEST, UTC+2) and want to schedule a call with colleagues in New York (EDT, UTC−4) and Sydney (AEST, UTC+10). You want the meeting at 2 PM your time.

• Berlin 2 PM CEST = 12 PM UTC (subtract 2).
• New York: 12 PM UTC − 4 hours = 8 AM EDT.
• Sydney: 12 PM UTC + 10 hours = 10 PM AEST.

The Sydney colleague may not appreciate a 10 PM call. You could try Berlin 8 AM (UTC 6 AM) → New York 2 AM (rejected) → Berlin 5 PM (UTC 3 PM) → New York 11 AM, Sydney 1 AM next day. No perfect slot exists for three continents. This is why asynchronous tools exist.

Flight times: why arrival can look earlier than departure

A flight departs Los Angeles at 11 PM PST and arrives in Sydney at 6 AM AEST two calendar days later. The elapsed flying time is about 15 hours, but because you cross the International Date Line going west-to-east, you "lose" a day. In the opposite direction, a flight from Tokyo to Los Angeles can arrive "earlier" than it departed because you gain time crossing the Pacific east-to-west. Always check the elapsed time, not just the clock times.

The International Date Line

Running roughly along 180° longitude, the International Date Line is where the calendar changes. Cross it going west (Asia to America) and you add a day. Cross it going east and you subtract a day. The line zigzags to avoid splitting countries and island groups, which is why Samoa and American Samoa — neighbours — are on different calendar days.

Time zone tools that actually work

• World Time Buddy: The cleanest visual grid for comparing multiple cities.
• Every Time Zone: A simple slider that shows times across zones.
• Google Calendar: Automatically converts invite times to each attendee's local zone if their timezone is set in their profile.
• ConvertProf time converter: For quick hour-to-minute calculations, use the time converter to handle offsets expressed in minutes or fractions.

Common pitfalls

• Abbreviation collisions: "CST" can mean Central Standard Time (UTC−6), Cuba Standard Time (UTC−5), or China Standard Time (UTC+8). Always verify the location.
• Date line confusion: A Monday 9 AM call in Auckland is Sunday 3 PM in San Francisco. The date matters as much as the time.
• Stating time without a zone: "The meeting is at 3 PM" is ambiguous. "The meeting is at 3 PM CEST" is not.
• Forgetting hemisphere seasons: When it is summer in the northern hemisphere, it is winter in the southern hemisphere. Sydney observes DST during December–February while New York does not.

Bottom line

Time zones are not complicated once you accept one rule: convert everything to UTC first. UTC is the universal language of time. Learn the standard offsets of the zones you work with most often, keep daylight saving dates bookmarked, and never schedule a "3 PM" meeting without naming the zone. Your colleagues — and your sleep schedule — will thank you.