How to convert a meeting time across time zones without mistakes
Last updated 2026-10-05
Scheduling across countries goes wrong in predictable ways: someone used today's offset for a date months away, someone assumed a city has no daylight saving, or someone read 03/04 the other way round. A few habits remove nearly all of it.
Convert for the date of the event
The gap between two cities is not constant. 9:00 AM in Kolkata, which has no daylight saving, is 03:30 UTC all year. In New York that is 10:30 PM the previous evening in January, when the city is on UTC−5, but 11:30 PM in July on UTC−4. London shows 03:30 in January and 04:30 in July. Convert using the actual date of the meeting, not today.
Use named zones, not offsets
Choose a place name such as Asia/Kolkata or Europe/London rather than a number such as UTC+1. A name carries that place's daylight-saving rules, so it handles both winter and summer dates, whereas a fixed offset cannot. A meeting set with a fixed offset is the classic one that is an hour out after the clocks change.
Share UTC alongside local times
UTC is the unambiguous reference: two people reading the same UTC time always agree, whatever their local clocks say. When you invite people from several countries, write the time as UTC plus each local time, for example 03:30 UTC on 15 January, which is 9:00 AM in India and 10:30 PM on 14 January in New York. Include the date each time, because the same moment can fall on different calendar days for different people.
Beware the changeover days
Countries change their clocks on different dates, so for a couple of weeks a year the usual gap between two cities is off by an hour. If a meeting falls around a clock change in either place, check the converted time carefully, and read the UTC line to confirm.
Dates and timestamps
Write dates unambiguously, for example 4 March 2026 or 2026-03-04, because 03/04/2026 means 4 March in the US and 3 April in much of the world. Programmers often see times as Unix timestamps, the number of seconds since 1 January 1970 UTC: 1700000000 is 14 November 2023, 22:13:20 UTC. A 13-digit value is the same thing in milliseconds. The Date Format Converter turns any of these into a readable date.
Try it: Time Zone Converter
Free, runs in your browser, nothing is uploaded.
Open Time Zone Converter →