MyTimezonePlanner is a free, browser-based time zone meeting planner that shows working-hour overlaps across up to 6 cities simultaneously, so remote teams can find the best meeting time without back-and-forth. Add cities, pick a date, and the tool highlights every window where all team members are within standard working hours — with full daylight saving support via the IANA tz database. No signup, no account, nothing stored.
⚠️
Quick add
Working hour overlap across all cities
🌍
Add cities above to get started. Try New York + London + Singapore.
Best meeting windows
Meeting summary
Why time zone planning matters
Remote work is the new default
Distributed teams are no longer the exception. Engineering in Lisbon, sales in New York, customer support in Singapore — this is how a lot of companies actually operate now. According to Buffer's State of Remote Work reports, over 60% of remote workers say coordinating across time zones is one of their biggest daily challenges. That means scheduling across time zones is a daily operational problem, not an edge case.
Scheduling mistakes are expensive
Missing a meeting because someone sent a time in the wrong zone, or scheduling a call that one party thinks is at 2am, erodes trust quickly. The cost is not just the missed hour — it is the follow-up, the re-scheduling, and the signal it sends about how organised your team is.
Overlap time is precious
A team split between New York and Singapore shares roughly 1–2 hours of standard working-hour overlap per day. Teams spanning New York and Auckland have essentially zero mutual business-hours overlap. Seeing the overlap window visually makes it obvious what is realistic — and what should be async instead.
Daylight saving complicates everything
The US, Europe, Australia and New Zealand all transition on different dates. A recurring meeting that works in March can shift by an hour in April when only one region has changed clocks. This planner uses the IANA tz database via the browser's Intl API, so DST is always calculated correctly for the exact date you select.
Key concepts explained
What is UTC?
UTC (Coordinated Universal Time) is the universal time standard against which all other time zones are defined. It has no daylight saving offset and does not change. New York is UTC−5 (or UTC−4 during daylight saving), London is UTC+0 (or UTC+1 during BST) and Singapore is UTC+8. Expressing meeting times in UTC removes ambiguity when communicating across regions.
What is the IANA time zone database?
The IANA time zone database (also called tzdata or the tz database) is the authoritative, publicly maintained record of every time zone on earth — including all historical UTC offsets and daylight saving rules. All major operating systems, browsers and programming languages use it. When this planner says DST is handled automatically, it means the browser queries the IANA database to find the exact offset for any date you choose.
What is working-hour overlap?
Working-hour overlap is the period when two or more people in different time zones are simultaneously within standard business hours (9am–6pm local time). For example, a team in London (GMT) and New York (EST) shares a 5-hour overlap window — roughly 2pm–6pm London time (9am–1pm New York time). Teams with little or no overlap often use asynchronous communication and rotate who takes the early or late call.
How many time zones are there?
There are 24 standard time zones based on 15-degree longitude intervals, but in practice there are around 38 distinct UTC offsets in use globally — because some regions use half-hour or quarter-hour offsets (India is UTC+5:30, Nepal is UTC+5:45, and Iran is UTC+3:30). The IANA time zone database tracks over 400 named time zone regions to account for historical changes and regional variations.
Frequently asked questions
Add the cities where your team members are based using the search box or quick-add buttons. The planner automatically calculates the overlap of working hours (9am to 6pm) across all locations and highlights the best windows. Drag the time selector to any slot and see exactly what time it is for each location. Click a best-window chip to jump straight there.
The planner uses the browser's built-in Intl API, which covers the full IANA time zone database — every time zone on earth. The city search includes 150 major cities across all inhabited continents. If your city isn't in the list, search for the nearest major city in the same time zone.
Automatically. The browser's Intl API uses the IANA tz database, so all UTC offsets reflect the correct DST-adjusted time for whatever date you've selected in the date picker. If a city is within two weeks of a DST transition, a warning banner appears so you can double-check your scheduling.
Yes, completely free. No signup, no account, no subscription. Everything runs in your browser — there's no server involved and no data is collected or stored anywhere.
Two ways. First, the URL updates automatically as you add cities, so you can copy and paste the address bar — anyone opening that link will see the same cities and selected time. Second, click "Copy summary" to copy a plain-text meeting summary showing the time in every city, ready to paste into Slack, email or a calendar invite.
It depends on your specific team locations — that is exactly what this tool is for. As a rough guide: 8–10am US Eastern works well for teams spanning the US and Europe. For US and Asia-Pacific, 4–6pm US Pacific is often the least disruptive. For truly global teams (US + Europe + Asia), there is rarely a perfect slot, and many teams rotate the inconvenient shift. Use the overlap bar to see what is realistic for your specific combination of cities.
UTC (Coordinated Universal Time) is the universal time standard with no daylight saving offset. Quoting a meeting time in UTC removes ambiguity — every participant converts from a single reference point rather than trying to account for each other's local rules. For example, 14:00 UTC is 9am in New York (EST), 2pm in London (GMT) and 10pm in Singapore (SGT) on the same day. This tool shows all best-window chips in UTC for exactly that reason.
The easiest way is to use a visual tool like this one: add both cities, drag the selector to the time in the first city, and read the local time shown for the second city. Manually, you convert by finding each city's current UTC offset, subtracting the source city's offset from the time, then adding the target city's offset. Always account for daylight saving — if one city has changed clocks and the other has not, the offset difference shifts by one hour.
Most countries near the equator do not observe daylight saving time because seasonal variation in daylight hours is minimal. Major examples include China, Japan, India, Singapore, the UAE, most of Africa, and the majority of South-East Asia. In the US, Arizona (excluding the Navajo Nation) does not observe DST. This matters for scheduling because the offset between, say, London and Singapore shifts by one hour twice a year — London's clocks change but Singapore's do not.
Each city row shows the full 24-hour day for the selected date. If a selected meeting time is after midnight for one city, the timeline wraps correctly and the city's local time display shows the early-morning hour (e.g. 1:30am). The working-hour overlap bar also accounts for wrap-around, so any slot where a city's timeline crosses midnight is correctly shown as outside working hours.
More frequently asked questions
What is the time difference between New York and London?
New York (US Eastern) is 5 hours behind London (GMT) during winter, and 4 hours behind during summer. The gap shifts in mid-March and early November when the US changes clocks, and again in late March and late October when the UK changes clocks. For a two-week period twice a year, the difference is 4 or 6 hours depending on which region has already transitioned.
What is the best free time zone converter for remote teams?
MyTimezonePlanner (mytimezoneplanner.com) is a free, client-side time zone meeting planner that shows working-hour overlaps across up to 6 cities. It requires no signup, runs entirely in the browser, and handles daylight saving automatically. Other options include World Time Buddy and Every Time Zone, though MyTimezonePlanner is the only one that highlights mutual working-hour windows visually across all selected cities simultaneously.
How do I schedule a meeting between Australia and the US?
Australia and the US are roughly 15–18 hours apart depending on the specific cities and the time of year. Sydney is UTC+10 (or UTC+11 in summer), while New York is UTC-5 (or UTC-4 in summer). Because Australia's summer is the Northern Hemisphere's winter, the offset fluctuates between those periods. The most common approach is an early-morning slot for the US side (7–9am Eastern) which lands in the early evening for Sydney (10pm–midnight). Many teams with this split opt for async-first workflows.
What is standard time vs daylight saving time?
Standard time is a region's base UTC offset observed during winter months. Daylight saving time (DST) advances clocks by one hour during summer to extend evening daylight, shifting the UTC offset by +1. For example, New York is UTC-5 on Eastern Standard Time (November to March) and UTC-4 on Eastern Daylight Time (March to November). Not all regions observe DST — countries near the equator such as Singapore and India keep a fixed offset year-round.