How to Convert Time Zones for a Meeting (Without DST Mistakes)

"Let's meet at 3 pm" works in one office. Across three countries it's a recipe for someone waiting in an empty call. Converting times is easy once you avoid a few traps.

Offsets, zones and why abbreviations mislead

A UTC offset is the difference to Coordinated Universal Time, for example UTC+1. A time zone is a region's full set of rules: its offset and when it switches for daylight saving time (DST).

That's why abbreviations cause mistakes:

• CST can mean US Central Standard Time (UTC−6) or China Standard Time (UTC+8).
• EST is strictly UTC−5, but people say "EST" in July when New York is actually on EDT (UTC−4).
• IST is used for India, Ireland and Israel.

Use a city or an IANA zone name such as America/New_York or Europe/Berlin. Converters and calendars then apply the correct DST rules automatically.

The daylight saving gap

The US switches to summer time on the second Sunday in March and back on the first Sunday in November. The EU switches on the last Sunday in March and the last Sunday in October. Many countries, including most of Asia, don't use DST at all, and in the Southern Hemisphere the seasons are reversed.

Result: for about three weeks in March and one week around late October and early November, New York is only 5 hours behind Berlin instead of the usual 6. Recurring meetings set up in one calendar can shift by an hour for the other side during those weeks.

Converting a single time

1. Open the time zone converter.
2. Add the cities involved. Your own zone is added automatically.
3. Enter the date and time in any row, or drag the time slider. All other rows update.
4. Check the markers: a "+1" means the time falls on the next day there, and a DST badge warns when a zone is in summer time.

Always enter the date as well as the time. The same wall-clock time converts differently before and after a DST change.

Finding a time that works for a group

Converting one proposal at a time and asking around is slow. Instead:

1. Open the meeting planner and add each participant's location.
2. Set working hours, for example 9:00–17:00, for each person.
3. Pick the day. The planner shows a 24-hour grid for every participant, with working hours, evenings and night marked.
4. Choose a slot in the highlighted overlap.
5. Copy the invitation text, which lists the time for every participant, or download an .ics calendar file.

Calendar files carry the time zone with them, so everyone's calendar shows the meeting at the correct local time, even after a DST change.

Rules of thumb for international teams

• Europe and the US East Coast: the overlap is usually the European afternoon, New York morning.
• Europe and India: easy, with a 3.5–4.5 hour difference depending on DST.
• US West Coast and Asia-Pacific: the working-hours overlap is small or none. Rotate early and late meetings so the same people aren't always stuck at 7 am or 9 pm.
• Write times with the zone in emails: "15:00 Berlin / 9:00 New York".

Counting down to the meeting

For launches or events across many time zones, a shared countdown link shows everyone the same remaining time, no conversion needed.

Frequently asked questions

Should I schedule in UTC? For technical teams and logs, UTC avoids confusion. For invitations to people, local times with the city name are friendlier, and calendar files handle the conversion anyway.