Time Zones Explained: UTC, GMT, Offsets, and DST

Time zones seem straightforward until you schedule a meeting across three continents. The world doesn’t split into clean 24 slices. According to IANA (the authority behind the tz database), there are over 400 named time zones in active use, many with half-hour or quarter-hour offsets and wildly different daylight saving rules.

This guide covers how UTC, GMT, and offsets actually work. You’ll learn the real differences between UTC and GMT, why DST breaks scheduling twice a year, and how to handle edge cases like Nepal’s UTC+5:45 offset. Whether you’re coordinating remote teams or writing code that touches timestamps, this is the reference you’ll keep coming back to.

time and date tools

Convert Time Zones Instantly

Offset math gets tedious fast, especially when DST is involved. Use the converter below to check any timezone pair without the mental arithmetic.

What Is the Difference Between UTC and GMT?

UTC (Coordinated Universal Time) and GMT (Greenwich Mean Time) share the same offset, UTC+0, but they’re fundamentally different. According to the Bureau International des Poids et Mesures (BIPM), UTC is defined by a weighted average of over 450 atomic clocks worldwide, making it accurate to within nanoseconds.

GMT is a time zone. It originated at the Royal Observatory in Greenwich, London, and was the world’s reference standard from 1884 until UTC replaced it in 1972. GMT is based on the Earth’s rotation, which is irregular. The planet’s spin slows down over time due to tidal friction.

UTC doesn’t care about the Earth’s rotation. It’s a calculated time standard that occasionally adds a “leap second” to stay within 0.9 seconds of astronomical time. Since 1972, 27 leap seconds have been inserted (IERS, 2024). However, the General Conference on Weights and Measures voted in 2022 to abolish leap seconds by 2035 (Resolution 4, CGPM, 2022).

So why does this matter in practice? For everyday scheduling, UTC and GMT are interchangeable. For scientific computing, satellite navigation, or financial trading, the distinction is critical. GPS time, for example, diverged from UTC by 18 seconds as of 2024 because GPS doesn’t apply leap seconds.

Citation capsule: UTC is maintained by over 450 atomic clocks coordinated by BIPM, accurate to nanoseconds (BIPM). GMT is a time zone based on Earth’s rotation. They share UTC+0 but UTC is the global standard since 1972.

calculate date differences

How Do Time Zones Actually Work?

The world has 24 primary time zones, each offset from UTC by whole hours, but reality is messier. According to the CIA World Factbook, countries use 38 distinct UTC offsets including half-hour and quarter-hour variations. Political boundaries, not longitude lines, determine which offset a region uses.

The 15-degree theory

In theory, the Earth rotates 360 degrees in 24 hours, so each time zone should span 15 degrees of longitude. Sir Sandford Fleming proposed this system in 1879, and the International Meridian Conference adopted it in 1884. But governments immediately started bending the lines. China spans five geographic time zones but uses a single offset (UTC+8) nationwide. Spain sits in the same longitude as the UK but uses UTC+1, a legacy of Franco-era alignment with Nazi Germany that was never reversed.

Understanding offsets

An offset tells you how many hours (and sometimes minutes) to add or subtract from UTC. UTC-5 means five hours behind UTC. UTC+5:30 means five and a half hours ahead. Offsets are not fixed for a given location. They change when daylight saving time kicks in.

Citation capsule: The world uses 38 distinct UTC offsets, not the theoretical 24 (CIA World Factbook). Political decisions, not geography, determine a country’s time zone. China uses one offset for five geographic zones.

What Are the Most Common Time Zone Conversions?

Cross-timezone scheduling is a daily headache for remote teams. A Buffer State of Remote Work survey found that 40% of remote workers cite scheduling across time zones as their top collaboration challenge. Here are the conversion pairs people look up most.

The conversion that trips people up most isn’t the big offsets. It’s EST to GMT during the three weeks in March when the US has already sprung forward but the UK hasn’t. The gap shrinks from 5 hours to 4 hours, and every recurring meeting shifts by an hour with no warning. We’ve found that putting “(UTC)” after every scheduled time in calendar invites eliminates this confusion entirely.

set a countdown to your next meeting

How Does Daylight Saving Time Work?

Roughly 70 countries observe DST, affecting about 1.6 billion people (TimeAndDate.com, 2025). Clocks move forward one hour in spring (“spring forward”) and back one hour in autumn (“fall back”). The original rationale was energy savings, but a U.S. Department of Energy study found DST reduces electricity use by only about 0.03% nationally.

When do clocks change?

The dates vary by country, which is the core problem for international scheduling.

The edge cases that break software

