Live same-instant twin clocks and a meeting overlap map - so a wall time never pretends to be a shared schedule by itself.
IANA zones with DST for the date you pick. Not elapsed-time math or a free/busy calendar.
By Ahmet C. Toplutaş·Site owner & editor · Time & calendar tools
Last updated May 21, 2026 · Reviewed May 21, 2026 · Planning estimates only - not tax, medical, or investment advice
01
“3:00 PM” only means something when you name the city. A wall clock is a local label on a calendar - Tuesday afternoon in New York, Wednesday morning in Tokyo. The same instant is one point on the timeline that every zone formats differently. Conversion does not make both places “feel” 3 PM; it answers “when their clocks show X, what do ours show?”
The legacy failure mode is pasting a clock face into a calendar invite without the zone, then discovering half the attendees joined twelve hours off. This page’s framing is wall clock ≠ same instant - show both cities’ labels for one shared moment, plus UTC as the anchor.
Decision framing: “Which city’s wall time am I typing, and which city’s wall time do I need on the invite?” - not “add or subtract five hours from EST forever.”
02
Stickers like “EST = UTC−5” or “CET = UTC+1” fail twice a year in many regions, and they fail permanently when governments change rules. IANA identifiers such as America/New_York or Europe/London carry seasonal daylight-saving transitions and historical corrections. The browser’s timezone database applies those rules for the date you pick.
Offsets shown in the panel are for that instant on that date - not a permanent property of the city. If you need a durable written record, prefer the IANA name (or UTC) over a three-letter abbreviation alone.
03
The twin-clock board is the unique readout: From wall, UTC anchor, and To wall for one moment. When the civil date rolls - “Tuesday in From, Wednesday in To” - the board flags it so the invite does not silently land on the wrong day.
UTC in the middle is the coordination habit global teams already use: store or quote the instant once, then display local walls for humans. Swap zones to reverse the story without retyping the clock.
04
Converting 2 AM correctly still books a terrible call. The meeting overlap map samples each hour of the From city’s calendar day and marks cells where both cities sit inside a default 09:00–17:00 local window. Those cells are the realistic live-meeting corridor for that pair - not a calendar of who is free.
Your selected hour is ringed on the map. If it sits outside the both-work corridor, the conversion is still correct - the etiquette is not. Tough pairs (Tokyo ↔ San Francisco) often show a thin or empty corridor; that is the product teaching you to async, not to force a “fair” midpoint that hurts both sides.
Work hours here are a planning default (9–5 local), not company policy. Shift culture, on-call rotations, and religious calendars need human judgment on top of the map.
05
The same wall clock on March 10 versus November 10 can sit on different UTC offsets when one city has sprung forward and the other has not - or when only one observes DST at all. Always convert against the actual meeting date, not “a typical Tuesday.”
Spring-forward gaps can make a local hour not exist; fall-back repeats can make an hour ambiguous. The panel uses the browser IANA database for a best-effort instant. For airline tickets, exchange cutoffs, or legal deadlines, confirm against the organizer’s official zone statement.
06
Example A · NYC → London, 09:00. Preset: NYC → London.
A New York morning usually lands in London afternoon (exact hour depends on whether either side is on daylight time). Open the overlap map: several green-both cells appear mid-morning Eastern / mid-afternoon UK - the classic transatlantic live window.
Example B · Tokyo → SF, 18:00. Preset: Tokyo → SF.
Early evening in Tokyo is morning (or still night) on the US West Coast depending on the season. The overlap map often shows a thin corridor - proof that a “correct” conversion can still be a bad live meeting. Prefer async updates or alternate who owns the early slot.
Example C · Istanbul → Berlin, 14:00. Preset: Istanbul → Berlin.
Near-neighbor zones often share the afternoon. Watch the twin clocks for a one- or two-hour delta and a wide overlap corridor - useful for confirming you are not accidentally using a summer-only mental offset in winter.
Example D · Sydney → UTC, 10:00. Preset: Sydney → UTC. Anchor the morning stand-up to UTC on the twin-clock middle column, then share city walls for humans. When the Sydney date and UTC date disagree, the invite subject should include the UTC date explicitly.
07
America/New_York is the durable ID.08
09
Stop here when the question is “what does this wall time say in another city?” Hand off when you need duration, remaining time, business-day length, or calendar-day spans.
10
A wall clock is what the local calendar shows (Tuesday 3:00 PM in New York). The same instant is one moment on the timeline that every city labels differently. Conversion maps one city’s wall time to another city’s wall time for that shared instant - it does not mean both places “feel” the same hour.
Labels like EST or CET hide daylight saving and political rule changes. IANA IDs such as America/New_York carry the historical and seasonal rules so the same calendar date can be UTC−5 in winter and UTC−4 in summer. Fixed offsets break around DST transitions.
It samples each hour of the From city’s calendar day and marks when both cities are inside a default 09:00–17:00 local work window. Green-both cells are the realistic live-meeting corridor. It is a planning aid, not a guarantee that anyone is free.
Yes, via the browser’s IANA timezone database for the selected date. Pick the real meeting date - converting “3 PM” in March can differ from “3 PM” in November for the same city pair.
When the offset between zones crosses midnight, the civil date changes even though it is the same instant. The twin-clock board shows both weekdays and dates so the rollover is visible before you send a calendar invite.
No. This page converts a wall time between zones. Use the time-difference calculator for elapsed duration between two timestamps, and the countdown calculator for remaining time to an event.
No. Date, time, and zones hydrate from the URL on load, but the address bar updates only when you use Share or Copy. That keeps live editing calm and share links intentional.
LIVE ZONE CONVERT
Wall ≠ instant ↓Route presets
Updates live. Wall clock ≠ same instant. IANA zones carry DST for the selected date.
In London
Sun 14:00
2026-08-16 · UTC+01:00 · Δ +5h from From
SAME-INSTANT TWIN CLOCKS · WALL ≠ INSTANT
FROM WALL
09:00
Sun 2026-08-16
US Eastern · UTC-04:00
SHARED INSTANT (UTC)
13:00
Sun 2026-08-16
Anchor · UTC+00:00
TO WALL
14:00
Sun 2026-08-16
London · UTC+01:00
One moment, three labels. If the To date differs, the invite must name the city - not only the clock face.
MEETING OVERLAP MAP · 09–17 LOCAL BOTH SIDES
3 hours today where both cities sit in a default 9–5 local window · your selected hour is inside that corridor.
00
→05
01
→06
02
→07
03
→08
04
→09
05
→10
06
→11
07
→12
08
→13
09
→14
10
→15
11
→16
12
→17
13
→18
14
→19
15
→20
16
→21
17
→22
18
→23
19
→00
20
→01
21
→02
22
→03
23
→04
Each cell is an hour on the From city’s calendar day. Top = From local hour; bottom = To local hour. Highlighted cells = both in 09–17. Not a free/busy calendar.
Copy the link to save or share your results.