World Clock
Track time across major cities and time zones worldwide. Perfect for scheduling international meetings and staying connected globally.
About the World Clock
Scheduling across time zones is where most meeting invitations go wrong — a slot that looks reasonable in your own calendar can land in the middle of the night somewhere else. A world clock makes the offset visible before you propose a time.
This tool lists time zones with their current local time, shows whether each location is in daylight or darkness, and sorts them by their offset from your own time zone so you can see the spread at a glance.
How to use it
- 1Browse or search the time zone list, which is ordered relative to your own local time.
- 2Add the cities you care about so they stay at the top of the list.
- 3Read the day/night indicator alongside each time to judge whether a proposed slot is reasonable for the other party.
- 4Export the list if you need to share it with colleagues.
When you would use it
- Finding a time that works for a call across several time zones without doing the arithmetic yourself.
- Tracking the working hours of a team in another region so you know when they are actually reachable.
- Checking the calendar date as well as the time, which is what matters when a meeting crosses midnight locally.
How it works, and what it does not do
This tool runs entirely in your browser, using the time zone database built into your operating system by way of the browser’s internationalisation API. Nothing is transmitted, and the times shown are the same ones your device would compute for those regions — there is no second opinion from a server that could disagree.
Two consequences follow. The offsets come from local time zone data, so a device with an out-of-date database can be an hour out for a region that has recently changed its rules; keeping the operating system updated is the fix. And the clock reads your device’s time, so if that is wrong, every city will be wrong by the same amount. Compare against a known-good clock if a result looks surprising.
Frequently asked questions
Does it account for daylight saving time?
Yes. Each zone is resolved through the browser's own time zone database, so daylight saving transitions are applied automatically. Because transition dates differ between countries and are changed by governments at short notice, always confirm an unusual zone close to the date in question.
Why do some offsets include a half hour or three quarters of an hour?
Not all time zones are whole-hour offsets from UTC. India is UTC+5:30, Nepal is UTC+5:45, and several others sit on half-hour offsets. Any tool that only handles whole hours will misreport these places.
Is the time taken from a server?
No. It is calculated in your browser from your device clock using the Internationalization API's time zone data. That keeps it fast and private, but it does mean an incorrect device clock produces incorrect results.
Can I keep a set of cities I check often?
Yes — favourite them and they are remembered in your own browser rather than on a server. They survive a reload, but clearing your browser data removes them, because there is no account behind the list to restore from.
Why does another city show a different date from mine?
Because the date follows local time. Far enough east or west, the calendar day genuinely differs from yours by one — that is the international date line rather than an error, and it is worth noticing before scheduling anything across it.