See the live local time in cities across the globe. Add the places you care about, and VClock keeps every clock accurate — including daylight saving — automatically.
Remote teams, family abroad, international markets and global sports fixtures all run into the same problem: "what time is it there right now?" A world clock answers that instantly, and more importantly it answers it correctly — including the daylight saving shifts that catch people out twice a year.
VClock reads time zone rules from the IANA database built into your browser, the same source operating systems use. That means Phoenix stays on Mountain Standard Time all year while Denver switches, London and New York change DST on different weekends, and India stays 30 minutes offset from its neighbours — all without you configuring anything.
| Zone | Standard | Daylight | Example cities |
|---|---|---|---|
| Eastern | UTC−5 | UTC−4 | New York, Miami, Atlanta, Boston |
| Central | UTC−6 | UTC−5 | Chicago, Dallas, Houston, New Orleans |
| Mountain | UTC−7 | UTC−6 | Denver, Salt Lake City, Albuquerque |
| Mountain (no DST) | UTC−7 | UTC−7 | Phoenix, most of Arizona |
| Pacific | UTC−8 | UTC−7 | Los Angeles, Seattle, San Francisco |
| Alaska | UTC−9 | UTC−8 | Anchorage, Juneau |
| Hawaii–Aleutian | UTC−10 | UTC−10 | Honolulu (no DST) |
In the United States, daylight saving currently begins on the second Sunday in March and ends on the first Sunday in November. Hawaii and most of Arizona do not observe it at all, which is why a call that works in July may not work in January.
These are the conversions that come up most often for American teams and families. Offsets shown are from US Eastern Time during the northern-hemisphere summer, when both regions are on daylight time; check the live cards above before scheduling anything that matters.
| City | Ahead of New York by | Practical overlap with a US workday |
|---|---|---|
| London | 5 hours | Comfortable — 9 AM ET is 2 PM in London |
| Berlin, Paris, Madrid | 6 hours | Morning ET calls only; afternoons are evening there |
| Dubai | 8 hours | Early ET mornings, late afternoon in Dubai |
| Mumbai, Delhi | 9 hours 30 minutes | Narrow — 8 AM ET is 5:30 PM in India |
| Dhaka | 10 hours | Narrow — best handled before 9 AM ET |
| Singapore, Manila | 12 hours | Essentially none; pick early morning or late evening |
| Tokyo | 13 hours | Evening ET meets next morning in Japan |
| Sydney | 14–16 hours | Late afternoon ET meets next-morning Sydney |
| Los Angeles | 3 hours behind | Wide — noon ET is 9 AM on the West Coast |
Two of these deserve a warning. Australia's offset swings by two hours across the year because its daylight saving runs opposite to the northern hemisphere's, so a recurring call with Sydney needs rechecking every April and October. India's half-hour offset means mental arithmetic goes wrong more often than for any other major destination — read it off the card rather than calculating it.
The practical trick with a spread-out team is to stop hunting for a time that suits everyone and instead decide which meetings genuinely need to be live. Anything that is a status update, a handoff or a document review works better written down, which frees the shared hours for the conversations that actually benefit from being synchronous.
When you do need everyone at once, add every participant's city to the clock above and read across the cards for the hours that fall inside a reasonable working day on all of them. If no such hour exists — which is normal once a team spans more than about ten hours of longitude — rotate the inconvenience rather than fixing it on one region permanently. Pair the world clock with a countdown timer to keep those rare live meetings to their agreed length, and with the alarm clock so an unusually early call is not something you have to remember.
The world is divided into zones offset from Coordinated Universal Time (UTC), the modern successor to Greenwich Mean Time. In theory each zone is one hour wide; in practice borders follow political lines, and several regions use 30- or 45-minute offsets — India is UTC+5:30, Nepal UTC+5:45, and parts of Australia UTC+9:30. Add seasonal daylight saving, which about a third of the world observes on its own schedule, and manual conversion becomes genuinely error-prone. That is exactly the arithmetic a world clock removes.
Yes. Times are calculated from your device clock using the official IANA time zone database built into your browser, which includes current daylight saving rules for every region.
Yes. Because it uses your browser's time zone engine, DST transitions are applied automatically — you never need to adjust anything in March or November.
Yes. Choose a city from the dropdown and press Add. Your list is saved in your browser, so it is still there next time you visit.
As many as you like. The grid reflows to fit your screen, and each card updates every second.
Time zones can be more than 24 hours apart in practice, so when it is Tuesday morning in New York it is already Tuesday evening in Tokyo. Each card shows its own local date to make this obvious.
Very. Add every participant's city and you can see at a glance which hours fall inside everyone's working day, without converting anything by hand.
Use the VClock alarm clock so you never miss an early call again.
Open the Alarm Clock