SmartClock

Free · every IANA zone · automatic DST

World clock

The current time in the places you care about, on one glanceable board. Search any city; daylight saving is handled for you.

New York

GMT-4

--:--

London

GMT+1

--:--

Tokyo

GMT+9

--:--

Ask about these cities

Pro answers scheduling questions across your board: call windows, whether a date is a working day, and how an upcoming clock change will move a recurring meeting.

Example · “best time for a call with everyone”

Two windows work for all three. The later one is kinder to Tokyo, which is otherwise finishing at 11pm.

  • Best overall

    • New York 8:00 AM
    • London 1:00 PM
    • Tokyo 9:00 PM
  • Kinder to Tokyo

    • New York 7:00 AM
    • London 12:00 PM
    • Tokyo 8:00 PM
  • Tokyo: Outside working hours either way

Tokyo is giving up their evening, so rotate who takes the bad slot.

See what Pro adds

How do I find a meeting time across time zones?

Find your own working hours first, then scan which cities fall inside roughly 9 to 18 at the same moment. Two clocks more than about ten hours apart have no comfortable overlap at all, and the honest move then is to decide out loud who takes the bad slot rather than pretending 6am is fine for them. Rotating it between calls costs nothing and gets noticed.

On Pro you can skip the scanning and ask. The board answers questions about itself: the best windows for everyone, whether a particular date is a working day in each country, and how an upcoming clock change will move a meeting you already have in the calendar. Answers come back as the same instant written in every city’s own local time, which is the form you can paste straight into an invite.

Why does the time difference between two cities change?

Because a UTC offset is a schedule rather than a fact. London is +0 in January and +1 in July, New York shifts on a different weekend, and plenty of countries do not shift at all. For a few weeks each spring and autumn the gap between two cities is not what it was last month, which is exactly when recurring meetings quietly move by an hour and somebody misses one.

This board stores IANA zone names like Europe/London rather than offsets, and lets your browser’s own time zone database do the conversion. When a government changes its rules your browser updates and the board is correct without anything shipping here. The small label under each city shows that zone’s current offset, which is the number you want when proposing a time.

Is it the same day in both cities?

Often not, and it is the most common way a cross-zone invite goes wrong. Each card carries a sun or a moon and switches to a dark treatment at night, so a city that has already rolled past midnight into tomorrow is obvious at a glance rather than something you work out from the digits. When you propose a time, give the date in their terms as well as yours.

Can I add any city?

Any zone your browser knows, which is the full IANA list of several hundred, searchable by city or region. The free tier keeps four cities on the board at once, which covers most teams. Pro removes the cap and allows custom labels, so a row can read “Client, Berlin” rather than Europe/Berlin. The board is stored in your browser, so it is still there tomorrow, and no account is involved.

Frequently asked questions

Which cities and time zones are supported?
All of them — the list comes from your browser's own IANA time-zone database (the same tz database operating systems use), so every city zone like America/New_York or Asia/Singapore is searchable and always up to date.
Does it handle daylight saving time?
Yes, automatically. Times are computed from the IANA zone rules, which encode every region's DST transitions — including the awkward half-hour and 45-minute offsets.
How many clocks can I add?
Four on the free board. Pro removes the cap and lets you rename each clock — useful for teams ("Design — Lisbon") rather than raw city names.
Is my city list stored anywhere?
Only in your browser. Nothing is uploaded.