urlcv

Time Zone Overlap

Pick two cities and instantly see which working hours overlap — fully DST-aware.

Timezone Remote Scheduling Global

Speed up your recruitment workflow

URLCV automates CV parsing, candidate scoring, and shortlist generation — so you can place more candidates, faster.

Start free trial →

Quick pairs

Set your team's working hours. Both cities will use the same window.

to
⚠ End time must be after start time

How it works

  1. 1

    Search for two cities

    Type any city name or country into the search boxes. Results update as you type — over 85 cities are included, spanning every major timezone.

  2. 2

    See the overlap chart instantly

    A colour-coded 24-hour timeline appears immediately. Blue shows when only your first city is working, green shows when only the second city is working, and the primary colour highlights the overlap window.

  3. 3

    Change the date to test DST transitions

    Use the date picker to check overlap on a specific day — useful for planning calls around daylight saving time changes. The chart recalculates immediately with the correct summer or winter offset.

  4. 4

    Adjust working hours if needed

    Not everyone works 9–5. Open Advanced options to set custom start and end times — for example, 08:00–16:00 for early-bird teams or 10:00–18:00 for late-start offices.

Real-world examples

London ↔ New York (typical agency pair)

In summer (BST/EDT): London is UTC+1 and New York is UTC−4 — a 5-hour gap. London's 14:00–17:00 aligns with New York's 09:00–12:00, giving 3 hours of overlap. In winter (GMT/EST): London is UTC+0 and New York UTC−5, the same 5-hour gap applies. Because both cities observe summer time, the overlap window stays at 3 hours year-round.

London ↔ Singapore (remote engineering team)

Singapore is UTC+8 and does not observe DST. In summer, London (BST, UTC+1) is 7 hours behind Singapore — meaning London's 9am is Singapore's 4pm, and London's 5pm is Singapore's midnight. The overlap is just 1 hour (London 16:00–17:00 = Singapore 23:00–00:00). For distributed teams in these cities, staggered hours or an async-first culture is usually the practical answer.

Frequently asked questions

Does the tool account for daylight saving time?

Yes — fully. The tool uses the browser's built-in Intl.DateTimeFormat API with IANA timezone identifiers, which is automatically updated by your browser and operating system. This means it handles every country's DST rules correctly, including unusual cases like Israel's irregular DST dates and Morocco's reversed clock change.

Can I use different working hours for each city?

The current version uses the same working-hours window for both cities — the assumption being you want to find time when both teams are available simultaneously. Open "Advanced options" to change the window from the default 09:00–17:00 to whatever suits your team. A future version may allow independent hours per city.

Why does London ↔ Sydney show no overlap?

Sydney (AEDT in summer) is UTC+11 — 11 hours ahead of London (GMT). Sydney's 09:00 is London's 22:00 the previous evening, and Sydney's 17:00 is London's 06:00. There's no overlap within standard 9–5 hours. For these pairs, teams typically use an early call from the Sydney side or a late call from the London side, or adopt async communication tools as the primary workflow.

How are half-hour timezone offsets handled?

Some countries use non-integer UTC offsets: India is UTC+5:30, Nepal is UTC+5:45, and Sri Lanka is UTC+5:30. The tool handles these correctly — when computing City B's local time for each hour on the chart, it uses the precise offset in minutes, so the displayed time for Mumbai will correctly show 14:30 when London is at 09:00.

Does any data leave my device?

No. The entire tool runs in your browser using JavaScript. No city selections, dates, or results are sent to any server. The timezone calculations are performed locally using the Intl API built into every modern browser.