DST creates a genuinely weird 2 AM. When clocks spring forward, 2:00 AM becomes 3:00 AM. The timestamp “2:30 AM” on that date doesn’t exist. When clocks fall back, 1:00 AM to 1:59 AM happens twice. The timestamp “1:30 AM” on that date is ambiguous. Here’s what most DST explanations miss: the transition gap means that any cron job, scheduled task, or database trigger set to run between 2:00 AM and 2:59 AM on spring-forward day will either skip entirely or fire at 3:00 AM, depending on the scheduler’s implementation. Scheduling daily jobs at 3 AM or later avoids this landmine.

Citation capsule: Around 70 countries observe daylight saving time, affecting 1.6 billion people (TimeAndDate.com, 2025). DST transitions create non-existent and ambiguous local times that break naive scheduling logic.

Which Countries Use Half-Hour and Quarter-Hour Offsets?

Not every offset is a whole number. According to the IANA tz database, nine active offsets include 30-minute or 45-minute components. These exist because countries chose offsets that better matched their geographic position between two whole-hour zones.

Nepal’s UTC+5:45 is the world’s only major quarter-hour offset in active use (alongside the Chatham Islands’ UTC+12:45). The choice was deliberate. When Nepal standardized time in 1986, the government set it 15 minutes ahead of India to assert national identity. It’s a political statement encoded in clocks. Newfoundland’s UTC-3:30 means that when New Yorkers hear “it’s 3 PM,” Newfoundlanders know it’s 4:30 PM. That half-hour gap is endlessly confusing for Canadians scheduling calls between provinces. Every Canadian developer who’s built a scheduling app has a Newfoundland story. Citation capsule: Nine active UTC offsets include 30-minute or 45-minute components (IANA tz database). Nepal uses UTC+5:45, the world’s only major quarter-hour offset, chosen deliberately to differentiate from India’s UTC+5:30.

What Happens at the International Date Line?

The International Date Line runs roughly along the 180th meridian in the Pacific Ocean, where the calendar date changes. Crossing it westward adds a day. Crossing eastward subtracts one. According to the National Oceanic and Atmospheric Administration (NOAA), the line isn’t straight. It zigzags to keep island nations on the same date as their trading partners.

The most dramatic zigzag happened in 2011. Samoa jumped from UTC-11 to UTC+13, skipping December 30 entirely. The country wanted to align with Australia and New Zealand, its main trading partners, rather than the Americas. Samoans went to bed on Thursday, December 29, and woke up on Saturday, December 31.

Kiribati pushed the line even further east in 1995, creating UTC+14, the world’s furthest-ahead offset. When it’s noon Monday in London, it’s 2 AM Tuesday on Kiribati’s Line Islands. This means Kiribati is always the first place to ring in the New Year.

Is the date line a formal legal boundary? No. It has no standing in international law. Each country unilaterally decides which side of the line it sits on. That’s why it zigzags so dramatically.

calculate time between any two dates

How Should Programmers Handle Time Zones?

Timezone handling is a top source of bugs in production software. A JetBrains Developer Ecosystem Survey from 2023 found that date/time logic ranks among the most error-prone areas across all programming languages. The fix starts with two tools: the IANA tz database and ISO 8601.

The IANA tz database

The IANA Time Zone Database (also called “tz” or “Olson database”) is the authoritative source for timezone rules. It’s maintained by volunteers and used by Linux, macOS, Java, PHP, Python, and virtually every modern platform. Zone names follow the format Area/City, like America/New_York or Asia/Kolkata.

Why city names instead of abbreviations? Because abbreviations are ambiguous. “CST” means Central Standard Time (UTC-6) in the US, China Standard Time (UTC+8) in China, and Cuba Standard Time (UTC-5) in Cuba. The IANA name is unambiguous.

ISO 8601 format

ISO 8601 is the international standard for date and time representation. A timestamp with timezone looks like:

2026-03-31T14:30:00-05:00

That’s March 31, 2026, at 2:30 PM, five hours behind UTC. The Z suffix means UTC: 2026-03-31T19:30:00Z. Always store timestamps in UTC (with Z) and convert to local time at display time.

Practical rules for developers

1. Store UTC, display local. Every timestamp in your database should be UTC. Convert to the user’s timezone only in the presentation layer.
2. Use IANA names, not abbreviations. Store America/New_York, not EST. The IANA name captures DST rules. The abbreviation doesn’t.
3. Never calculate offsets by hand. Use your language’s timezone library: pytz or zoneinfo in Python, Intl.DateTimeFormat in JavaScript, java.time.ZoneId in Java.
4. Test around DST transitions. Write unit tests for timestamps during spring-forward and fall-back transitions. This is where timezone bugs hide.
5. Don’t trust the client’s clock. Server-generated timestamps should come from NTP-synchronized clocks, not client-submitted values.

// JavaScript: convert UTC to local time
const utc = new Date('2026-03-31T19:30:00Z');
const local = utc.toLocaleString('en-US', {
  timeZone: 'America/New_York',
  dateStyle: 'full',
  timeStyle: 'short'
});
// "Tuesday, March 31, 2026 at 3:30 PM"

The most common timezone bug isn’t wrong offsets.

