World Clock
Check world times
Check world times Runs locally in your browser
Times update every second and use your browser's timezone database, so daylight saving is applied automatically. Click a city to hide or show it.
Your local time
--:--:--
·
UTC
--:--:--
·
New York
--:--:--
·
London
--:--:--
·
Paris
--:--:--
·
Berlin
--:--:--
·
Dubai
--:--:--
·
Beijing
--:--:--
·
Tokyo
--:--:--
·
Singapore
--:--:--
·
Sydney
--:--:--
·
Los Angeles
--:--:--
·
Sao Paulo
--:--:--
·
About the
The World Clock shows the current time in your own timezone alongside UTC, New York, London and Tokyo, computed from your device clock and rendered in the target timezone. The point of having UTC in the list is that it is the unambiguous reference: when you arrange a meeting across three cities, agreeing on a UTC time and converting from there avoids the confusion of everyone naming their own local time. Daylight saving shifts are applied automatically, because the conversion uses the browser's timezone database rather than a fixed offset.
Where people use the
- Scheduling a call across Europe, North America and Asia.
- Checking whether it is already the next day somewhere before sending a message.
- Converting a UTC timestamp from a log into your local time.
- Working out whether a market or office abroad is open right now.
How to use the
- 1
Open the tool
It reads your device clock and updates every second, so make sure your own system time is correct first.
- 2
Read the cities you need
Your local time, UTC, New York, London, Paris, Berlin, Dubai, Beijing, Tokyo, Singapore, Sydney, Los Angeles and Sao Paulo are shown at once, each with its date and UTC offset.
- 3
Show or hide cities
Click any city button to hide it, and click again to bring it back. Useful when you only care about three of them.
- 4
Use UTC as the reference
When agreeing a time with people in several timezones, write down the UTC value and let everyone convert from that.
- 5
Re-read it when planning ahead
The clock shows the current time. For a future date, work out the offset from today and check it again closer to the day, because daylight saving may have shifted in between.
Tips and best practices
- Always state times as UTC in writing; it removes every ambiguity.
- Re-check a few days before a scheduled event if it crosses a daylight saving change.
- Compare dates, not just hours, when the cities are far apart.
Frequently asked questions
How is the time calculated?
From your device clock, converted using the browser's built-in timezone database. That database includes historical and scheduled daylight saving rules, so the offsets are correct for the date in question.
Why is the time wrong?
Because your own device clock is wrong. The tool has no independent time source; if your laptop is five minutes fast, every city shown will be five minutes fast.
Does it handle daylight saving automatically?
Yes. New York and London move between standard and daylight time on their own schedules, and the conversion reflects that. This is exactly why a fixed offset such as UTC-5 is unreliable for future dates.
Why is Tokyo sometimes a day ahead?
Because when it is Monday evening in London it is already Tuesday morning in Tokyo. Compare the date as well as the hour when scheduling across the Pacific.
Can I see a city that is not listed?
Not here. The five shown cover the most commonly needed reference points; anything else needs a converter that accepts an arbitrary timezone.