Written by Sarah Mitchell · Reviewed by Alex Chen · July 30, 2026
View current times for cities around the world with automatic refresh and DST indicators.
The TL3 World Clock shows the current time in major cities across the globe on one page. Each row ticks every second and reports the local time, date, UTC offset, and whether Daylight Saving Time is in effect for that zone. When it is 2:00 PM in New York, the list shows the simultaneous moment in London, Tokyo, Sydney, and a dozen other cities — no mental math required. Everything is computed in your browser with the Intl.DateTimeFormat API, so the clocks need no network connection to stay accurate.
local time − UTC in minutes and formatted as UTC+HH:MM.Asia/Kolkata, fixed offsets like Etc/GMT-8, and regional entries all work.A JavaScript timer refreshes the display every second. Each row formats the current instant through Intl.DateTimeFormat with that row's timezone, so the math is done by the browser's own timezone database — nothing is sent to a server.
That is daylight saving. The displayed offset is the current one, including DST when active. London, Paris, Berlin, and New York all shift by an hour across the year; the DST status column tells you which state each zone is in right now.
Any IANA timezone the browser knows, including half- and quarter-hour offsets like Asia/Kolkata (UTC+05:30) and Asia/Kathmandu (UTC+05:45). The dropdown is generated from your browser's own timezone list.
No. Custom zones live only for the current page session; each visit starts from the default city list. Re-add anything you need with the dropdown — it takes a couple of clicks.
Time zones are political artifacts, not physical facts. Governments move their clocks for economic or diplomatic reasons, and the catalogue of changes is maintained by volunteers in the IANA timezone database that every operating system ships. That is why the same city can report different offsets across eras: Samoa skipped an entire calendar day in 2011 by moving straight from December 29 to December 31, and countries have split, merged, and reversed their offsets over the decades. When your browser updates, the zone definitions update with it, so historical dates shown by other tools may disagree with today's rules.
Offsets are rarely whole hours. India runs at UTC+5:30, Nepal at UTC+5:45, and parts of Australia at UTC+9:30 — the half-hour standard descends from the era when railway companies negotiated compromises between solar noon in neighboring towns. Because the browser's own timezone engine computes every entry, all of these oddities are handled automatically: you never need to remember which quarter-hour zone to pick.
When scheduling a meeting between coworkers in different cities, read the list twice — once for each side's current DST state, because the gap between two zones can be zero, one, or two hours depending on whether one region has already sprung forward. The dangerous window is the transition night: in zones that observe daylight saving, the local time 02:30 may occur twice in autumn or not at all in spring, so an appointment typed as a bare wall-clock time becomes ambiguous. The robust habit is to record the moment as an instant — the timestamp your computer stores — and let each participant's calendar render it in their own zone. This tool shows the present, not the future: it has no calendar logic, so use it to double-check a time, not to plan one.
Your local zone is always present in the default list, with its offset computed live from the device clock. That makes the page a handy sanity check for a misconfigured machine: if the entry for your city disagrees with the time on your watch or phone, the problem is the computer's timezone setting, not the tool. Because every entry derives from the same clock, all columns shift together when the clock is wrong — a stuck date or a large offset gap across the whole list is the signature of a device that lost its network time sync.