See the World's Time Zones at a Glance
The world is divided into 38 distinct UTC offsets — from UTC−12 in the far western Pacific to UTC+14 off the east coast of Kiribati. The difference between the earliest and latest point on Earth is a full 26 hours.
How the color gradient works
- Blue tones — zones west of UTC (UTC−12 to UTC−1)
- Cyan / green — UTC+0 (the Prime Meridian)
- Yellow → orange → red — zones east of UTC (UTC+1 to UTC+14)
Click any polygon to see a popup with the live local time, today's date, and the countries that observe that offset. The sidebar keeps a live clock for the selected zone plus a permanent UTC reference clock.
Watch: World Time Zone Map in Under a Minute
Prefer to watch instead of read? This short walkthrough covers exploring the interactive time zone map and reading each zone's UTC offset.
Common Use Cases
How the Tool Works
Three live data sources — nothing hardcoded
- Boundary polygons — fetched at runtime from a GeoJSON dataset (not bundled into the page), so the map reflects current international timezone data.
- Local time per zone — calculated by the browser's built-in Intl.DateTimeFormat API using IANA timezone rules embedded in your OS. DST adjustments are applied automatically.
- My Timezone / city search — calls the BigDataCloud free timezone API with your detected or geocoded coordinates, returning the IANA identifier (e.g. America/Chicago) for precise DST-aware time display.
Frequently Asked Questions
The International Date Line
Where it is and what it does
- Runs roughly along the 180° meridian in the Pacific, zigzagging around island groups and territories
- Crossing westward advances the calendar by one day; crossing eastward moves it back
- Kiribati's Line Islands (UTC+14) can be celebrating New Year's while the Aleutian Islands of Alaska — geographically close across the Pacific — are still on December 30th
Why the color contrast at the date line is intentional
The deep blue of UTC−12 and the deep red of UTC+14 sit directly next to each other at the western Pacific boundary — visually representing the full 26-hour range of time coexisting on Earth at any given moment.
Understanding UTC Offsets
How offsets work
Every timezone is a positive or negative offset from UTC. When it is 12:00 UTC:
- India (UTC+5:30) → 17:30
- Tokyo (UTC+9) → 21:00
- New York (UTC−5) → 07:00
- Los Angeles (UTC−8) → 04:00
Why some offsets aren't whole hours
- Nepal — UTC+5:45: the only country using a 15-minute offset, chosen to distinguish itself from India
- India — UTC+5:30: avoids splitting a vast landmass across two zones
- Newfoundland — UTC−3:30: dates to its period as an independent dominion before joining Canada in 1949
- Iran — UTC+3:30, Afghanistan — UTC+4:30: historical solar-time conventions
Offsets beyond UTC±12
- Kiribati adopted UTC+13 and UTC+14 in 1995 to keep its scattered islands on the same calendar date
- Samoa switched from UTC−11 to UTC+13 in 2011 to align with Australia and New Zealand for trade
Step-by-Step Guide










Daylight Saving Time (DST)
Key facts
- Observed by roughly 70 countries — mainly Europe, North America, parts of South America and Australia
- Clocks advance one hour in spring, fall back one hour in autumn
- Countries near the equator generally do not observe DST (day length barely changes year-round)
- Northern and Southern Hemisphere DST periods are opposite — when the US springs forward in March, Australia falls back in April
How this tool handles DST
- Map polygons: show fixed UTC offset labels from the boundary data (e.g. UTC−5 for Eastern US)
- My Timezone or city search: the live IANA lookup shows the actual current offset — so New York displays UTC−4 during summer DST, not UTC−5
- For scheduling: always check the live offset rather than the standard label — search each participant's city, read the sidebar, then subtract
Related Tools
Time zone boundaries: ArcGIS World Time Zones. Time zone lookup: BigDataCloud (free plan, no key needed). Address search: OpenStreetMap data through LocationIQ, OpenCage, Geoapify, Photon and Nominatim. Map tiles © OpenStreetMap contributors, drawn with Protomaps (hosted by KONAKTIVE), with CARTO as the fallback. Local time is calculated by your browser with Intl.DateTimeFormat, so it is always current.
