Time zones · DST handled

Same meeting.
Different clocks.

Choose a date and time once, then see what it means in New York, Los Angeles, London, Tokyo, or anywhere else on the call.

Your meeting details stay on this device. Time-zone conversion uses the rules built into your browser; nothing is submitted.

01

Set one time, compare every clock

Your city choices are remembered. The meeting date and time are not.

Quiet memory: selected cities and working hours update automatically on this device.

The useful details

Clear enough to send without a correction.

01

Date changes stay visible

If one city has moved into yesterday or tomorrow, the card says so plainly.

02

DST follows the date

The browser applies the correct offset for the meeting date instead of using a fixed EST or PST guess.

03

Working hours are yours

Set the start and end of a reasonable day, then let the planner search for overlap.

Straight answers

Time-zone questions.

Does this handle daylight saving time?

Yes. It uses IANA time-zone identifiers and the date-aware rules provided by your browser. The same city can have a different UTC offset in winter and summer.

Why not just use EST, CST, MST, and PST?

Those abbreviations can be ambiguous and do not always communicate whether daylight saving time is active. City-based zones such as America/New_York are safer.

What happens during a daylight-saving clock change?

A local time can be skipped or repeated on the transition night. If the entered wall time cannot be represented exactly, the planner flags it so you can choose a less dramatic hour.

Are the suggested overlaps guaranteed to suit everyone?

No. They only check the working-hour window you selected. Lunch, school pickup, local holidays, and a teammate’s strong feelings about 8:00 a.m. still deserve a human check.