Plan across time zones without losing the date
A time conversion describes one instant. Start with the date and clock time in the first city, then read the complete date, time and UTC offset in the destination. These examples use explicit dates so you can reproduce them.
Before sending an invitation
- Choose the city where the original time is stated. Enter its local date and time, even when your device is elsewhere.
- Read the destination date as well as the hour. A previous or following day is part of the result, not an error.
- For a meeting, set both working windows and the duration. Check the suggested slot with participants before sharing.
Three situations worth checking
A recurring New York–Tokyo call
The same 09:00 start in New York gives different Tokyo times in January and July. Recheck future occurrences; sharing one converted instant does not create a recurring calendar event.
| Original local date and time | Destination date and time | Worked example |
|---|---|---|
| 2026-01-15 09:00 -05:00 | 2026-01-15 23:00 +09:00 | Open this example |
| 2026-07-15 09:00 -04:00 | 2026-07-15 22:00 +09:00 | Open this example |
A London meeting during the March changeover
The UK and the US change clocks on different dates. The two March examples show why a familiar time difference can briefly change. Convert the actual meeting date instead of adding a memorized offset.
| Original local date and time | Destination date and time | Worked example |
|---|---|---|
| 2026-03-20 09:00 +00:00 | 2026-03-20 05:00 -04:00 | Open this example |
| 2026-03-30 09:00 +01:00 | 2026-03-30 04:00 -04:00 | Open this example |
An early Seoul call on the previous Los Angeles day
A 00:30 start in Seoul falls on the previous calendar date in Los Angeles. Include both dates in your message so the recipient does not join one day late.
| Original local date and time | Destination date and time | Worked example |
|---|---|---|
| 2026-01-15 00:30 +09:00 | 2026-01-14 07:30 -08:00 | Open this example |
City time, fixed offsets and repeated hours
Choose Los Angeles for a local appointment; PST is a fixed UTC−08:00 reference and does not become summer time. During a clock change, a local hour may be missing or occur twice. Distinguish repeated hours by their displayed UTC offset and check it before sharing.
What the result does and does not promise
Working-hour suggestions compare the windows you enter; they do not read personal calendars or public holidays. Time-zone rules depend on your browser’s data, so update the browser and recheck important future appointments. Shared links contain the selected time and planning settings. Saved plans stay in that browser; they are not a cross-device account.
Reference and method
City calculations use named IANA time zones. The worked examples use the same conversion functions as the calculator; the UK reference explains its clock-change dates.