How does this handle daylight saving time automatically?

Every conversion looks up each city's actual UTC offset for the specific date you entered, using the real time zone rules for that location — not a fixed offset table. A city that observes daylight saving will show a different offset in July than in January, exactly as it would in reality, without you needing to adjust anything manually.

Why does the date sometimes change when I convert a time?

Because time zones can be many hours apart, a time late in the evening in one city often falls on the next calendar day somewhere far enough ahead — or the previous day somewhere far enough behind. The result shows a "+1d" or "−1d" badge whenever the converted date differs from your source date, so this is never ambiguous.

How does "Find meeting time" work?

Each city's business-hours window (9am–5pm by default, adjustable) is converted to the same underlying point in time, then the calculator finds the range where every city's window overlaps. If there's no overlap, it tells you directly rather than showing a misleading partial answer — some city combinations genuinely don't share business hours on the same calendar date.

Why might "Find meeting time" show no overlap even for nearby cities?

Because it checks all cities against the same single calendar date by default. Two cities on opposite sides of the international date line, or separated by 10+ hours, sometimes only overlap if one side's meeting falls on what's technically "tomorrow" for the other — try adjusting the date by a day, or widening the business-hours window, if the default search comes up empty.

Are the city time zones kept up to date?

Yes — conversions use your browser's built-in time zone database (the same IANA database operating systems and browsers maintain and update), not a hand-maintained offset table. That means daylight saving rule changes, and rare historical timezone rule changes, are reflected automatically.

Why does the same business-hours window apply to every city in meeting mode?

It keeps the tool simple and covers the overwhelmingly common case — most people scheduling across time zones are working with a standard 9-to-5-style window. If your actual availability differs by city, use "Convert time" mode instead to manually check specific proposed times against each participant's local clock.

AI Insights

Time Zone Converter

Convert a time between cities worldwide with automatic daylight saving handling, or find a meeting time that works for everyone's business hours.

Last updated August 21, 2026

From city

Date

Time

Convert to

City	Local time	Date	Offset
London	7:56 AM	Thu, Sep 17	UTC+1
Tokyo	3:56 PM	Thu, Sep 17	UTC+9
Sydney	4:56 PM	Thu, Sep 17	UTC+10

When sending out meeting invites across multiple locations, always attach the times to explicit time zones rather than relying on bare numbers to prevent costly confusion. Even without date changes to worry about, a quick double-check of everyone's local working hours keeps early mornings and late nights off your attendees' plates.

AI-generated insight

How to use the time zone converter

1
Pick a mode: Convert time for one date/time converted across several cities, or Find meeting time for a shared availability window.
2
In Convert mode, set your source city, date, and time, then add as many target cities as you need.
3
In Meeting mode, add every participant's city, pick a date, and adjust the shared business-hours window if needed.
4
Results update instantly as you adjust any field, including day-crossing badges and UTC offsets.

How DST is handled automatically

A city's offset from UTC isn't fixed — most of the world's major cities shift their clocks forward or back once or twice a year for daylight saving time, and different regions change on different dates. Rather than relying on a static offset table (which would be wrong for roughly half of every year), this converter looks up each city's real offset for your specific date using the IANA time zone database your browser already maintains — the same data source operating systems and calendar apps use internally.

Worked example: 9:00 AM in New York converts to 2:00 PM in London during summer (New York is UTC−4 on daylight saving), but to 1:00 PM in London during winter (New York shifts to UTC−5) — even though London's own offset doesn't change in this comparison. The converter handles this automatically for whatever date you pick.

Finding a meeting time that works for everyone

Only the hours where every city's business-hours window overlaps count as a valid meeting time.

Each city's business-hours window gets converted to the same underlying timeline, and the calculator finds the overlap — the range every city's window shares in common. New York and London's 9-to-5 windows overlap for three hours (New York's morning is London's afternoon); adding a city like Tokyo, whose entire business day falls outside both of theirs on the same date, can eliminate the overlap entirely.

Scheduling across a lot of dates instead of times? Our Date Calculator and Time Card / Hours Calculator handle date-span and hours-worked math respectively.

Frequently asked questions

Related calculators