Skip to content
Shift Overlap

About Shift Overlap

Why Shift Overlap exists, how it stays correct through daylight-saving changes, and what it deliberately refuses to do: no accounts, no tracking, no server.

The problem it solves

Time zone converters are everywhere, and they all answer the same question: what time is it there. Nobody scheduling a meeting across four countries needs that. They need to know which hours of their own day the whole team is at work — and then they need to send that answer to five other people.

Why it takes a date

Because the answer genuinely changes. In most years the United States and the European Union change clocks about two weeks apart in March and about a week apart in late October or early November, and the southern hemisphere shifts in the opposite direction. Any tool that computes overlap by subtracting one local clock from another is wrong during exactly those weeks.

Shift Overlap converts each person's hours into absolute time, finds the intersection, and only then works out what that means on each person's clock. It also handles the zones that no whole-hour assumption survives: India at +05:30, Nepal at +05:45, the Chatham Islands at +12:45.

What it deliberately does not do

  • No account, no email, no personal data — there is nothing to sign up to.
  • No server doing the maths. Every calculation runs in your browser, and your cities are never transmitted anywhere.
  • No AI model guessing at your schedule. The answer is arithmetic, and it is exact.
  • No invented working hours. If there is no overlap, the tool says so rather than suggesting a window that does not exist.

How it is paid for

A small amount of advertising. There is no paid tier and no plan to add one — a tool used once every few weeks should not have a checkout page. See the privacy page for what that means in practice.