Free tool
Convert any time between any cities. Add as many zones as you want, share the link, or embed the live widget on your site. Every row is editable: change one, the others move with it.
Colombia · Tue · UTC-05:00Business
United States · Tue · UTC-04:00Business
Pick the day, type a time in any row, and every other zone updates instantly. The row you typed in becomes the pivot. Add more cities with the "Add zone" button. When you find a time that works, hit "Copy share link", your teammates open the same view.
Old converters force you to pick a "from" and a "to" zone, type the source time, then stare at one output. Real scheduling involves three or four cities, and you want to nudge each one to see what the other side looks like. ClockOrbit's converter lets every row be an input, adjust freely until you spot the overlap.
Built on the IANA tzdata, so DST rules are correct for every city and every year. If you need a live world clock rather than a snapshot, the homepage shows ticking clocks for any set of cities.
The converter opens with San Francisco, New York, and London, pivoting on 09:00. For most of the year the arithmetic runs like this: 09:00 in San Francisco is 12:00 in New York, because the two coasts sit three hours apart, and 17:00 in London, eight hours ahead of the US west coast. Type 17:00 into the London row instead and the other two rows walk backwards to the same instant. Nothing about the moment in time changed; only the row doing the steering did. That symmetry is the whole trick: once you stop thinking in "from" and "to" and start thinking in one shared instant, multi-city scheduling gets much less error-prone.
North America and Europe do not change their clocks on the same weekend. The United States and Canada spring forward on the second Sunday of March, while the United Kingdom and the European Union wait until the last Sunday of March. In autumn the order reverses: Europe falls back on the last Sunday of October, North America on the first Sunday of November. During those short windows the London to New York gap shrinks from five hours to four, and a recurring call booked as "same time as last week" quietly lands an hour off for one side. Because every row here resolves its date against the IANA timezone database, changing the date field is enough to spot the slip before it costs anyone a meeting.
Not every zone sits a round number of hours from UTC, which is exactly where mental arithmetic tends to fail. Some widely used examples:
| Region | Base offset from UTC |
|---|---|
| India | +5:30 |
| Iran | +3:30 |
| Afghanistan | +4:30 |
| Myanmar | +6:30 |
| Newfoundland, Canada | -3:30 |
| Central Australia (Adelaide, Darwin) | +9:30 |
| Nepal | +5:45 |
| Chatham Islands, New Zealand | +12:45 |
A few of these regions also observe daylight saving on top of the base offset, so the half-hour difference can combine with a seasonal shift. For example, 09:00 in London during British Summer Time is 13:30 in Mumbai, but the same 09:00 in January, when London is back on GMT, is 14:30 there. The converter carries the fractional part for you either way.
Yes. Each city resolves through its IANA timezone rules for the exact date you pick, so the offset already includes any daylight saving in force on that day.
The pivot is the row you last typed a time into. That wall-clock time is held fixed and every other row is recalculated from the same instant, so any city can steer the conversion.
Yes. Pick any date and the timezone rules published for that date are applied. Keep in mind that governments occasionally change their rules, so a conversion years ahead uses the rules as currently published.
Either they share one timezone, like Manchester and London, or their zones happen to sit at the same offset on that date, like London and Dublin.
Yes. Offsets such as India at UTC+5:30 or Nepal at UTC+5:45 are applied exactly as defined, never rounded to the nearest hour.