Compare India and Sydney time side by side to find a meeting time that works for both.
Add a few cities and see their local time laid out side by side across a full day, so you can spot a meeting time that's reasonable for everyone at a glance — rather than converting each city's time zone in your head one at a time.
Every conversion accounts for that city's actual current daylight saving rules automatically, using each location's real time zone database entry rather than a fixed UTC offset — which matters because a fixed offset would be wrong for half the year in any city that observes daylight saving, and some cities don't observe it at all while their neighbors do.
Rows are shaded to highlight roughly typical working hours (8am to 8pm) in each city, so a quick scan down the grid shows you which hours are reasonable everywhere at once, not just technically-possible-but-3am-for-someone.
Nothing here touches a server — all the time zone math runs using your browser's own built-in time zone data.
Yes, automatically — each city’s time is computed from its real time zone rules for today’s date, not a fixed UTC offset, so it stays correct through daylight saving changes without you needing to adjust anything.
A shaded cell means that hour falls within roughly typical working hours (8am–8pm) in that city. Look for a column of shaded cells across every city you’ve added — that’s a time that’s reasonable for everyone, not just convenient for one person.
Up to 6 — beyond that the grid gets too wide to read comfortably on most screens.
Not in this version — it shows the current day’s hours. Since daylight saving dates differ by country, a specific far-future date could shift the exact overlap by an hour in some cities.