Two clocks can both be right and still disagree. One says 9:00 and the other says 14:00 because they are labeling the same moment in two places. A world clock is a way to see those labels side by side. A time zone converter, in the strict sense, answers a slightly different question: if it is this local time in one place, what local time is that same moment somewhere else? Clockbeam splits those jobs. The world clock shows the current local time in the cities you add. The meeting planner takes a minute you choose and shows that minute in each selected city, along with the overlap of their working hours.
You do not need a table of every city to use either page. You do need a clear idea of what an offset is, because the number under a city is the whole story of “how far ahead” or “how far behind.”
UTC is the reference, not a place you live
Coordinated Universal Time, UTC, is the official, internationally agreed standard for world time. NIST describes it that way, and NIST’s own UTC(NIST) is a real-time version kept with atomic clocks for the United States. The time of day expressed by UTC is the time at the prime meridian, near Greenwich. Local time zones are then described as an offset from UTC.
NIST’s explanation uses the United States as the example. Eastern standard time is five hours behind UTC, written UTC−5. Coordinated Universal Time is not adjusted during daylight saving time, so eastern daylight time is four hours behind UTC, UTC−4. The same pattern runs across the continental zones: the daylight offset is one hour ahead of the standard offset. Central standard time is UTC−6 and central daylight time is UTC−5. Mountain standard time is UTC−7 and mountain daylight time is UTC−6. Pacific standard time is UTC−8 and pacific daylight time is UTC−7. Alaska standard time is UTC−9 and Alaska daylight time is UTC−8. Hawaii standard time is UTC−10. Those are the offsets NIST lists for local time in the United States, not a promise that every community inside a colored band on a map uses them.
The switch to daylight saving does not move UTC. It moves the local offset. If a colleague in London and a colleague in New York both “spring forward,” the difference between them may stay the same or it may change, depending on whether their transition days match. You cannot memorize “New York is five hours behind London” and expect it in July. You look up the offset for that date.
Daylight saving is a rule, and the rule is not universal
NIST’s local-time FAQ is blunt about who decides. Time zones and daylight saving time in the United States are overseen by the Department of Transportation, not by NIST. Most of the country follows daylight saving time. Hawaii, American Samoa, Guam, Puerto Rico, the Virgin Islands, and most of Arizona do not. Inside Arizona, the Navajo Nation does observe it. The dates have changed before. NIST notes changes in 1986 and 2007 that lengthened the daylight period. A chart you printed years ago can be wrong even if the city has not moved.
The data that software uses for this is the Time Zone Database maintained for IANA, often called tz or zoneinfo. IANA describes it as code and data for the history of local time at many representative locations. It is updated when political bodies change boundaries, UTC offsets, or daylight-saving rules. Your phone and your laptop get those updates from their operating systems. Clockbeam does not ship a second copy of the world’s offsets. The world clock asks your browser for the current offset of an IANA time zone, at the current moment. When the zone’s rule moves the clocks, the offset on the page moves with it, because the browser’s data moved.
That also means a brand-new law can be missing until the device updates. If a government changes a rule and your operating system has not caught up, the page will be as wrong as the laptop clock. There is no separate Clockbeam feed to correct it.
What the world clock shows
Your device’s own zone is already listed. Search for a city and add it. Each row shows the local time, the date, and the current UTC offset. The date matters more than people expect. A city can already be on tomorrow while you are still on today. The offset explains the gap. The clock face, or the digits, show what a person standing in that city would read right now.
You can keep up to eight added cities. The page says so when you reach the limit. Remove a city with its remove button. The list is stored in this browser. Clearing site data removes it. The row for this device is always shown, and it is not one of the eight.
There is no page for every city, and there should not be. A directory of thousands of near-duplicate “current time in X” URLs would not tell you more than the search box. You search, you add, you read. If you need the same list tomorrow, it is still in this browser.
The world clock is the current moment only. It does not hold a meeting next Tuesday. It does not convert “3:00 p.m. in Chicago on the first Monday in November” by itself. For that, use the meeting planner, which takes a date and a minute in the first city and shows the corresponding local time in the others. The planner also shows the band of the day where the cities’ working hours overlap. The world clock is the right tool when someone asks “what time is it there?” The planner is the right tool when someone asks “what time should we meet?”
A conversion you can do from the offset
Suppose the world clock shows your city at UTC−4 and another city at UTC+1. The other city is five hours ahead. Add five hours to your local time and you have theirs, for this moment. If the clocks say 09:10 and 14:10, the arithmetic agrees. If it does not, you are probably comparing a standard-time memory with a daylight-time display. Trust the offsets on the page for today, not a difference you learned in winter.
Crossing midnight is ordinary. If it is 22:00 where you are and the other city is 8 hours ahead, it is 06:00 there on the next date. The world clock prints the date on the row so you do not have to notice that yourself. When you write the time down for someone else, write the date too. “9 a.m.” without a date is how flights get missed in one direction.
Naming the zone beats naming the abbreviation when you can. “EST” and “EDT” are different offsets, and some abbreviations are reused in other countries. The label on Clockbeam follows the zone you added. When you copy a time into a message, include the city or the offset you see, not a three-letter guess.
What this clock is not
It is not an atomic clock. NIST’s UTC(NIST) is a laboratory time scale. Clockbeam follows the clock in your device, and the zone database in your browser. If the laptop is two minutes slow, every row is two minutes slow together. The differences between cities can still be right when the absolute time is slightly off, because the offsets are applied to the same device clock. For almost every human schedule, that is enough. For a measurement that has to match UTC(NIST), it is not the instrument.
It does not know office hours, holidays, or whether a city is in a meeting. A sensible local time can still be a bad time to call. The meeting planner’s working-hours band is a default of 9:00 to 17:00 that you can change. It is not a statement about the law or about a particular office.
It will not notify you when a city crosses into daylight saving time. The offset changes on the row when the moment arrives and the browser knows the rule. If you are planning across that night, do not assume today’s offset. Open the planner and look at the date you mean.
A short routine
Add the cities you actually call. Read the offset, not only the hour, the first few times, until the gap is familiar. When the season changes, look again instead of trusting the gap you memorized. When the question becomes a future minute rather than “right now,” switch to the meeting planner and set the date. Write the result with the city name and the date. That is the whole skill. The page is there so you do not have to keep the offset table in your head.
