World Clock Converter and Work-Hour Comparison
Distinguish the current time from the selected meeting time. Compare local dates, the base time zone and work-hour overlap before using a conversion for a real appointment.
Choosing a time in the updated layout
Set the cities and work hours in the regions section, then compare them on the timeline. The grid height follows the number of regions. On desktop, time controls sit below the grid on the left and suggestions on the right. On a phone, they follow in that order vertically. Time controls remain available with just one region.
The left and right arrows above the grid move one day at a time. The arrows beside the large start–end time below it move the whole meeting 15 minutes earlier or later, preserving its length. Crossing midnight changes the date too. You can also type a start time or choose a length from 15 minutes to eight hours.
The time controls are visible before a time is selected. The initial dashed range is a prompt, so no verdict appears yet. Select the timeline or change the date, start or length to see work-hour status and whether calendars have been checked. Expand the regional time and status details for local dates and times. Suggestions do not confirm attendance; agree on the final time with participants.
The time now and the meeting time are different questions
Use the Now line on the timeline to check the current time. Before selecting a meeting, the region labels show current local times; after selecting one, they show that meeting’s local times. Pick a date and time on the Timeline below, and each region’s row and the Selected meeting card show what that meeting time is locally. “What time is it in New York now?” and “What time is next Tuesday’s meeting in New York?” can have different answers, so check a meeting by selecting its date.
Where the local date changes, the timeline shows the date at local midnight, and the Selected meeting card lists each region’s date.
Offsets change with the date
In regions that use daylight saving, the offset moves by an hour after each change. In autumn 2026, London returns to standard time on October 25 and New York and Los Angeles on November 1, while Sydney moved forward on October 4. The same “10 PM in Seoul” lands at a different local time depending on the date.
| City | 2026-10-20 | 2026-11-10 |
|---|---|---|
| Seoul | UTC+9 | UTC+9 |
| New York | UTC−4 | UTC−5 |
| London | UTC+1 | UTC+0 |
| Los Angeles | UTC−7 | UTC−8 |
| Sydney | UTC+11 | UTC+11 |
| Mumbai | UTC+5:30 | UTC+5:30 |
| Kathmandu | UTC+5:45 | UTC+5:45 |
| St. John’s (Newfoundland) | UTC−2:30 | UTC−3:30 |
When2Overlap calculates offsets for each date from the browser’s IANA time-zone data, so half-hour and 45-minute zones and daylight-saving changes need no manual entry. Regions with a change within seven days show “Clock change in N days” on the timeline.
Compare work hours, not just clocks
An offset tells you what time it is, not whether anyone is working. Press a region chip to set that region’s real work hours; the timeline’s Overlap row then shows when everyone is at work, and picking a time names any region outside work hours and why. Times can be shown in 24-hour, 12-hour or mixed format.
For choosing and sharing meeting options, see the When2Overlap guide or the timezone meeting scheduler.
Add your cities and check the offsets
Time-zone comparison and work-hour overlap work without signing in.