How accurate are the times shown?

The times are taken from your device's system clock and formatted using the browser's Intl.DateTimeFormat API, which handles DST automatically. Accuracy depends on your device clock — typically within 1 second of real time.

Does this use my location or any server data?

No. All time formatting runs locally in your browser using the JavaScript Intl API. No location data or requests are sent to any server.

Why does my city show a different offset than expected?

If a region is currently observing daylight saving time, the offset shown will reflect that. For example, New York is UTC−5 in winter (EST) and UTC−4 in summer (EDT).

Can I save my clock layout?

Your selected clocks are saved in localStorage and restored when you revisit the page.

Why do some zones use half-hour or 45-minute offsets?

Time zones were historically set to align with local solar noon. Countries like India (UTC+5:30), Iran (UTC+3:30) and Nepal (UTC+5:45) chose offsets that best matched their geography rather than rounding to the nearest hour.

What does UTC stand for?

UTC stands for Coordinated Universal Time. It is the global time standard used as the basis for all civil time. UTC does not observe daylight saving time and never changes — all other time zones are defined as offsets from UTC.

🌍

World Clock

See the current time in multiple cities and time zones simultaneously. Add any city, watch times update live. Free, browser-based, no signup.

🕐 Time & Date Tools Free Browser-based

Tool

Add a city / time zone

Why Use a World Clock?

Coordinating across time zones is one of the most common challenges for remote teams, international travellers and online event planners. A world clock lets you instantly compare local times without mental arithmetic or zone conversion errors.

Time Zone Reference

City	Time Zone	UTC Offset
New York	America/New_York	UTC−5 / UTC−4 DST
London	Europe/London	UTC+0 / UTC+1 BST
Paris	Europe/Paris	UTC+1 / UTC+2 CEST
Dubai	Asia/Dubai	UTC+4
Mumbai	Asia/Kolkata	UTC+5:30
Tokyo	Asia/Tokyo	UTC+9
Sydney	Australia/Sydney	UTC+10 / UTC+11 AEDT
Los Angeles	America/Los_Angeles	UTC−8 / UTC−7 PDT

Daylight Saving Time

Offsets automatically adjust for daylight saving time (DST) using the Intl.DateTimeFormat browser API, which reflects the current real-world offset for every zone.

Tips for Scheduling Across Time Zones

Watch for midnight crossings — 10 PM on Monday in New York is 3 AM on Tuesday in London. Always note the date, not just the time.
Avoid DST transition days — clocks change at 2 AM, creating a 23- or 25-hour day. Meetings scheduled around that hour can shift by an hour unexpectedly.
Use UTC for server timestamps and APIs — store all timestamps in UTC and convert to local time only for display. Never store local times in a database.
Check half-hour and 45-minute offsets — India (UTC+5:30), Iran (UTC+3:30) and Nepal (UTC+5:45) do not fall on whole-hour boundaries.
Communicate in UTC when possible — for global teams, sending "15:00 UTC" removes all ambiguity about which side of a DST boundary a meeting falls on.

Zones That Do Not Observe DST

Not all countries change their clocks. China, Japan, India, most of Africa, and several other countries keep a fixed UTC offset year-round. This means the offset between a DST-observing region (like New York or London) and a non-DST region (like Mumbai or Tokyo) changes by one hour twice a year. The world clock above reflects real-time offsets automatically — no manual adjustment needed.