What Is a Time Zone?
A time zone is a region of the Earth that observes a uniform standard time. The planet is divided into zones so that local clock time roughly corresponds to the position of the sun — noon occurs when the sun is near its highest point in the sky.
There are 38 distinct UTC offsets in use today, ranging from UTC−12 to UTC+14. Most follow whole-hour offsets from UTC, but several use half-hour or 45-minute offsets.
Time Zone Converter
Select two cities, enter a time, and see the converted result instantly — with automatic Daylight Saving Time handling.
Convert NowWhat Is UTC?
UTC (Coordinated Universal Time) is the primary time standard used worldwide. Every time zone is defined as a fixed offset from UTC.
- UTC is maintained by a network of atomic clocks around the world, making it extremely precise.
- UTC does not observe Daylight Saving Time. It is always the same, regardless of season.
- UTC replaced GMT as the international civil time standard in 1960.
When you see a time written as 14:30 UTC, that is an unambiguous moment in time that anyone on the planet can convert to their local clock.
How UTC Offsets Work
A UTC offset tells you how many hours (and sometimes minutes) a time zone differs from UTC.
- UTC+0 — same as UTC (London in winter, Reykjavik year-round)
- UTC+1 — 1 hour ahead of UTC (Berlin, Paris, Rome in winter)
- UTC−5 — 5 hours behind UTC (New York in winter)
- UTC+5:30 — 5 hours and 30 minutes ahead (India, year-round)
- UTC+9 — 9 hours ahead (Tokyo, year-round)
To convert from one zone to another, calculate the difference between their offsets.
Example: Convert 3:00 PM New York time (UTC−5) to Tokyo time (UTC+9).
- Offset difference: +9 − (−5) = 14 hours
- 3:00 PM + 14 hours = 5:00 AM the next day in Tokyo
UTC vs. GMT — What Is the Difference?
GMT (Greenwich Mean Time) and UTC are functionally identical for everyday use — both represent the time at the UTC+0 offset. The differences are technical:
| UTC | GMT | |
|---|---|---|
| Basis | Atomic clocks (International Atomic Time) | Solar observations at Greenwich, England |
| Precision | Atomic-level accuracy | Based on Earth's rotation (which varies) |
| DST | Never changes | Never changes (but UK uses BST in summer) |
| Usage | International standard for computing, aviation, science | Commonly used in casual UK/European context |
In practice: When someone says "GMT" they almost always mean UTC+0. Use UTC for precision; GMT is fine in conversation.
Major Time Zones and Their UTC Offsets
Here are the most commonly referenced time zones, listed from west to east:
| Abbreviation | Full Name | UTC Offset | Major Cities |
|---|---|---|---|
| HST | Hawaii Standard Time | UTC−10 | Honolulu |
| AKST / AKDT | Alaska Standard / Daylight | UTC−9 / UTC−8 | Anchorage |
| PST / PDT | Pacific Standard / Daylight | UTC−8 / UTC−7 | Los Angeles, Seattle, Vancouver |
| MST / MDT | Mountain Standard / Daylight | UTC−7 / UTC−6 | Denver, Phoenix (no DST) |
| CST / CDT | Central Standard / Daylight | UTC−6 / UTC−5 | Chicago, Dallas, Mexico City |
| EST / EDT | Eastern Standard / Daylight | UTC−5 / UTC−4 | New York, Toronto, Miami |
| AST | Atlantic Standard Time | UTC−4 | Halifax, San Juan |
| BRT | Brasília Time | UTC−3 | São Paulo, Rio de Janeiro |
| GMT | Greenwich Mean Time | UTC+0 | London (winter), Reykjavik |
| BST | British Summer Time | UTC+1 | London (summer) |
| CET / CEST | Central European Time / Summer | UTC+1 / UTC+2 | Berlin, Paris, Rome, Madrid |
| EET / EEST | Eastern European Time / Summer | UTC+2 / UTC+3 | Athens, Helsinki, Bucharest |
| MSK | Moscow Standard Time | UTC+3 | Moscow, St. Petersburg |
| GST | Gulf Standard Time | UTC+4 | Dubai, Abu Dhabi |
| IST | India Standard Time | UTC+5:30 | Mumbai, Delhi, Bangalore |
| ICT | Indochina Time | UTC+7 | Bangkok, Ho Chi Minh City |
| CST (Asia) | China Standard Time | UTC+8 | Beijing, Shanghai, Taipei |
| SGT | Singapore Time | UTC+8 | Singapore |
| HKT | Hong Kong Time | UTC+8 | Hong Kong |
| KST | Korea Standard Time | UTC+9 | Seoul |
| JST | Japan Standard Time | UTC+9 | Tokyo, Osaka |
| AEST / AEDT | Australian Eastern Standard / Daylight | UTC+10 / UTC+11 | Sydney, Melbourne |
| NZST / NZDT | New Zealand Standard / Daylight | UTC+12 / UTC+13 | Auckland, Wellington |
Note: Abbreviations like "CST" are ambiguous — it can mean US Central Standard Time (UTC−6) or China Standard Time (UTC+8). When precision matters, use the IANA timezone name (e.g., America/Chicago or Asia/Shanghai) or the explicit UTC offset.
Daylight Saving Time (DST) Explained
Daylight Saving Time shifts clocks forward by 1 hour in spring ("spring forward") and back by 1 hour in fall ("fall back"). The purpose is to align daylight hours with typical waking hours during summer months.
How DST Changes UTC Offsets
When a region enters DST, its UTC offset increases by 1 hour:
- US Eastern: UTC−5 (EST) in winter → UTC−4 (EDT) in summer
- Central Europe: UTC+1 (CET) in winter → UTC+2 (CEST) in summer
- Australia Eastern: UTC+10 (AEST) in winter → UTC+11 (AEDT) in summer
This means the time difference between two cities can change depending on whether one, both, or neither is observing DST.
Example: New York to London
- Winter (both standard): New York UTC−5, London UTC+0 → 5-hour difference
- Summer (both daylight): New York UTC−4, London UTC+1 → 5-hour difference
- Spring transition weeks (US changes before UK): New York UTC−4, London UTC+0 → 4-hour difference
- Fall transition weeks (US changes before UK): Difference temporarily shifts to 4 hours
This 2–3 week transition period catches many people off guard when scheduling meetings.
When DST Transitions Happen
| Region | Spring Forward | Fall Back |
|---|---|---|
| United States & Canada | 2nd Sunday of March | 1st Sunday of November |
| European Union | Last Sunday of March | Last Sunday of October |
| Australia (participating states) | 1st Sunday of October | 1st Sunday of April |
Regions That Do Not Observe DST
Many places skip DST entirely, keeping the same offset year-round:
- Japan (JST, UTC+9)
- China (CST, UTC+8)
- India (IST, UTC+5:30)
- Singapore (SGT, UTC+8)
- Most of Africa
- Most of South America (Brazil stopped in 2019)
- Arizona, USA (except Navajo Nation)
- Hawaii, USA
- Iceland
For scheduling, regions without DST are simpler — their offset never changes.
Half-Hour and 45-Minute Time Zones
Not all time zones use whole-hour offsets. Several regions use fractional offsets to better align clock time with solar noon:
| Region | Offset | Why |
|---|---|---|
| India | UTC+5:30 | Entire country uses one zone; 5:30 splits the geographic difference |
| Nepal | UTC+5:45 | Chose an offset 15 minutes ahead of India for national identity |
| Iran | UTC+3:30 | Geographic position between UTC+3 and UTC+4 |
| Afghanistan | UTC+4:30 | Between Iran (UTC+3:30) and Pakistan (UTC+5) |
| Myanmar | UTC+6:30 | Between Bangladesh (UTC+6) and Thailand (UTC+7) |
| Marquesas Islands | UTC−9:30 | Remote Pacific location |
| Chatham Islands (NZ) | UTC+12:45 | 45 minutes ahead of mainland New Zealand |
| South Australia | UTC+9:30 / +10:30 | Between Western Australia (UTC+8) and Eastern Australia (UTC+10) |
| Northern Territory (AU) | UTC+9:30 | Same base offset as South Australia, but no DST |
When converting to or from these zones, remember to account for the extra 30 or 45 minutes — rounding to the nearest hour will give the wrong time.
How to Convert Time Between Zones
Method 1: UTC Offset Math
- Find the UTC offset for each zone on the specific date
- Subtract the source offset from the target offset
- Add the result to the source time
Example: 2:30 PM in Mumbai (UTC+5:30) → what time in Berlin (UTC+1)?
- Difference: +1 − (+5.5) = −4.5 hours
- 2:30 PM − 4 hours 30 minutes = 10:00 AM in Berlin
Method 2: Convert Through UTC
- Convert the source time to UTC by subtracting its offset
- Convert UTC to the target time by adding the target offset
Example: 8:00 PM in Tokyo (UTC+9) → what time in São Paulo (UTC−3)?
- Tokyo to UTC: 8:00 PM − 9 hours = 11:00 AM UTC
- UTC to São Paulo: 11:00 AM − 3 hours = 8:00 AM in São Paulo
Method 3: Use a Converter Tool
Manual math works, but it's error-prone — especially across DST transitions, half-hour offsets, and date boundaries. A time zone converter handles all of this automatically by using the IANA timezone database, which contains every historical and current offset rule.
The International Date Line
The International Date Line (IDL) runs roughly along the 180° meridian in the Pacific Ocean. It separates consecutive calendar days:
- Crossing westward → add 1 day
- Crossing eastward → subtract 1 day
This creates some surprising situations:
- Samoa (UTC+13) and American Samoa (UTC−11) are about 100 km apart but 24 hours apart on the calendar.
- Kiribati's Line Islands use UTC+14, the most extreme positive offset — when it is noon Monday in London, it is already 2:00 AM Tuesday in Kiritimati.
- Baker Island (UTC−12) is the last place on Earth where any given day exists.
For practical purposes, the date line matters when scheduling across the Pacific. A meeting set for "Tuesday" in Tokyo may fall on "Monday" in Honolulu.
Countries with Unusual Time Zone Rules
China: One Zone for a Huge Country
Despite spanning approximately 5 geographic time zones, all of China uses UTC+8 (Beijing Time). This means sunrise in western Xinjiang can be as late as 10:00 AM local clock time. Unofficial local time is sometimes used in daily life in western regions.
India: One Zone with a Half-Hour Offset
India uses a single time zone (UTC+5:30) across its entire width, roughly 2,000 km. This was a deliberate choice for national unity. Proposals to split India into two zones have been debated but not adopted.
Russia: 11 Time Zones
Russia spans from UTC+2 (Kaliningrad) to UTC+12 (Kamchatka), covering 11 contiguous time zones — more than any other country. Russia does not observe DST as of 2014.
Australia: Multiple Zones Including Half-Hours
Australia uses three main zones: Western (UTC+8), Central (UTC+9:30), and Eastern (UTC+10). Some states observe DST and others don't, creating five effective time zones during summer.
Common Mistakes When Working with Time Zones
-
Using abbreviations instead of IANA names. "CST" is ambiguous (US Central or China Standard). Use
America/ChicagoorAsia/Shanghaito be precise. -
Assuming a fixed offset year-round. EST is always UTC−5, but New York is not always in EST — it switches to EDT (UTC−4) in summer. The city's offset changes; the abbreviation changes with it.
-
Forgetting that DST transitions happen on different dates. The US and EU switch clocks on different weekends. For 2–3 weeks each spring and fall, the time difference between US and European cities temporarily shifts by 1 hour.
-
Ignoring half-hour offsets. Saying India is "5 hours ahead of London" is wrong — it's 5 hours and 30 minutes.
-
Not checking for date changes. A 14-hour offset means afternoon in one city is early morning the next day in another. Always verify whether the date changes.
-
Storing local times without timezone context. "3:00 PM on March 15" is meaningless without a timezone. Store timestamps in UTC or with an explicit offset (ISO 8601 format:
2026-03-15T15:00:00-05:00). -
Converting "from EST" when you mean "from Eastern Time." If it's summer, Eastern Time is EDT (UTC−4), not EST (UTC−5). The 1-hour error matters.
FAQ
What does UTC stand for?
UTC stands for Coordinated Universal Time (from the French "Temps Universel Coordonné"). The abbreviation UTC was chosen as a language-neutral compromise between the English "CUT" and French "TUC."
Is UTC the same as GMT?
For practical purposes, yes — both represent the time at the 0° meridian with no seasonal offset. Technically, UTC is based on atomic clocks and is the international standard for timekeeping, while GMT was historically based on solar observations. Use UTC for precision; GMT is acceptable in casual contexts.
Why do time zones exist?
Before time zones, each city set its clocks based on local solar noon, creating thousands of slightly different local times. This became unworkable when railways and telegraphs connected distant cities. In 1884, the International Meridian Conference established a system of standard time zones based on offsets from the Prime Meridian at Greenwich.
How many time zones are there?
There are 38 distinct UTC offsets in use today, ranging from UTC−12 to UTC+14. The number of named time zones is higher because different regions may share the same offset but use different abbreviations and DST rules.
What is the difference between EST and EDT?
EST (Eastern Standard Time) is UTC−5 and applies during winter. EDT (Eastern Daylight Time) is UTC−4 and applies during summer when Daylight Saving Time is in effect. The term "Eastern Time" (ET) covers both — it refers to whichever offset is currently active.
Why do some time zones use half-hour offsets?
Countries chose offsets that best align their clock time with local solar noon. India, for instance, would be too far east for UTC+5 and too far west for UTC+6, so UTC+5:30 was selected as a compromise. Nepal chose UTC+5:45 partly for geographic reasons and partly to distinguish itself from India.
What is the earliest time zone?
UTC+14 (Line Islands, Kiribati) is the furthest ahead. When it is midnight Monday in London (UTC), it is already 2:00 PM Monday in the Line Islands.
What is the latest time zone?
UTC−12 (Baker Island, Howland Island) is the furthest behind. These uninhabited US territories are the last places where any given calendar date exists.
Do all countries observe Daylight Saving Time?
No. Only about 70 countries observe DST. Most of Africa, Asia, and South America do not. Even within countries that observe DST, some regions opt out — Arizona (US), parts of Australia, and parts of Canada, for example.
How do computers handle time zones?
Most computer systems store time internally as UTC (often as a Unix timestamp — seconds since January 1, 1970 UTC). When displaying time to users, the system converts UTC to the user's local time zone using the IANA timezone database (also called the tz database or Olson database), which contains rules for every time zone's offsets and DST transitions, both current and historical.
What is the IANA timezone database?
The IANA timezone database is a comprehensive, regularly updated record of the world's time zones. It uses location-based names like America/New_York, Europe/London, and Asia/Tokyo. It is the authoritative source used by Linux, macOS, most programming languages, and the browser's Intl API. It is maintained by volunteers and published by IANA (Internet Assigned Numbers Authority).
How do I store times correctly in a database?
Store timestamps in UTC, and convert to local time only when displaying to users. Use ISO 8601 format with timezone information: 2026-03-15T15:00:00Z (UTC) or 2026-03-15T15:00:00-05:00 (with offset). Never store local times without timezone context — they become ambiguous during DST transitions.
Related Tools
- Time Zone Converter — Convert time between any two cities with automatic DST handling
- Time Zone Overlap Finder — Find overlapping working hours for international teams
- Unix Timestamp Converter — Convert between Unix timestamps and human-readable dates
- Date Difference Calculator — Calculate the number of days between two dates