Time zone converter — compare cities at a glance
Compare a moment in time across several cities at once. Daylight saving is applied correctly for the date you choose, not assumed from today.
Runs entirely in your browser — nothing is uploaded.
Currently following the live clock.
Offsets come from your browser’s IANA timezone data, so daylight saving is handled correctly for the specific date — not assumed from today. Zones that observe DST shift on different dates in each hemisphere.
How to use
- Pick a reference zone and time. Or leave it on the live clock to see current times everywhere.
- Add the zones you care about. Each shows the local time, date, weekday and UTC offset.
- Read the offsets. Useful when scheduling — a difference that holds today may not hold next month.
Questions
How does it handle daylight saving?
Offsets come from your browser’s IANA timezone database and are calculated for the specific instant, so a meeting in March gets March’s offset. This matters because the northern and southern hemispheres shift on different dates.
Why do some zones have half-hour offsets?
Not every zone is a whole hour from UTC. India is UTC+5:30, Nepal is UTC+5:45, and parts of Australia are UTC+9:30. Any tool that assumes whole hours gets these wrong.
What is the safest way to schedule across zones?
Agree the time in UTC, then let each person convert. Naming a city is second best — it at least handles DST — but describing a time as "3pm my time" is how meetings get missed.
What do the abbreviations mean?
CET, EST, AEDT and so on are the short names your browser reports for the zone at that moment. They change with daylight saving, and several are ambiguous worldwide, which is why the numeric UTC offset is shown alongside.