World Time
Search a city or scan major regions fast.
Major cities grouped for faster scanning. Times update by minute and show hours and minutes only.
North and South America at a glance.
Oceania and Pacific-facing workday hours.
Core business hubs across western Europe.
Eastern Europe and nearby cross-border time zones.
Key time zones spanning Gulf and African cities.
Major Asian cities used in travel, trade, and remote work.
Every city listed above shows live local time, updated in your browser from your device's clock and the timezone rules it already carries. Nothing is cached or approximated, so the times stay correct even on the weekends when a region shifts its clocks. Select any city to open its full page, with the current date, the time zone it belongs to, and its UTC offset right now.
Beyond looking up a single city, three tools cover the situations that actually come up. The desk clock turns any city into a large fullscreen display for a second monitor, a tablet, or a meeting-room screen. Dual time puts two cities side by side, which is the fastest way to answer "is it a reasonable hour for them right now?" without doing arithmetic. The time difference tool converts a specific hour between two cities and shows the gap, including the date change when a conversion crosses midnight.
The most common scheduling mistake is treating a time gap as a fixed number. It usually is not. Daylight saving time moves a region's clocks by an hour twice a year, and the schedules do not line up between countries: the United States changes on the second Sunday of March, the European Union on the last Sunday of March, and most of Asia — Korea, Japan, China, India, Singapore — never changes at all. That means the gap between London and New York is five hours for most of the year but four for a few weeks each spring and autumn, and the gap between London and Sydney cycles through nine, ten, and eleven hours because the two cities shift in opposite seasons.
Offsets are not always whole hours either. India runs on UTC+5:30, Iran on UTC+3:30, Nepal on UTC+5:45, and parts of Australia use half-hour offsets. Rounding those to the nearest hour is how a call ends up starting thirty minutes wrong. Time zone borders follow politics rather than longitude, too — China spans five geographic bands but keeps one national clock, and Spain sits on Central European Time despite lining up with the UK.
This is why the pages here are organized by city rather than by offset. Each clock asks your browser for the current time in a named zone such as Asia/Seoul or America/New_York, and the browser applies whatever rules are in force today, drawn from the IANA time zone database that operating systems keep updated as governments change their policies. You get the current answer instead of one you have to remember to revise.
Pick one anchor city and quote every time in it, with the city name attached — "10:00 Seoul time", never a bare "10:00". Keeping a dual clock visible builds an intuition for the overlap window that mental math never does, and it makes the twice-yearly daylight saving shift obvious instead of surprising.
Look up the destination city before booking connections or messaging anyone on arrival. On long-haul routes the calendar date matters as much as the hour: fly west across the date line and you can land before your departure time; fly east and a day disappears from the itinerary.
Open the other city's clock before you call rather than after. A glance answers the only question that matters — whether it is a decent hour there — and it saves the mental conversion that people get wrong most often late in their own evening.
For a market open, a submission deadline, or a launch window, keep the relevant city on a desk clock for the day. Watching the actual city time is more reliable than a countdown you set from a converted figure, because the conversion is where errors enter.
They read your device's own clock and convert it into the city's time zone using the rules your browser already has. If your device time is correct, the city time is correct. If a clock here looks wrong by a whole number of hours, the usual cause is that the device's own time or time zone setting has drifted.
For scheduling purposes they refer to the same moment. UTC is the modern reference timescale kept by atomic clocks and never observes daylight saving; GMT is the older term that also survives as the name of the zone the UK uses in winter. The trap is treating GMT as London time all year — in summer the UK is on British Summer Time, one hour ahead of UTC.
No. Every page is open, and nothing here requires signing in or installing anything. The site is a set of static pages that run entirely in your browser.
Yes — that is what the desk clock is for. Open a city's desk clock and press F11 on Windows or Linux, or Control-Command-F on a Mac, to go fullscreen. On a tablet, use "Add to Home Screen" so it opens without browser chrome. Disable sleep on whichever device hosts it, or the display will go dark mid-session.
Whichever one actually drives your day: the office you report to, the client you invoice, the market you watch, or the person you call most. If your work is local, your own city is the right answer and a single clock is enough.
Read the guides for longer explanations of UTC, daylight saving, and scheduling meetings across time zones.