Time-zone conversion

Convert a meeting time for everyone

A useful meeting time-zone converter does more than add or subtract hours. It should use the meeting date, each city’s local rules and the length of the meeting.

Open the free meeting planner

Why the date matters

Time-zone differences are not fixed throughout the year. Countries change clocks on different dates, and many never change them. Always convert the actual meeting date rather than relying on a familiar offset.

How to convert a proposed meeting

Read the result in local terms

Start with the proposed time in one city, then read every other row as that participant will experience it. Check both the local date and the full start-to-end range. A meeting that begins during office hours may finish after them, and a late-evening meeting can cross into the following day. The working-hour shading is a guide, not a promise of availability.

Common conversion mistakes

Before you send the invitation

Move the proposed time earlier and later to compare the burden on each city. Check the holiday status for the actual meeting date, then copy or share the result so everyone sees the same cities, date, duration and local times. For recurring meetings, recheck dates near seasonal clock changes rather than assuming the offset stays fixed.

Example: New York, London and Mumbai

Suppose a one-hour call is proposed for 9:00 AM in New York. The converter shows the corresponding local time and date in London and Mumbai using the rules that apply on the selected date. Extend the duration to see whether anyone’s end time leaves normal working hours. Then move the meeting by 30 minutes and compare again. This is more reliable than memorizing offsets because the difference between New York and London changes temporarily when their daylight-saving dates do not match.

Why city names are better than abbreviations

Abbreviations such as CST, IST and BST can describe more than one time zone. A city plus a date is much less ambiguous because it identifies a named time zone and the seasonal rule in force. When sharing a proposal, include readable local times as well as the restoring link; recipients can understand the message immediately and reopen the full comparison if they want to test another time.

The three weeks each year when the gap changes

North America and Europe do not change their clocks on the same day, so the difference between them shifts twice a year for about three weeks at a time. In 2026 the United States moves on 8 March and 1 November, while the United Kingdom and most of Europe move on 29 March and 25 October. London is normally five hours ahead of New York, but between 8 and 29 March, and again between 25 October and 1 November, it is only four. A recurring call that felt comfortable in February can land an hour early in the middle of March without anyone having touched the invitation.

Why time-zone abbreviations are unreliable

Converting a meeting that repeats

Choose one city as the anchor — usually where the meeting owner sits — and keep that local time fixed. Everyone else’s local time will then move by an hour whenever their own region changes clocks. That is the real trade-off: either the anchor city stays stable and the others drift, or everyone else stays stable and the anchor moves. Decide which before the first invitation goes out, and re-check the series in March, April, September and October, when most of the world’s transitions fall.

A worked example across the March transition

A one-hour call is set for 9:00 AM in New York. On 1 March that is 2:00 PM in London and 7:30 PM in Mumbai. On 15 March, after the United States has moved its clocks but Europe has not, the same 9:00 AM in New York becomes 1:00 PM in London, and Mumbai shifts to 6:30 PM. By 1 April, once Europe has moved as well, London is back to 2:00 PM. India never changed anything — Mumbai moved because New York did.