Time Zone Converter

Convert a time into multiple zones at once — great for scheduling across teams.

Cmd/Ctrl-click to pick multiple zones.

Time zones are political boundaries as much as geographic ones

There are over 600 distinct time zone identifiers in the IANA database — far more than the 24 you might expect from dividing a globe into hour-wide strips. India runs on UTC+5:30, Nepal on UTC+5:45, and parts of Australia use 30-minute offsets. Countries choose their offsets for economic and political reasons, not geographic ones. China spans five natural time zones but uses a single official time (UTC+8) across the entire country to project national unity.

Daylight Saving Time is the most error-prone element of time zone conversion. Most of the US 'springs forward' on the second Sunday of March and 'falls back' on the first Sunday of November — but Arizona does not observe DST at all, except the Navajo Nation within Arizona, which does. Australia's DST runs in the opposite season from Europe's. If you schedule a recurring meeting across hemispheres, the gap between participants shifts by one or two hours twice a year.

Frequently asked questions

What is UTC and why is it used as a reference?
UTC (Coordinated Universal Time) is the international time standard that all time zones are defined relative to. It is based on atomic clock measurements and is never adjusted for daylight saving. UTC replaced GMT (Greenwich Mean Time) as the technical standard in 1972, though the terms are often used interchangeably in casual conversation. <strong>Servers, APIs, and databases almost always store timestamps in UTC</strong> and convert to local time only for display — this avoids ambiguity during DST transitions.
Why does a meeting scheduled 'at 9 AM Eastern' sometimes shift by an hour?
Because <strong>Eastern Time is either EST (UTC-5) or EDT (UTC-4)</strong> depending on the time of year, and participants in other regions have different DST schedules. In March and November, the US and Europe switch DST on different dates, creating a two-to-three-week window where the offset between them temporarily changes by one hour. Calendar apps that store meetings in UTC and display in local time handle this correctly; email confirmations with local times do not — always include the UTC offset when scheduling internationally.
What is the International Date Line and how does it affect conversions?
The International Date Line runs roughly along the 180th meridian in the Pacific Ocean. Crossing it westward advances the calendar date by one day; crossing it eastward subtracts a day. Time zone conversions that span the date line can produce results that are a day earlier or later than expected. <strong>American Samoa (UTC-11) and Samoa (UTC+13)</strong> are geographically adjacent but have a 23-hour difference — and a calendar day difference — because Samoa switched sides of the date line in 2011 to align with trading partners.
How do I avoid scheduling mistakes across time zones?
Always confirm meeting times in UTC alongside local times, and use calendar invitations that store the time in UTC rather than a fixed local time. For recurring meetings, <strong>audit the times in March and November</strong> around DST transitions. Tools like World Time Buddy let you see multiple time zones side by side. When in doubt, state the UTC offset explicitly: 'Tuesday at 14:00 UTC' is unambiguous in a way that '2 PM Eastern' is not during the transition weeks.