How it works
Add your cities
Type a name, airport code, or country. Up to six at a time.
Drag the timeline
Scrub through 24 hours. Every city updates live, color-coded by whether it's a reasonable hour or not.
Do something with it
Copy the link, drop it in a calendar invite, or start a video call right there.
Why this exists
You can keep the offset between two cities in your head. Add a third and you’re guessing. Add DST and you’re wrong.
London and New York are five hours apart most of the year. Then four, for a few weeks in spring, because the clocks change on different Sundays. Nobody remembers which weeks.
Putting someone’s standup in their sleep hours is how you lose people. A visual timeline makes the tradeoff obvious before you send the invite.
170 cities, every continent
No account needed
Open the page and start. Nothing to sign up for.
Runs in your browser
All the math happens on your device. We don't see your cities or times.
Shareable links
Your cities and time are in the URL. Copy it, send it, they see the same thing.
More about how MeeTime works
Time zone overlap is harder than it looks
The offset between two cities isn’t fixed. It shifts when Daylight Saving Time kicks in, and not every country changes clocks on the same date. London and New York are five hours apart most of the year, then four for a few weeks in March and again in November. If you’re scheduling a recurring meeting, the time that worked last month might not work this month.
Once you add a third city the mental math gets unreliable fast. MeeTime pulls from the IANA timezone database and computes offsets for the specific date you pick, not just today. So if you’re planning something three weeks out and a DST switch happens in between, the times you see are still right.
Getting this wrong costs more than a missed meeting. A standup that falls during someone’s sleep hours, if it happens every week, breeds real resentment. The color-coded timeline makes the tradeoff visible so the team can split the inconvenience instead of dumping it on one person.
170 cities and growing
MeeTime covers 170 cities from Auckland to Zurich. San Francisco to Tokyo, New York to London, Sydney to Berlin, the pairings people actually need for work are all here. If yours is missing, tell us and we’ll add it.
New York vs London is the most common comparison (the transatlantic staple). San Francisco vs Tokyo comes up a lot for Pacific Rim teams. Sydney vs London is one of the hardest, with up to eleven hours of offset depending on the time of year.
Every city pair has its own page. meetime.app/nyc-vs-lon, meetime.app/sfo-vs-tok, and so on. They’re indexed by search engines, so you can find the comparison you need straight from Google. Copy the URL and whoever opens it sees the same cities and time slot you were looking at.
Frequently asked questions
- How does MeeTime work?
- Pick the cities where your people are, then drag the timeline through 24 hours. Each city’s local time updates as you move, color-coded green for business hours, yellow for early or late, and red for sleep. The overlap score (0-100) tells you how good each hour is for the group.
- Is MeeTime free?
- Yes. No signup, no premium tier, no feature gates. MeeTime is free and covers 170 cities across every inhabited continent.
- Does MeeTime handle Daylight Saving Time?
- Yes. MeeTime uses the IANA timezone database and calculates offsets for the exact date you select. If a DST transition happens between now and your meeting, the times are still correct. Most tools only show today’s offset.
- Does MeeTime store my data?
- No. All timezone calculations run in your browser. MeeTime doesn’t require an account and doesn’t send your city selections or meeting times to a server. Your preferences are saved in your browser’s local storage, which never leaves your device.