It’s comparing timestamps stored with different timezone awareness. Mixing “naive” timestamps (no timezone info) with “aware” timestamps (UTC-marked) in the same query produces silently wrong results. An ORM that strips timezone info on read is a time bomb. Always audit whether your database driver preserves timezone metadata. Citation capsule: The IANA tz database is the authoritative source for timezone rules, used by every major operating system and programming language (IANA). Always store timestamps in UTC and use IANA zone names like America/New_York instead of ambiguous abbreviations.

explore all time and date tools

What Are the Best Practices for Scheduling Across Time Zones?

Remote work has made cross-timezone scheduling a daily reality. Owl Labs’ State of Remote Work reports that 62% of workers aged 22-65 work remotely at least occasionally. Here are the practices that actually work for distributed teams.

Find the overlap window

For teams spanning US Eastern (UTC-5) and Central European (UTC+1), the overlap window is roughly 9 AM to 12 PM Eastern (3 PM to 6 PM CET). For US Pacific (UTC-8) to India (UTC+5:30), the overlap shrinks to about 7:30 AM to 9 AM Pacific (9 PM to 10:30 PM IST). That’s painfully narrow.

Use UTC as the lingua franca

When posting meeting times in Slack, email, or project management tools, always include the UTC time. “Standup at 15:00 UTC” is unambiguous. “Standup at 10 AM” requires everyone to know whose 10 AM you mean.

Account for DST transition weeks

The US and EU shift DST on different dates. For two to three weeks in March and one week in October/November, the offset between American and European time zones differs by one hour from the rest of the year. Block those weeks in your calendar as “check meeting times” reminders.

Rotate the pain

If only one timezone always takes the early-morning or late-night slot, resentment builds. Rotate meeting times quarterly so the inconvenience is shared. Async communication (recorded standups, written updates) can eliminate the need for synchronous overlap entirely.

Citation capsule: 62% of workers work remotely at least occasionally (Owl Labs, 2023). Best practices include posting all times in UTC, accounting for DST transition weeks, and rotating meeting times to share the inconvenience across timezones.

Frequently Asked Questions

Is UTC the same as GMT?

UTC and GMT share the same offset (UTC+0), but they’re defined differently. UTC is maintained by atomic clocks coordinated by BIPM, accurate to nanoseconds. GMT is a time zone based on Earth’s rotation at the Greenwich meridian. For everyday scheduling, they’re interchangeable. For scientific or financial applications, UTC is the correct standard. Since 1972, UTC has been the official global reference time (BIPM).

Why do some time zones have half-hour offsets?

Half-hour offsets exist because some countries sit geographically between two whole-hour zones and chose a compromise. India (UTC+5:30) is the largest example, serving 1.4 billion people. Iran (UTC+3:30), Afghanistan (UTC+4:30), Myanmar (UTC+6:30), and Newfoundland (UTC-3:30) also use half-hour offsets. Nepal goes further with UTC+5:45, the only major quarter-hour offset (IANA tz database).

How many countries still use daylight saving time?

Around 70 countries observe DST, affecting approximately 1.6 billion people (TimeAndDate.com, 2025). The trend is toward abolishing it. Russia dropped DST in 2014, Brazil in 2019, and the EU has debated ending it since 2019 (though no final legislation has passed). In the US, the Sunshine Protection Act to make DST permanent has been introduced multiple times but hasn’t become law.

What timezone format should I use in code?

Use IANA timezone names like America/New_York or Europe/London, never abbreviations like EST or GMT. Abbreviations are ambiguous: “CST” could mean UTC-6 (US), UTC+8 (China), or UTC-5 (Cuba). IANA names encode the full history of a zone’s offsets and DST rules. Store all timestamps in UTC (ISO 8601 format with Z suffix) and convert to local time only at display time.

What is the furthest-ahead time zone?

UTC+14, used by Kiribati’s Line Islands, is the furthest ahead of UTC. This means Kiribati is always the first place on Earth to reach a new calendar day. The offset exists because Kiribati moved the International Date Line in 1995 to keep all its islands on the same day. At the other extreme, Baker Island and Howland Island use UTC-12, creating a 26-hour spread across all active time zones.

try the full timezone converter

Wrapping Up

Time zones are a solved problem with an unsolved human layer on top. The technical infrastructure works: UTC provides a global anchor, the IANA database tracks every rule change, and ISO 8601 gives us an unambiguous format. The messy part is always people. DST transitions that shift on different dates across countries, half-hour offsets that break simple arithmetic, and political decisions that redraw the date line.

Three rules will save you from most timezone headaches. First, store everything in UTC and convert at display time. Second, use IANA zone names instead of abbreviations. Third, always include the UTC time when communicating across zones. These aren’t clever tricks. They’re the boring fundamentals that prevent bugs and missed meetings.

The world’s clocks aren’t going to get simpler. But your handling of them can be.