World Clock
Last updated: 23 October 2026
See the current time in New York, London, Tokyo and nine more cities at a glance, next to your own local time — all from your device's clock.
Your local time
--:--:--
New York
--:--:--
Chicago
--:--:--
Los Angeles
--:--:--
London
--:--:--
Berlin
--:--:--
Dubai
--:--:--
Karachi
--:--:--
Mumbai
--:--:--
Singapore
--:--:--
Tokyo
--:--:--
Sydney
--:--:--
UTC
--:--:--
All of these times come from your own device's clock — nothing is fetched from a server. Daylight-saving changes are applied automatically by your browser's time zone rules, so if your device clock is set wrong, every clock on this page is off by the same amount.
Why this tool is private
Your numbers are crunched locally in this tab — nothing is sent to a server. No sign-up, no uploads, nothing to install.
How to use the World Clock
- Your own local time appears first, at the top — labelled with the time zone name your device reports, such as Asia/Karachi or Europe/London.
- Read the city cards for the current time in New York, Chicago, Los Angeles, London, Berlin, Dubai, Karachi, Mumbai, Singapore, Tokyo and Sydney, plus UTC.
- Each card also shows the day and date in that city and its current GMT offset, so you can tell immediately whether it is the same calendar day there.
- Every clock updates once a second from the same instant, so the page can stay open as a live reference while you plan a call, a deadline or a message.
- For converting a specific planned time between two zones — rather than the current time — use the Time Zone Converter linked in the related tools below.
About this World Clock
This world clock puts your own local time first, then live clocks for twelve zones — New York, Chicago, Los Angeles, London, Berlin, Dubai, Karachi, Mumbai, Singapore, Tokyo, Sydney and UTC. Each card shows the current time to the second, that city's day and date, and its GMT offset as it stands today, so daylight-saving changes are already reflected. All twelve clocks are rendered in your browser from your device clock and its built-in time zone rules — nothing is fetched as they tick — which makes the page a fast, private reference before you message, call or set a deadline across borders.
How this world clock gets its times
There is one current instant, and every clock on this page is that same instant expressed in a different place. Your browser takes the time from your device clock, then formats it separately for each city's IANA time zone — America/New_York, Europe/London, Asia/Tokyo and so on — using the zone database built into the browser itself. The GMT offset on each card is not typed in by hand: it is derived from those same rules for today's date, which is why Mumbai reads GMT+5:30 (India's half-hour offset) and why London's label changes across the year.
Because the zones are applied to a single shared 'now', the cards can never disagree with each other — if two cities look an hour further apart than you expected, a daylight-saving change in one of them is almost always the reason. Nothing is requested from a time server as the seconds tick: the page loaded once, and from then on your own device supplies everything. That makes the page fast and private, at the price of depending entirely on your device clock being right.
Worked example: a call that suits four cities
Suppose you are in Karachi and need a call with colleagues in Dubai, London and New York on a Friday in late October. Open this page mid-afternoon and you might read: Karachi 15:00 (GMT+5), Dubai 14:00 (GMT+4), London 11:00 (GMT+1, still on British Summer Time until the last Sunday of October), New York 06:00 (GMT−4, still on daylight time). One glance tells you the slot works for Karachi, Dubai and London but lands at 6 in the morning in New York — too early to be polite.
Sliding the call two hours later fixes it: 17:00 Karachi is 16:00 in Dubai, 13:00 in London and 08:00 in New York — the start of the working day there. Notice what the offsets did: the Karachi–London gap is four hours in late October but five hours in midwinter, because London drops back to GMT while Karachi never changes. Checking the cards for the actual day beats memorising fixed differences, which is precisely the mistake this page exists to prevent.
Offsets, daylight saving and the date line
Three habits make world times easy to read. First, never treat an offset difference as permanent: roughly half the zones here move their clocks twice a year, on different dates — the US and Europe change on different Sundays, and Sydney, in the southern hemisphere, moves in the opposite direction in the same weeks. Second, watch the half hours: Mumbai sits at GMT+5:30 all year, so calls with India land on the half hour from most other zones. Third, always read the date on the card, not just the time.
The date matters because the international date line runs through the Pacific: when it is Friday evening in Sydney it is still Friday morning in London but Thursday night in Los Angeles belongs to the small hours — sending a 'see you Friday' message across that spread without checking which Friday each side means is a classic scheduling bug. The cards show weekday and date for exactly this reason. UTC, the final card, is the escape hatch: quote a time in UTC and it means the same instant everywhere, with no summer-time trap.
Honest limitations
This page answers one question — what time is it now, there? — and deliberately does not do the neighbouring jobs. The city list is fixed: twelve major zones plus your own, with no way to add a city, search for one, or pin favourites. It also cannot convert a future or past time — 'what is 3 pm Tuesday in Berlin, in Tokyo?' needs the Time Zone Converter, which is built for a specific date and time in two zones. And it cannot set alarms or reminders for other zones.
Its accuracy is your device's accuracy. If your phone or laptop clock is manually set or has drifted, every clock here is wrong by that same amount — the differences between cities remain correct, but the absolute times do not, which is the one case where a search result is the better reference. Within that limit, the page is exactly what it claims: the current time in a dozen places, ticking once a second, worked out locally with nothing about you sent anywhere.
How it works
Your own local time sits at the top, labelled with your device's time zone, followed by live clocks for New York, Chicago, Los Angeles, London, Berlin, Dubai, Karachi, Mumbai, Singapore, Tokyo, Sydney and UTC — each showing the time to the second, the local date, and its current GMT offset. Every clock is rendered in your browser from your own device clock using the standard time zone rules built into it, so daylight saving is applied automatically and nothing about your location is sent anywhere. It is a quick-glance reference for calls, deadlines and colleagues in other countries.
Privacy note: this tool runs locally in your browser. Your input is not uploaded, stored in analytics, or placed in the page URL.
Frequently asked questions
Where do the times on this page come from?
Entirely from your own device. The page takes the current instant from your phone or computer clock and formats it for each city using your browser's built-in time zone database — the same (IANA) zone rules your operating system uses. Nothing is fetched from a time server when the clocks tick, which is why the page keeps working offline after it loads, and why every clock would be wrong by the same amount if your device clock is set wrong.
How is daylight saving time handled?
Automatically. Each city's offset is worked out for the date from the time zone rules built into your browser, so when London moves between GMT and British Summer Time, or New York between EST and EDT, the card shows the new offset on the day it changes — the GMT label on the card changes with it. You never need to add or subtract an hour yourself, and the date shown is the date in that city after the change.
Why does a city here show a different time from a search result?
Almost always, your device clock. Search results are served from time servers; this page renders from the clock in your device, and if that clock is a few minutes out — manual time setting, a drifted laptop, a delayed network sync — every city here shifts by exactly that same error, so the gap between cities stays right while all of them disagree with the search result. Switching your device to automatic date and time fixes it.
Is my location detected or tracked?
Your zone name is read from your browser's own settings — the page asks the browser what time zone the device is set to, which is how the 'Your local time' panel gets its label. Nothing about your location is detected by GPS, requested, sent or stored: the site never learns where you are, only which zone your device already believes it is in. If you have set your device to a different zone manually, that is the zone shown.
What is UTC, and why is it included?
UTC is Coordinated Universal Time, the reference every zone is measured against — the GMT offsets on the cards are hours ahead of or behind it. It never observes daylight saving, which makes it the safe common language for anything technical or international: server logs, flight and shipping schedules, and meeting invites between countries are often quoted in UTC precisely so nobody has to guess whose summer time applies. The UTC card shows that reference clock ticking alongside the cities.
Why do some cities show a different date?
Because the cities span the globe, they are not all on the same day. When it is early morning in Karachi it is still the previous evening in New York, while Sydney is into a day New York has not reached. Each card shows its weekday and date — 'Fri 23 Oct' — next to the time, so before you send a message or set a deadline you can see not just what time it is there, but which day.
Can I add my own cities to the list?
The grid is a fixed set of twelve used zones, chosen to cover main business centres across the Americas, Europe, the Middle East, Asia and Australia, plus UTC. You cannot add or remove cities on this page. If you need a time in a place that is not listed — or to convert a planned time, such as next Tuesday at 3 pm, rather than the current time — the Time Zone Converter on this site covers more zones.
Related tools
Date & Time Tools
Time Zone Converter
Convert a date and time between 12 world time zones using the Intl API and IANA zone names, with daylight-saving rules applied automatically.
Date & Time Tools
Countdown Timer
Set hours, minutes and seconds — or tap a preset — and count down with big clear digits, the time left in your tab title, and a beep at zero.
Date & Time Tools
Stopwatch
Time anything to the centisecond with lap splits you can copy in one click — timestamp-based, so it stays accurate even in a background tab.