
Convert one meeting time for London, Mumbai and Sydney, see the March daylight-saving trap, and handle times that do not exist.
A recurring 9 a.m. Pacific call looks simple until the clocks change in one country and not in another. Time Zone Converter converts one wall-clock time into any other zone using the real offsets on that date, and it can show the same moment in up to six extra zones at once.
The clip below shows a basic conversion.
Imagine a small design studio in Los Angeles with a contractor in London, a developer in Mumbai and a client in Sydney. The weekly call is Monday at 9:00 a.m. Los Angeles time. Pick "America/Los Angeles" under From, type the date and time into the date-and-time field, choose London under To, and add Mumbai (Asia/Kolkata) and Sydney through the "Also show the same moment in" selector. Each zone shows the full date, the time and its UTC offset.
The interesting part is the date you choose. We ran this exact setup for three Mondays in 2026:
London lost an hour for a few weeks, not because anyone changed the meeting, but because the United States and the United Kingdom change their clocks on different weekends. India does not use daylight saving, so Mumbai's evening slot moved a full hour earlier when the US changed, then stayed put when the UK followed. Sydney, which was still on summer time, also moved an hour earlier. Without checking each date, a weekly invite quietly drifts.
The hour you type is always read in the From zone. Changing the From zone afterwards keeps the typed numbers and reads them in the new zone, so check the result again after any change.
Two dates a year cause real confusion, and the tool says so rather than guessing. On 8 March 2026 in Los Angeles, the clock jumps from 2:00 a.m. straight to 3:00 a.m., so 2:30 a.m. never happens. The converter shows an amber notice that the time does not exist and reads it as the first valid time after the jump.
In the autumn the opposite happens: on 1 November 2026, 1:30 a.m. occurs twice in Los Angeles. The converter warns that the time is ambiguous and shows the first occurrence. If you are scheduling something near those hours, name the zone and the offset in the invitation, for example "1:30 a.m. PDT", so nobody has to guess.
If you have built an agenda for an event in the Event Day Schedule, it appears underneath the converter in the zones you picked. Each session is shown in the agenda zone and every chosen zone, with a marker like +1 day when the date changes, which is the line you want when a Sydney attendee joins a Pacific morning session. You can copy the agenda as text or download it as a CSV file to paste into an invitation or spreadsheet.
Picking a country-sized label instead of a city is the common one. Names in the list are city-based zone names, because some countries have several zones and the rules differ by region. Another is forgetting that the date can move: a 4 a.m. Tuesday in Sydney is a Monday call for the Pacific side. A third is assuming that a half-hour offset is a typo. India's offset is five and a half hours ahead of UTC, so Mumbai times often end in :30.
Also remember that the converter reads the offset for the date you typed, not for today. A future date in a month where a country changes its clocks is converted with the rules known to the browser's time zone database, which governments occasionally update, so confirm any critical one-off event the week before.
If you are working with raw machine timestamps from logs or databases, the Timestamp Converter turns epoch numbers into readable dates. For event planning with several sessions, the Event Day Schedule builds the agenda that the converter then translates. More conversion tools are in the converters category.
The conversion runs in your browser. Using the converter counts toward your 10 trial uses for the day, and once that limit is reached the result is hidden until the allowance resets or you move to a paid plan.
Write the time in the sender's zone and in each recipient's zone, name the date, and mention if one city is about to change its clocks. A single line such as "Monday 9 March, 9:00 a.m. Los Angeles / 4:00 p.m. London / 9:30 p.m. Mumbai" saves several replies.
Which scheduling headache would you like covered next: recurring meetings across a clock change, webinars for a global audience or travel itineraries with long flights? Tell us on the contact page.