About TimezoneSearch

Who runs this

TimezoneSearch is maintained by Chunyang, an independent developer. There is no company behind the site and no editorial staff. Chunyang builds the tool, writes the corridor notes and the articles, and reads mail at admin@timezonesearch.com.

There is no timekeeping credential to attach to that. This site is not a standards body, not an airline, and not a law firm. If a page and an official source disagree, the official source wins. Tell us anyway, so the page can be corrected.

Why the site exists

The converter came first. Comparing several cities in one browser tab, with daylight saving handled by the clock already on the machine, was more reliable than a spreadsheet of UTC offsets that went stale in March. You can still do that from the homepage: up to ten cities, a meeting grid, and a link you can send to someone else.

The city-pair pages are for a more specific question. "What time is it in London when New York sits down, and when can both sides actually meet?" A bare offset answers the first half. It does not say that London's afternoon is the only overlap, or that the gap shrinks for a few weeks because the United States changes clocks before Europe. Those notes are written by hand, for corridors people book. Pairs without a note are still usable as calculators. They are not offered as guides.

Where the times come from

Conversions use the IANA time zone database through the browser's Intl APIs. The site does not keep its own table of offsets. When a government changes a rule, the correction arrives with a browser or operating-system update of tzdata. Two up-to-date browsers agree. A hardcoded spreadsheet does not.

IANA publishes that database. This site does not, and it is not affiliated with IANA. The article on the IANA time zone database explains who maintains it and how the names work.

The meeting grid assumes a 9:00 to 18:00 local day. That is a planning default, not a description of any particular office. Factories, hospitals, retail, and a Ramadan schedule will not match it. The live clocks are current civil time. They are not a legal timestamp.

What gets maintained

The city list, the written corridor notes, and the articles are edited here. A note has to be updated when a rule change would make it wrong. Mexico ended daylight saving for most of the country in 2022. Turkey stayed on UTC+3. The UAE weekend moved to Saturday and Sunday in 2022. Those are the kind of facts that rot if nobody is watching them.

Browser time zone data is not something this site ships. If a brand-new political change is missing, update the browser before assuming the page has a bug in its arithmetic.

There is one maintainer, so a correction can sit for a few days. The contact page is the path. Include the city, the date, and what you expected to see.

Privacy, in short

There is no account. Your selected cities, theme, and language preference stay in your browser's local storage. They are not sent to a server or tied to an identity. The privacy policy covers analytics, weather, holidays, and reverse geocoding. Scheduling guides live on the articles page, and the corridors with a written note are listed first on city pairs.