About besttimefor.io

besttimefor.io is a free meeting planner for teams that work across time zones. Drop your team's cities in, see the overlap window, share a link.

Who it's for

The site is built for people who schedule across time zones every week. That includes founders running globally distributed companies, engineering managers with team members in two or three regions, sales and customer success teams covering multiple markets, and freelancers working with clients in different countries.

If you're scheduling within a single time zone, you don't need this. If you're co-ordinating between London and New York, London and Singapore, San Francisco and Tokyo, or any of the harder combinations, the planner is built to make those decisions in under thirty seconds.

Why it exists

The dominant timezone tools were built more than a decade ago. They work, but the user interface assumes you'll spend two minutes squinting at a grid of grey rectangles. They also bury the answer to the only question most users have: when is the meeting actually possible?

besttimefor.io leads with the answer. The overlap window is the first thing you see. The hour-by-hour visual is there if you want to verify, but the lead is the practical recommendation. We built it because we needed it.

What's free and what's not

Everything on the site is free. The planner, the city-pair pages, the time-difference references, the blog, the live current-time pages. There is no premium tier, no signup wall, no API key.

We do receive a small commission if you sign up for one of the scheduling tools we recommend (Calendly, Zoom, Loom, Slack). That doesn't change which tools we recommend or what we say about them. If a tool isn't worth using, we won't list it.

How we keep the data accurate

Timezone offsets and daylight saving rules come from the IANA Time Zone Database, which is the same source used by Linux, macOS, and most major software platforms. We use the Luxon library to apply those rules, which handles fractional offsets (like India's UTC+5:30 and Nepal's UTC+5:45) and the irregular DST schedules across more than 50 jurisdictions.

Pages are regenerated on a regular cadence, so the offset shown reflects current DST status at the time of build. The live widget on each page computes the offset in the browser using the same Luxon library, so it stays accurate even across DST transitions.

If you spot an error, particularly around a DST changeover or a less-common timezone, please email us using the contact form below. We will fix it within a working day.

Editorial standards

The blog content on this site is written by the besttimefor.io team. We don't run AI-generated drafts. The city-pair pages use Claude (Anthropic's language model) at build time to produce the location-specific paragraphs, with strict input constraints: every fact in those paragraphs is sourced from a structured data file, not invented by the model. We re-read and adjust the output where the model gets it wrong.

We don't publish unverified statistics, fictional case studies, or quotes we haven't sourced. If a number isn't in our reference data, it doesn't appear on the page.