Free time-zone tools for distributed teams
Live world clocks, time-zone converters, meeting schedulers, holidays, and the rest. Built for people who run standups across San Francisco, London, Bengaluru, and Sydney in the same day.
Side-by-side conversion across 3+ zones with shareable URLs.
Open tool →Find the best overlap across any number of teammates.
Open tool →Years, months, days, hours, dog years, milestone birthdays.
Open tool →Count calendar days, weekdays, or business days.
Open tool →Skip weekends and per-country public holidays.
Open tool →25-minute focus blocks, configurable, distraction-free.
Open tool →A single clock tells you what time it is. A world clock tells you what time it is for everyone else at the same instant, and that second question is the one that actually shapes a working day. The moment your colleagues, family, or customers are spread across more than one time zone, the useful unit stops being "the time" and becomes "the time, everywhere I care about, right now." The clock above is built around that comparison: instead of mentally adding and subtracting offsets, you keep a row of live clocks for the exact cities in your life and read all of them in one glance. It is the difference between calculating "London is eight hours ahead of San Francisco, so if it is 4pm here it must be midnight there" and simply seeing that London already says 00:03 and is well outside working hours.
The reason a world clock is more than a lookup table is that time-zone offsets move. Many countries, concentrated in Europe and North America, observe daylight saving time, and the dates on which clocks spring forward and fall back differ by country and even by year. For several weeks each spring and autumn the gap between, say, New York and London is not the usual five hours because the two regions change their clocks on different weekends. Hard-coding "+5" somewhere will be wrong twice a year. This clock avoids that trap by driving every city from its IANA time-zone database entry, the same authoritative dataset operating systems use, which encodes each region's historical and upcoming rules. When a country shifts its clocks, abolishes daylight saving, or redraws a zone boundary, the displayed time follows automatically. That is also why you should trust a live clock over a remembered offset: the live clock already knows about the edge cases you forgot.
Each clock carries a ring that signals whether the city is currently inside ordinary working hours. The point is not precision, it is triage. When you are trying to schedule a quick call or decide whether a message can wait, you do not need to know that it is 14:37 in Bengaluru, you need to know that Bengaluru is awake and working while San Francisco is still asleep. Glancing down a column of clocks and seeing which ones are lit tells you instantly where the overlap is and where it isn't. For anything more involved than a single call, the meeting scheduler extends this idea into a full overlap heatmap across every participant's working hours and each country's public holidays.
The cities you choose are remembered in your browser, so the clock you build is yours and waits for you on every visit. You can add cities, drag them into the order that matches how you think about your day, and remove the ones that stop being relevant. When you want to hand the same view to someone else, the share link reproduces your exact set of cities, and the embed option drops a live, theme-aware version onto your own website. Distributed teams often pin an embedded world clock to a status or handbook page so anyone can see at a glance when each office is online, and frequent travellers keep home, current, and destination clocks side by side to stay oriented. When you need to convert a specific time rather than watch the current one, the time zone converter turns "3pm Friday in Berlin" into every other city's local time.
Use the add-city box to search by city name and pick from the list. Each city you add gets its own live clock, and your selection is saved in your browser so the same set is waiting for you next time. You can reorder the clocks or remove any you no longer need.
Yes. Each city's clock is driven by its IANA time zone, which carries that region's daylight saving rules, so the offset shifts on the correct date without you doing anything. A city that springs forward in March or falls back in November updates the moment its local rule takes effect.
The ring is a quick visual cue for whether a city is currently inside typical working hours, roughly 9 to 5 local time. When you are coordinating a call across continents it lets you see at a glance who is awake and at their desk and who would be answering at midnight, which is the whole point of looking at several clocks at once.
Yes. The embed option generates a small iframe snippet you can paste into any page. The embedded clock keeps ticking live, respects your visitor's light or dark theme, and links back here. It is a simple way to show your team's or your audience's local times on a contact, careers, or status page.
The clocks update every second from your device's own system clock, which on most computers and phones is synchronised to network time servers. As long as your device's clock is correct, every city shown will be correct too, because the tool only applies each zone's offset to that single reference time.