What time is my meeting in another time zone on a specific date?
Short answer: The Time Zone Meeting Planner converts a date and clock time from one named time zone to another, using the UTC offset each zone has on that exact date. Enter 10:00 AM in New York on March 16, 2026 and it returns 2:00 PM in London (14:00 UTC), because the US had already switched to daylight time and the UK had not.
Key facts
- Each dropdown in the Time Zone Meeting Planner offers 15 choices: UTC, Los Angeles, Denver, Chicago, New York, Toronto, São Paulo, London, Paris, Moscow, Dubai, Kolkata, Singapore, Tokyo and Sydney.
- The planner reads the Date and time field as wall-clock time in the "Time is in" zone, not in your computer's zone.
- Daylight saving comes from the time-zone database built into your browser, so the tool has no rule table of its own.
- On load, "Time is in" is set to your browser's zone if it appears in the list (otherwise UTC), "Convert to" starts on New York, and the date and time start at the current moment.
- The result shows three lines: the time in the source zone, the corresponding time in the destination zone, and the UTC instant in ISO 8601 format. Precision is one minute.
- A local time that was skipped by a spring clock change produces an error message instead of a guess.
- The conversion runs in the page's JavaScript with no network requests, so the date and zones you enter are not uploaded.
How to use
- Pick the meeting's date and clock time in the Date and time field.
- Choose the zone where that time was written in the "Time is in" dropdown. If a colleague says "10:00 in Chicago", pick Chicago even if you are elsewhere.
- Choose the place you need the time for in the "Convert to" dropdown.
- Press Convert time and read the highlighted destination line, including the weekday and date.
Formula and logic
A zone's offset from UTC depends on the instant being converted, so the planner works in two steps: find the UTC instant, then express it in the other zone.
utc_instant = entered_wall_clock - offset(source_zone, instant)
destination_time = utc_instant + offset(destination_zone, instant)Because the source offset is only known once the instant is known, the code starts by treating the entered time as UTC, checks what clock reading that instant has in the source zone, and corrects by the difference. It repeats this up to five times, then confirms that the result reads back as exactly what you typed. Nothing is rounded: minutes are kept, so a half-hour zone such as Kolkata stays at :30.
Worked example
These rows come from running the same conversion logic with the en-US display format.
| Input (time is in) | Convert to | Destination result | UTC instant |
|---|---|---|---|
| Mar 2, 2026, 10:00 AM (New York) | London | 3:00 PM GMT, 5 hours ahead | 15:00 |
| Mar 16, 2026, 10:00 AM (New York) | London | 2:00 PM GMT, 4 hours ahead | 14:00 |
| Apr 6, 2026, 10:00 AM (New York) | London | 3:00 PM GMT+1, 5 hours ahead | 14:00 |
| Oct 28, 2026, 9:00 AM (New York) | London | 1:00 PM GMT, 4 hours ahead | 13:00 |
| Oct 21, 2026, 9:00 AM (Tokyo) | Los Angeles | Tuesday, Oct 20, 5:00 PM PDT | 00:00 on Oct 21 |
| Jan 15, 2026, 4:00 PM (Moscow) | New York | 8:00 AM EST | 13:00 |
| Jul 15, 2026, 4:00 PM (Moscow) | New York | 9:00 AM EDT | 13:00 |
Why New York and London are sometimes 4 hours apart
The US and the UK start and end daylight saving on different dates. For three weeks in spring and one in autumn, the usual 5-hour gap shrinks to 4. Rows two and four of the table land in those windows.
If your recurring "10:00 New York" call shows up an hour earlier for the London team in late March, nobody made a mistake. Convert the actual meeting date, not the date you remember the gap from.
When the clock skips or repeats an hour
On March 8, 2026, New York clocks jump from 2:00 AM to 3:00 AM, so 2:30 AM never exists. Enter it with New York as the source and the planner replies that the local time does not exist because of a clock change.
In autumn the opposite happens: 1:30 AM on November 1, 2026 occurs twice in New York. The planner does not warn you. With the current code it returns the first occurrence (EDT, 05:30 UTC). For the second one, enter 06:30 with UTC as the source and convert to New York.
Crossing midnight and the date line
A 9:00 AM Wednesday call in Tokyo is still Tuesday afternoon in Los Angeles. Going the other way, 9:00 AM Wednesday in Los Angeles is 1:00 AM Thursday in Tokyo.
Read the weekday and date in the result, not just the hour, and share the full date with the city name so nobody has to repeat the arithmetic.
Zones that never change, and why Moscow still moves
Moscow keeps UTC+3 all year, yet its gap to New York changes by an hour between January and July (rows six and seven). The movement comes entirely from New York's daylight saving.
What this tool does not do
- The Time Zone Meeting Planner covers only the 15 listed zones. It has no field for cities such as Berlin, Phoenix, Shanghai or Auckland, so choose a listed city that follows the same clock rules or work in UTC.
- The planner converts one time between two zones at a time, with no multi-zone overlay or search for working hours that suit everyone.
- The planner does not create calendar events, send invitations or check anyone's availability.
- The planner depends on your browser's time-zone data. If a government changes its clock rules, a browser that has not updated may show the old result, so confirm important future meetings in participants' calendars.
Frequently asked questions
How do I convert a meeting time from New York to London on a specific date?
Enter the date and time, set "Time is in" to New York, set "Convert to" to London and press Convert time. For 10:00 AM on March 16, 2026 the result is 2:00 PM in London, because the date decides which UTC offsets apply.
Why is New York sometimes 4 hours behind London instead of 5?
The two places change their clocks on different dates, so the gap shrinks for a few weeks each spring and autumn. In 2026 the planner shows 4 hours on March 16 and October 28, and 5 hours on March 2 and April 6.
Which time zones can I choose in the planner?
You can choose UTC and 14 cities: Los Angeles, Denver, Chicago, New York, Toronto, São Paulo, London, Paris, Moscow, Dubai, Kolkata, Singapore, Tokyo and Sydney. Other cities are not in the dropdowns.
What happens if I enter a time that doesn't exist because of daylight saving?
The planner shows an error saying that local time does not exist in the zone. For example, 2:30 AM on March 8, 2026 in New York is skipped, so you need to pick a different time.
How does the planner treat the hour that repeats when clocks go back?
It returns a single result and does not flag the ambiguity. For 1:30 AM on November 1, 2026 in New York it gives the first occurrence, 05:30 UTC. Use a UTC source time to reach the second one.
Can the converted meeting land on a different day?
Yes. The result includes the weekday and full date of the destination, so a 9:00 AM Wednesday meeting in Tokyo shows as Tuesday, October 20 at 5:00 PM in Los Angeles when the date is October 21, 2026.
Does the planner send a calendar invite or find a time that works for everyone?
No. It converts one date and time between two zones and shows the result on screen. Copy the confirmed local date, time and zone into your own calendar or message.
Is the time I enter uploaded anywhere?
No. The conversion runs in the page's JavaScript using your browser's time-zone data, and the script makes no network requests with the values you enter.
Related tools
Last reviewed: