Time Zone Converter and World Clock — 80+ Cities
Convert times between any cities instantly — PKT to EST, IST to PST, GMT to IST, EST to JST, and more. Keep a live multiple time zone clock online for all your key locations with analog clocks, DST support, and 12/24h toggle.
Why Scheduling Across Zones Goes Wrong
Converting a single time between two places is arithmetic. Scheduling a recurring meeting across them is not, and almost every failure comes from one of four assumptions that feel safe and are not.
| The assumption | Why it fails |
|---|---|
| A zone has a fixed offset from UTC | Daylight saving moves it twice a year in many places, and not at all in others |
| Offsets are whole hours | Several zones are offset by 30 or even 45 minutes |
| An abbreviation identifies a zone | The same letters are used by different zones on different continents |
| A country has one time | Some large countries span several zones; others deliberately use one |
Offsets Are Not Fixed
The gap between two places changes during the year, and it changes by different amounts depending on whether each place observes daylight saving and when it switches.
Two cities that are five hours apart for most of the year can be four or six hours apart for a few weeks, because their clock changes fall on different dates. The Northern and Southern hemispheres shift in opposite directions, so the gap between a European and an Australian city can move by two hours rather than one.
The practical consequence is the recurring-meeting problem. A call set for 15:00 in one city and 10:00 in another stays correct until one of them changes its clocks, at which point the meeting silently moves an hour for one participant. Anyone who has arrived an hour early to a standing call in late March or October has met this.
The reliable fix is to agree the meeting in one anchor location and let everyone else convert, rather than agreeing two local times as if they were permanently linked.
Not Every Zone Is a Whole Hour Off
The assumption that offsets come in whole hours is built into a surprising amount of mental arithmetic, and it breaks in several parts of the world.
- Half-hour offsets are used across South Asia, in parts of Australia, and in Newfoundland among others. A meeting time that lands on the hour in one place lands on the half hour in the other.
- Forty-five-minute offsets exist too, in Nepal and in the Chatham Islands. These are rare enough that many scheduling habits simply do not account for them.
- Offsets beyond twelve hours exist on both sides, so the total spread across the world is more than 24 hours. At certain moments three different calendar dates are in use simultaneously.
Abbreviations Are Ambiguous
Zone abbreviations look precise and are not standardised. Several are used by more than one zone.
| Abbreviation | Can mean |
|---|---|
| CST | Central Standard Time in North America, China Standard Time, or Cuba Standard Time |
| IST | India, Ireland, or Israel Standard Time |
| BST | British Summer Time or Bangladesh Standard Time |
| AMT | Amazon Time or Armenia Time |
Where precision matters, name the city or use the UTC offset for the specific date. "14:00 UTC" is unambiguous; "2pm CST" is not, and the difference between the readings can be thirteen hours.
There is a second trap in the standard-versus-summer distinction. EST and EDT are different offsets an hour apart, so writing EST during summer is technically wrong and frequently means the writer meant the current local time rather than standard time.
Country Does Not Mean Time Zone
Some countries span many zones and split accordingly; others span many and use a single time anyway, as a matter of policy. China is the best-known example of a country covering a wide longitudinal range on one official time, which means the sun rises at very different clock times across it.
The reverse case matters just as much for scheduling. In countries with several zones, saying you are "in the US" or "in Australia" narrows the answer to a range of several hours rather than pinning it down. Always exchange cities rather than countries.
Finding a Time That Works for Everyone
For two or three locations, a workable window is usually findable. For more than that, someone is going to be inconvenienced, and the useful question becomes who and how often.
- List each participant's acceptable window in their own local time, then convert all of them into one reference zone and look for the overlap.
- Where no overlap exists, rotate the inconvenience between meetings rather than fixing it permanently on whoever is furthest away.
- Watch the date, not just the hour. A Friday afternoon call in one place can be Saturday morning in another, which no amount of goodwill fixes.
- Send invitations from a calendar rather than as written times. A calendar entry carries the underlying instant and converts itself; text does not.
Writing a Time So It Cannot Be Misread
When a time has to be communicated as text, three habits remove almost all ambiguity.
Use the 24-hour clock, which eliminates the midnight and midday confusion that AM and PM create. Name the city rather than an abbreviation. And include the date, since the same instant can fall on different days for different readers.
"Thursday 14:00 in London" can be converted by anyone without ambiguity. "2pm BST" requires the reader to know which BST you mean and whether summer time is in effect on that date.
For durations and elapsed time rather than clock conversions, the time calculator handles the arithmetic, and the days between dates calculator covers spans measured in days.
Time Zone Questions
Why did my recurring meeting shift by an hour?
Is the time difference between two cities always the same?
Are all time zones a whole number of hours from UTC?
What does CST actually mean?
Should I write EST or EDT?
Does everyone in one country share the same time?
How do I write a time so nobody misreads it?
Why does a meeting land on a different day for some people?
What is the best way to schedule across many time zones?
Last updated