worldclock.tools

Precision time, everywhere

The world clock for every hour, everywhere.

Live local time for 34,043 cities, a meeting planner that finds the hour everyone is awake, and 36 time zone converters, timers and developer utilities. Free, no account, and computed entirely in your browser.

123456789101112
Your city
––:––:––
Daylight, right now — from the international date line, east to west−180° → +180°
––:––Honolulu
––:––Los Angeles
––:––New York City
––:––London
––:––Cairo
––:––Dubai
––:––Bangkok
––:––Tokyo
––:––Sydney
Los Angeles
United States
––:––:––
London
United Kingdom
––:––:––
Dubai
United Arab Emirates
––:––:––
Tokyo
Japan
––:––:––

The suite

One meridian, every kind of time.

36 tools · all live

How it works

Time computed in your browser, not on a server.

Every clock, conversion and countdown here is calculated locally by your own browser, using the IANA time zone database that ships inside it — the same database operating systems use. That has two consequences worth knowing. The results reflect current daylight-saving rules for each zone independently, including the weeks when one region has changed its clocks and another has not. And what you enter is never transmitted: no converter input, no meeting time, no saved board leaves the page. There is no geolocation prompt and no account.

It also means the tools keep working when the network does not. Once a page has loaded, the time zone rules are already present, so clocks keep ticking and converters keep converting offline. Searching the full city dataset is the one action that needs a connection, and that request carries the letters you type and nothing else — the privacy policy lists every request the site makes.

The city data comes from GeoNames, which gives each of the 34,043 cities its own coordinates and IANA zone rather than a country-level guess. That distinction matters more than it sounds: the United States spans six zones, Russia eleven, and Australia splits by state, so two cities in one country can differ by hours and behave differently at a daylight-saving boundary.

Common questions

Is worldclock.tools free?
Yes — every one of the 36 tools is free, with no account, no sign-up and no paywall. There are no ads. The only third-party script is Google Analytics, used to count page views; nothing you enter into a tool is ever sent anywhere.
How accurate are the clocks?
Every clock and conversion is computed in your browser from your device's clock and the IANA time zone database that ships with it. That database is the same one operating systems use, so daylight-saving rules are current and each city is handled by its own zone rather than a country-wide assumption. Accuracy is therefore limited only by how well your own device clock is synchronised.
Does the site send my data anywhere?
Nothing you type into a tool. Every calculation runs locally in the page, there is no geolocation prompt and no account, and saved boards and preferences live in your browser's local storage rather than on a server. Two requests do leave your browser: city search, which sends the letters you typed and nothing else, and Google Analytics, which records anonymous page views and sets its own cookies. The privacy policy lists every request the site makes and how to block the analytics one.
How many cities are supported?
34,043 cities across 244 countries and territories, from the GeoNames geographical database. Each carries its own coordinates and IANA time zone, so local time, daylight saving and sun times are computed from real data for the specific city rather than for its country.
Why does the time difference between two cities change during the year?
Because each zone follows its own daylight-saving rule and they change on different dates. New York and London are normally five hours apart but four for a couple of weeks in March, when the United States has moved its clocks and Europe has not. Between hemispheres the swing is larger still, because the two sides move in opposite directions.
Can I use these tools offline?
Largely, yes. Once a page has loaded, the clocks, converters and timers keep working without a connection because the computation and the time zone rules are already in your browser. Only searching the full city dataset needs the network.